Go to:
Gentoo Home
Documentation
Forums
Lists
Bugs
Planet
Store
Wiki
Get Gentoo!
Gentoo's Bugzilla – Attachment 182229 Details for
Bug 259218
net-wireless/bluez-libs-2.25 doesn't build with gcc-4.3 or 4.1.2
Home
|
New
–
[Ex]
|
Browse
|
Search
|
Privacy Policy
|
[?]
|
Reports
|
Requests
|
Help
|
New Account
|
Log In
[x]
|
Forgot Password
Login:
[x]
build.log
build.log (text/plain), 8.14 KB, created by
Bogdanov Ivan
on 2009-02-16 12:56:23 UTC
(
hide
)
Description:
build.log
Filename:
MIME Type:
Creator:
Bogdanov Ivan
Created:
2009-02-16 12:56:23 UTC
Size:
8.14 KB
patch
obsolete
>>>> Unpacking source... >>>> Unpacking bluez-libs-2.25.tar.gz to /var/tmp/portage/net-wireless/bluez-libs-2.25/work >>>> Source unpacked. >>>> Compiling source in /var/tmp/portage/net-wireless/bluez-libs-2.25/work/bluez-libs-2.25 ... > * econf: updating bluez-libs-2.25/config.guess with /usr/share/gnuconfig/config.guess > * econf: updating bluez-libs-2.25/config.sub with /usr/share/gnuconfig/config.sub >./configure --prefix=/usr --host=x86_64-pc-linux-gnu --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc --localstatedir=/var/lib --libdir=/usr/lib64 --build=x86_64-pc-linux-gnu >checking for a BSD-compatible install... /usr/bin/install -c >checking whether build environment is sane... yes >checking for gawk... gawk >checking whether make sets $(MAKE)... yes >checking whether to enable maintainer-specific portions of Makefiles... no >checking for x86_64-pc-linux-gnu-gcc... x86_64-pc-linux-gnu-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 x86_64-pc-linux-gnu-gcc accepts -g... yes >checking for x86_64-pc-linux-gnu-gcc option to accept ANSI C... none needed >checking for style of include used by make... GNU >checking dependency style of x86_64-pc-linux-gnu-gcc... gcc3 >checking for a BSD-compatible install... /usr/bin/install -c >checking build system type... x86_64-pc-linux-gnu >checking host system type... x86_64-pc-linux-gnu >checking for a sed that does not truncate output... /bin/sed >checking for egrep... grep -E >checking for ld used by x86_64-pc-linux-gnu-gcc... /usr/x86_64-pc-linux-gnu/bin/ld >checking if the linker (/usr/x86_64-pc-linux-gnu/bin/ld) is GNU ld... yes >checking for /usr/x86_64-pc-linux-gnu/bin/ld option to reload object files... -r >checking for BSD-compatible nm... /usr/bin/nm -B >checking whether ln -s works... yes >checking how to recognise dependent libraries... pass_all >checking how to run the C preprocessor... x86_64-pc-linux-gnu-gcc -E >checking for ANSI C header files... yes >checking for sys/types.h... yes >checking for sys/stat.h... yes >checking for stdlib.h... yes >checking for string.h... yes >checking for memory.h... yes >checking for strings.h... yes >checking for inttypes.h... yes >checking for stdint.h... yes >checking for unistd.h... yes >checking dlfcn.h usability... yes >checking dlfcn.h presence... yes >checking for dlfcn.h... yes >checking the maximum length of command line arguments... 32768 >checking command to parse /usr/bin/nm -B output from x86_64-pc-linux-gnu-gcc object... ok >checking for objdir... .libs >checking for x86_64-pc-linux-gnu-ar... x86_64-pc-linux-gnu-ar >checking for x86_64-pc-linux-gnu-ranlib... x86_64-pc-linux-gnu-ranlib >checking for x86_64-pc-linux-gnu-strip... x86_64-pc-linux-gnu-strip >checking if x86_64-pc-linux-gnu-gcc supports -fno-rtti -fno-exceptions... no >checking for x86_64-pc-linux-gnu-gcc option to produce PIC... -fPIC >checking if x86_64-pc-linux-gnu-gcc PIC flag -fPIC works... yes >checking if x86_64-pc-linux-gnu-gcc static flag -static works... yes >checking if x86_64-pc-linux-gnu-gcc supports -c -o file.o... yes >checking whether the x86_64-pc-linux-gnu-gcc linker (/usr/x86_64-pc-linux-gnu/bin/ld -m elf_x86_64) supports shared libraries... yes >checking whether -lc should be explicitly linked in... no >checking dynamic linker characteristics... GNU/Linux ld.so >checking how to hardcode library paths into programs... immediate >checking whether stripping libraries is possible... yes >checking if libtool supports shared libraries... yes >checking whether to build shared libraries... yes >checking whether to build static libraries... yes >configure: creating libtool >configure: creating ./config.status >config.status: creating Makefile >config.status: creating include/Makefile >config.status: creating src/Makefile >config.status: creating bluez.pc >config.status: creating config.h >config.status: executing depfiles commands >make -j5 -l8 >make all-recursive >make[1]: Entering directory `/var/tmp/portage/net-wireless/bluez-libs-2.25/work/bluez-libs-2.25' >Making all in include >make[2]: Entering directory `/var/tmp/portage/net-wireless/bluez-libs-2.25/work/bluez-libs-2.25/include' >make[2]: Leaving directory `/var/tmp/portage/net-wireless/bluez-libs-2.25/work/bluez-libs-2.25/include' >Making all in src >make[2]: Entering directory `/var/tmp/portage/net-wireless/bluez-libs-2.25/work/bluez-libs-2.25/src' >if /bin/sh ../libtool --mode=compile x86_64-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I. -I.. -I../include -march=nocona -O2 -pipe -D_FORTIFY_SOURCE=2 -MT bluetooth.lo -MD -MP -MF ".deps/bluetooth.Tpo" \ > -c -o bluetooth.lo `test -f 'bluetooth.c' || echo './'`bluetooth.c; \ > then mv -f ".deps/bluetooth.Tpo" ".deps/bluetooth.Plo"; \ > else rm -f ".deps/bluetooth.Tpo"; exit 1; \ > fi >if /bin/sh ../libtool --mode=compile x86_64-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I. -I.. -I../include -march=nocona -O2 -pipe -D_FORTIFY_SOURCE=2 -MT hci.lo -MD -MP -MF ".deps/hci.Tpo" \ > -c -o hci.lo `test -f 'hci.c' || echo './'`hci.c; \ > then mv -f ".deps/hci.Tpo" ".deps/hci.Plo"; \ > else rm -f ".deps/hci.Tpo"; exit 1; \ > fi >if /bin/sh ../libtool --mode=compile x86_64-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I. -I.. -I../include -march=nocona -O2 -pipe -D_FORTIFY_SOURCE=2 -MT sdp.lo -MD -MP -MF ".deps/sdp.Tpo" \ > -c -o sdp.lo `test -f 'sdp.c' || echo './'`sdp.c; \ > then mv -f ".deps/sdp.Tpo" ".deps/sdp.Plo"; \ > else rm -f ".deps/sdp.Tpo"; exit 1; \ > fi >mkdir .libs > x86_64-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I. -I.. -I../include -march=nocona -O2 -pipe -D_FORTIFY_SOURCE=2 -MT bluetooth.lo -MD -MP -MF .deps/bluetooth.Tpo -c bluetooth.c -fPIC -DPIC -o .libs/bluetooth.o > x86_64-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I. -I.. -I../include -march=nocona -O2 -pipe -D_FORTIFY_SOURCE=2 -MT sdp.lo -MD -MP -MF .deps/sdp.Tpo -c sdp.c -fPIC -DPIC -o .libs/sdp.o > x86_64-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I. -I.. -I../include -march=nocona -O2 -pipe -D_FORTIFY_SOURCE=2 -MT hci.lo -MD -MP -MF .deps/hci.Tpo -c hci.c -fPIC -DPIC -o .libs/hci.o >sdp.c: In function 'sdp_data_alloc_with_length': >sdp.c:426: error: 'USHRT_MAX' undeclared (first use in this function) >sdp.c:426: error: (Each undeclared identifier is reported only once >sdp.c:426: error: for each function it appears in.) >sdp.c:435: error: 'UCHAR_MAX' undeclared (first use in this function) >sdp.c: In function 'sdp_append_to_buf': >sdp.c:2348: error: 'UCHAR_MAX' undeclared (first use in this function) >make[2]: *** [sdp.lo] ÐÑибка 1 >make[2]: *** Ðжидание завеÑÑÐµÐ½Ð¸Ñ Ð·Ð°Ð´Ð°Ð½Ð¸Ð¹... > x86_64-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I. -I.. -I../include -march=nocona -O2 -pipe -D_FORTIFY_SOURCE=2 -MT bluetooth.lo -MD -MP -MF .deps/bluetooth.Tpo -c bluetooth.c -o bluetooth.o >/dev/null 2>&1 > x86_64-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I. -I.. -I../include -march=nocona -O2 -pipe -D_FORTIFY_SOURCE=2 -MT hci.lo -MD -MP -MF .deps/hci.Tpo -c hci.c -o hci.o >/dev/null 2>&1 >make[2]: Leaving directory `/var/tmp/portage/net-wireless/bluez-libs-2.25/work/bluez-libs-2.25/src' >make[1]: *** [all-recursive] ÐÑибка 1 >make[1]: Leaving directory `/var/tmp/portage/net-wireless/bluez-libs-2.25/work/bluez-libs-2.25' >make: *** [all] ÐÑибка 2 > [31;01m*[0m > [31;01m*[0m ERROR: net-wireless/bluez-libs-2.25 failed. > [31;01m*[0m Call stack: > [31;01m*[0m ebuild.sh, line 49: Called src_compile > [31;01m*[0m environment, line 2148: Called _eapi0_src_compile > [31;01m*[0m ebuild.sh, line 595: Called _eapi2_src_compile > [31;01m*[0m ebuild.sh, line 629: Called die > [31;01m*[0m The specific snippet of code: > [31;01m*[0m emake || die "emake failed" > [31;01m*[0m The die message: > [31;01m*[0m emake failed > [31;01m*[0m > [31;01m*[0m If you need support, post the topmost build error, and the call stack if relevant. > [31;01m*[0m A complete build log is located at '/var/tmp/portage/net-wireless/bluez-libs-2.25/temp/build.log'. > [31;01m*[0m The ebuild environment file is located at '/var/tmp/portage/net-wireless/bluez-libs-2.25/temp/environment'. > [31;01m*[0m
You cannot view the attachment while viewing its details because your browser does not support IFRAMEs.
View the attachment on a separate page
.
View Attachment As Raw
Actions:
View
Attachments on
bug 259218
: 182229 |
182230
|
182546
|
182728
|
183537
|
183539