* gcc 4.9.1 fails to compile in libsanitizer on Fedora 14
@ 2014-08-01 15:19 Winston Smith
2014-08-01 15:43 ` Jonathan Wakely
0 siblings, 1 reply; 4+ messages in thread
From: Winston Smith @ 2014-08-01 15:19 UTC (permalink / raw)
To: gcc-help
Hi All,
As the head line already announces: gcc 4.9.1 fails to compile with an error when getting to compile libsanizer.
Here's my transcript:
$
../gcc-4.9.1/configure --prefix=/usr/ --with-local-prefix=/usr/local/
--with-native-system-header-dir=/usr/include/ --disable-libada
--enable-libssp --enable-libquadmath --enable-nls
--with-included-gettext --enable-shared --enable-threads
--disable-bootstrap --enable-languages=c,c++,fortran,go,objc,obj-c++
--enable-werror --enable-gather-detailed-mem-stats --disable-multilib
checking build system type... x86_64-unknown-linux-gnu
checking host system type... x86_64-unknown-linux-gnu
checking target system type... x86_64-unknown-linux-gnu
checking for a BSD-compatible install... /usr/bin/install -c
checking whether ln works... yes
checking whether ln -s works... yes
checking for a sed that does not truncate output... /bin/sed
checking for gawk... gawk
checking for libatomic support... yes
checking for libcilkrts support... yes
checking for libitm support... yes
checking for libsanitizer support... yes
checking for libvtv support... yes
checking for gcc... gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking for g++... g++
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking whether g++ accepts -static-libstdc++ -static-libgcc... no
checking for gnatbind... gnatbind
checking for gnatmake... gnatmake
checking whether compiler driver understands Ada... yes
checking how to compare bootstrapped objects... cmp --ignore-initial=16 $$f1 $$f2
checking for objdir... .libs
checking for version 0.10 of ISL... no
checking for version 0.11 of ISL... no
checking for version 0.12 of ISL... no
The following languages will be built: c,c++,fortran,go,lto,objc,obj-c++
checking for default BUILD_CONFIG...
checking for --enable-vtable-verify... no
checking for bison... bison -y
checking for bison... bison
checking for gm4... no
checking for gnum4... no
checking for m4... m4
checking for flex... flex
checking for flex... flex
checking for makeinfo... makeinfo
checking for expect... expect
checking for runtest... runtest
checking for ar... ar
checking for as... as
checking for dlltool... no
checking for ld... ld
checking for lipo... no
checking for nm... nm
checking for ranlib... ranlib
checking for strip... strip
checking for windres... no
checking for windmc... no
checking for objcopy... objcopy
checking for objdump... objdump
checking for readelf... readelf
checking for cc... cc
checking for c++... c++
checking for gcc... gcc
checking for gcj... no
checking for gfortran... gfortran
checking for gccgo... no
checking for ar... no
checking for ar... ar
checking for as... no
checking for as... as
checking for dlltool... no
checking for dlltool... no
checking for ld... no
checking for ld... ld
checking for lipo... no
checking for lipo... no
checking for nm... no
checking for nm... nm
checking for objdump... no
checking for objdump... objdump
checking for ranlib... no
checking for ranlib... ranlib
checking for readelf... no
checking for readelf... readelf
checking for strip... no
checking for strip... strip
checking for windres... no
checking for windres... no
checking for windmc... no
checking for windmc... no
checking where to find the target ar... host tool
checking where to find the target as... host tool
checking where to find the target cc... just compiled
checking where to find the target c++... just compiled
checking where to find the target c++ for libstdc++... just compiled
checking where to find the target dlltool... host tool
checking where to find the target gcc... just compiled
checking where to find the target gcj... host tool
checking where to find the target gfortran... just compiled
checking where to find the target gccgo... just compiled
checking where to find the target ld... host tool
checking where to find the target lipo... host tool
checking where to find the target nm... host tool
checking where to find the target objdump... host tool
checking where to find the target ranlib... host tool
checking where to find the target readelf... host tool
checking where to find the target strip... host tool
checking where to find the target windres... host tool
checking where to find the target windmc... host tool
checking whether to enable maintainer-specific portions of Makefiles... no
configure: creating ./config.status
config.status: creating Makefile
$ make
...
libtool:
compile: /home/zoidberg/1/gcc-4.9.1-build/./gcc/xgcc -shared-libgcc
-B/home/zoidberg/1/gcc-4.9.1-build/./gcc -nostdinc++
-L/home/zoidberg/1/gcc-4.9.1-build/x86_64-unknown-linux-gnu/libstdc++-v3/src
-L/home/zoidberg/1/gcc-4.9.1-build/x86_64-unknown-linux-gnu/libstdc++-v3/src/.libs
-L/home/zoidberg/1/gcc-4.9.1-build/x86_64-unknown-linux-gnu/libstdc++-v3/libsupc++/.libs
-B/usr/x86_64-unknown-linux-gnu/bin/
-B/usr/x86_64-unknown-linux-gnu/lib/ -isystem
/usr/x86_64-unknown-linux-gnu/include -isystem
/usr/x86_64-unknown-linux-gnu/sys-include -D_GNU_SOURCE -D_DEBUG
-D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS
-I. -I../../../../gcc-4.9.1/libsanitizer/sanitizer_common -I.. -I
../../../../gcc-4.9.1/libsanitizer/include -isystem
../../../../gcc-4.9.1/libsanitizer/include/system -Wall -W
-Wno-unused-parameter -Wwrite-strings -pedantic -Wno-long-long -fPIC
-fno-builtin -fno-exceptions -fno-rtti -fomit-frame-pointer
-funwind-tables -fvisibility=hidden -Wno-variadic-macros
-I../../libstdc++-v3/include
-I../../libstdc++-v3/include/x86_64-unknown-linux-gnu
-I../../../../gcc-4.9.1/libsanitizer/../libstdc++-v3/libsupc++
-DSANITIZER_LIBBACKTRACE -DSANITIZER_CP_DEMANGLE -I
../../../../gcc-4.9.1/libsanitizer/../libbacktrace -I ../libbacktrace -I
../../../../gcc-4.9.1/libsanitizer/../include -include
../../../../gcc-4.9.1/libsanitizer/libbacktrace/backtrace-rename.h -g
-O2 -D_GNU_SOURCE -MT sanitizer_platform_limits_posix.lo -MD -MP -MF
.deps/sanitizer_platform_limits_posix.Tpo -c
../../../../gcc-4.9.1/libsanitizer/sanitizer_common/sanitizer_platform_limits_posix.cc
-fPIC -DPIC -o .libs/sanitizer_platform_limits_posix.o
../../../../gcc-4.9.1/libsanitizer/sanitizer_common/sanitizer_platform_limits_posix.cc:302:75:
error: invalid application of ?izeof??to incomplete type
?_sanitizer::input_keymap_entry?? unsigned
struct_input_keymap_entry_sz = sizeof(struct input_keymap_entry);
^
../../../../gcc-4.9.1/libsanitizer/sanitizer_common/sanitizer_platform_limits_posix.cc:674:37:
error: ?VIOCGKEYCODE_V2??was not declared in this scope
unsigned IOCTL_EVIOCGKEYCODE_V2 = EVIOCGKEYCODE_V2;
^
../../../../gcc-4.9.1/libsanitizer/sanitizer_common/sanitizer_platform_limits_posix.cc:675:43:
error: ?VIOCGPROP??was not declared in this scope
unsigned IOCTL_EVIOCGPROP = EVIOCGPROP(0);
^
../../../../gcc-4.9.1/libsanitizer/sanitizer_common/sanitizer_platform_limits_posix.cc:676:37:
error: ?VIOCSKEYCODE_V2??was not declared in this scope
unsigned IOCTL_EVIOCSKEYCODE_V2 = EVIOCSKEYCODE_V2;
^
make[4]: *** [sanitizer_platform_limits_posix.lo] Error 1
make[4]: Leaving directory `/home/zoidberg/1/gcc-4.9.1-build/x86_64-unknown-linux-gnu/libsanitizer/sanitizer_common'
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory `/home/zoidberg/1/gcc-4.9.1-build/x86_64-unknown-linux-gnu/libsanitizer'
make[2]: *** [all] Error 2
make[2]: Leaving directory `/home/zoidberg/1/gcc-4.9.1-build/x86_64-unknown-linux-gnu/libsanitizer'
make[1]: *** [all-target-libsanitizer] Error 2
make[1]: Leaving directory `/home/zoidberg/1/gcc-4.9.1-build'
make: *** [all] Error 2
$ uname -a
Linux box 2.6.35.6-45.fc14.x86_64 #1 SMP Mon Oct 18 23:57:44 UTC 2010 x86_64 x86_64 x86_64 GNU/Linux
The glibc version is glibc-2.12.90-17.x86_64.
The web is mute on this issue (at least I haven't found anything related). Is there anything wrong with my setup?
Cheers,
Winston
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: gcc 4.9.1 fails to compile in libsanitizer on Fedora 14
2014-08-01 15:19 gcc 4.9.1 fails to compile in libsanitizer on Fedora 14 Winston Smith
@ 2014-08-01 15:43 ` Jonathan Wakely
2014-08-02 4:27 ` Winston Smith
0 siblings, 1 reply; 4+ messages in thread
From: Jonathan Wakely @ 2014-08-01 15:43 UTC (permalink / raw)
To: Winston Smith; +Cc: gcc-help
On 1 August 2014 16:19, Winston Smith wrote:
> The glibc version is glibc-2.12.90-17.x86_64.
>
> The web is mute on this issue (at least I haven't found anything related). Is there anything wrong with my setup?
I think it's just too old to build libsanitizer. But either the code
should be made more portable or the configure checks should have
tested for the relevant feature and disabled the lib automatically, so
please report it to Bugzilla, as described at
https://gcc.gnu.org/bugs/
As a workaround you can configure with --disable-libsanitizer
^ permalink raw reply [flat|nested] 4+ messages in thread
* RE: gcc 4.9.1 fails to compile in libsanitizer on Fedora 14
2014-08-01 15:43 ` Jonathan Wakely
@ 2014-08-02 4:27 ` Winston Smith
2014-08-02 11:09 ` Jonathan Wakely
0 siblings, 1 reply; 4+ messages in thread
From: Winston Smith @ 2014-08-02 4:27 UTC (permalink / raw)
To: jwakely.gcc; +Cc: gcc-help
Thanks a lot, Jonathan!
----------------------------------------
> Date: Fri, 1 Aug 2014 16:42:54 +0100
> Subject: Re: gcc 4.9.1 fails to compile in libsanitizer on Fedora 14
> From: jwakely.gcc@gmail.com
> To: smith_winston_6079@hotmail.com
> CC: gcc-help@gcc.gnu.org
>
> On 1 August 2014 16:19, Winston Smith wrote:
>> The glibc version is glibc-2.12.90-17.x86_64.
>> The web is mute on this issue (at least I haven't found anything related). Is there anything wrong with my setup?
>
> I think it's just too old to build libsanitizer.
I suspected that that was the case. Unfortunately, updating that box
(kernel + libc, that is) is out of the question.
> But either the code
> should be made more portable or the configure checks should have
> tested for the relevant feature and disabled the lib automatically, so
> please report it to Bugzilla, as described at
> https://gcc.gnu.org/bugs/
I'll file a bug report.
> As a workaround you can configure with --disable-libsanitizer
I wwas actually wondering if there is such a switch, but the configure.html in
INSTALL does not give a hint. I'll give that a try. Are there any drawbacks
by not having libsanitizer? I.e., what can I NOT do if I don't have that lib
installed?
Cheers,
Winston
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: gcc 4.9.1 fails to compile in libsanitizer on Fedora 14
2014-08-02 4:27 ` Winston Smith
@ 2014-08-02 11:09 ` Jonathan Wakely
0 siblings, 0 replies; 4+ messages in thread
From: Jonathan Wakely @ 2014-08-02 11:09 UTC (permalink / raw)
To: Winston Smith; +Cc: gcc-help
On 2 August 2014 05:27, Winston Smith wrote:
>> As a workaround you can configure with --disable-libsanitizer
>
> I wwas actually wondering if there is such a switch, but the configure.html in
> INSTALL does not give a hint. I'll give that a try. Are there any drawbacks
> by not having libsanitizer? I.e., what can I NOT do if I don't have that lib
> installed?
You can't use the -fsanitize=xxx options, that's all.
The sanitizers are useful, but if you don't know what they do then
you're not going to notice their absence! :-)
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2014-08-02 11:09 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2014-08-01 15:19 gcc 4.9.1 fails to compile in libsanitizer on Fedora 14 Winston Smith
2014-08-01 15:43 ` Jonathan Wakely
2014-08-02 4:27 ` Winston Smith
2014-08-02 11:09 ` Jonathan Wakely
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).