[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Bug#823145: Qt4-using packages fail to build with gcc6



Hi Rene,

On Sun, May 01, 2016 at 02:55:23PM +0200, Rene Engelhard wrote:
> When I try to compile LibreOffice (which otherwise is ready for gcc 6, see
> below) with gcc 6 I get:
>
> [...]
>
> configure:37742: x86_64-linux-gnu-g++ -o conftest -g -O2 -fstack-protector-stron
> g -Wformat -Werror=format-security -isystem /usr/include -DQT_SHARED -isystem /u
> sr/include/qt4 -isystem /usr/include/qt4/QtNetwork -isystem /usr/include/qt4 -is
> ystem /usr/include/qt4/QtGui -isystem /usr/include/qt4 -isystem /usr/include/qt4
> /QtCore -DQT_CLEAN_NAMESPACE -DQT_THREAD_SUPPORT -Wdate-time -D_FORTIFY_SOURCE=2
>   -Wl,-z,relro   conftest.cpp  >&5
> In file included from /usr/include/c++/6/bits/stl_algo.h:59:0,
>                  from /usr/include/c++/6/algorithm:62,
>                  from /usr/include/qt4/QtCore/qglobal.h:68,
>                  from /usr/include/kdemacros.h:162,
>                  from /usr/include/kdecore_export.h:24,
>                  from /usr/include/kdeversion.h:30,
>                  from conftest.cpp:139:
> /usr/include/c++/6/cstdlib:75:25: fatal error: stdlib.h: No such file or directory
>  #include_next <stdlib.h>

This has nothing to do with Qt 4. I can reproduce this with the following
minimal example:

  $ cat test.c
  #include <cstdlib>
  $ g++-6 -isystem /usr/include -c test.c
  In file included from test.c:1:0:
  /usr/include/c++/6/cstdlib:75:25: fatal error: stdlib.h: No such file or directory
   #include_next <stdlib.h>
                           ^
  compilation terminated.

This does not happen with g++-5, so it is a behavior change in GCC 6.

I am not sure whether this is a bug or intended change, so not yet reassigning
this bug, however CCing the GCC maintainer to get his opinion.

By the way, is there any particular reason why LibreOffice buildsystem uses
-isystem /usr/include?

--
Dmitry Shachnev

Attachment: signature.asc
Description: PGP signature


Reply to: