Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 278148 - dev-util/boost-build-1.39.0: compilation failed
Summary: dev-util/boost-build-1.39.0: compilation failed
Status: RESOLVED DUPLICATE of bug 293652
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Development (show other bugs)
Hardware: x86 Linux
: High normal (vote)
Assignee: Tiziano Müller (RETIRED)
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-07-17 12:53 UTC by George Sitov
Modified: 2009-11-18 19:42 UTC (History)
5 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments
build.log for boost-build-1.39 (build.log,3.32 KB, text/plain)
2009-07-17 14:41 UTC, George Sitov
Details
emerge --info for my machines (info.txt,20.95 KB, text/plain)
2009-07-18 11:05 UTC, Cănărău Constantin
Details

Note You need to log in before you can comment on or make changes to this bug.
Description George Sitov 2009-07-17 12:53:11 UTC
If i emerge lasr boost-build it make whith errors:

# emerge -av boost-build

These are the packages that would be merged, in order:

Calculating dependencies... done!
[ebuild  NS   ] dev-util/boost-build-1.39.0 [1.37.0] USE="python -examples" 0 kB
....
>>> Emerging (1 of 1) dev-util/boost-build-1.39.0
 * boost_1_39_0.tar.bz2 RMD160 SHA1 SHA256 size ;-) ...                                                                                               [ ok ]
 * checking ebuild checksums ;-) ...                                                                                                                  [ ok ]
 * checking auxfile checksums ;-) ...                                                                                                                 [ ok ]
 * checking miscfile checksums ;-) ...                                                                                                                [ ok ]
>>> Unpacking source...
>>> Source unpacked in /var/tmp/portage/dev-util/boost-build-1.39.0/work
>>> Preparing source in /var/tmp/portage/dev-util/boost-build-1.39.0/work/boost_1_39_0/tools ...
>>> Source prepared.
>>> Configuring source in /var/tmp/portage/dev-util/boost-build-1.39.0/work/boost_1_39_0/tools ...
>>> Source configured.
>>> Compiling source in /var/tmp/portage/dev-util/boost-build-1.39.0/work/boost_1_39_0/tools ...
###
### Using 'cc' toolset.
###
rm -rf bootstrap
mkdir bootstrap
i686-pc-linux-gnu-gcc -o bootstrap/mkjambase0 -O2 -march=native -pipe -fno-strict-aliasing -Wl,-O1 mkjambase.c
./bootstrap/mkjambase0 jambase.c Jambase
i686-pc-linux-gnu-gcc -o bootstrap/jam0 -O2 -march=native -pipe -fno-strict-aliasing -Wl,-O1 command.c compile.c debug.c expand.c glob.c hash.c hdrmacro.c headers.c jam.c jambase.c jamgram.c lists.c make.c make1.c newstr.c option.c output.c parse.c pathunix.c pathvms.c regexp.c rules.c scan.c search.c subst.c timestamp.c variable.c modules.c strings.c filesys.c builtins.c pwd.c class.c native.c w32_getreg.c modules/set.c modules/path.c modules/regex.c modules/property-set.c modules/sequence.c modules/order.c execunix.c fileunix.c
hash.c: In function Б─≤hashstatБ─≥:
hash.c:458: warning: format Б─≤%ldБ─≥ expects type Б─≤long intБ─≥, but argument 7 has type Б─≤unsigned intБ─≥
variable.c: In function Б─≤var_string_to_fileБ─≥:
variable.c:408: warning: ignoring return value of Б─≤fwriteБ─≥, declared with attribute warn_unused_result
variable.c:409: warning: ignoring return value of Б─≤fwriteБ─≥, declared with attribute warn_unused_result
./bootstrap/jam0 -f build.jam --toolset=cc --toolset-root= clean
...found 1 target...
...updating 1 target...
...updated 1 target...
./bootstrap/jam0 -f build.jam --toolset=cc --toolset-root= --with-python
...found 47 targets...
...updating 2 targets...
[MKDIR] bin.linuxx86
[COMPILE] bin.linuxx86/bjam
i686-pc-linux-gnu-gcc: : No such file or directory
i686-pc-linux-gnu-gcc: : No such file or directory
hash.c: In function Б─≤hashstatБ─≥:
hash.c:458: warning: format Б─≤%ldБ─≥ expects type Б─≤long intБ─≥, but argument 7 has type Б─≤unsigned intБ─≥
hcache.c: In function Б─≤write_netstringБ─≥:
hcache.c:169: warning: format Б─≤%luБ─≥ expects type Б─≤long unsigned intБ─≥, but argument 3 has type Б─≤size_tБ─≥
variable.c: In function Б─≤var_string_to_fileБ─≥:
variable.c:408: warning: ignoring return value of Б─≤fwriteБ─≥, declared with attribute warn_unused_result
variable.c:409: warning: ignoring return value of Б─≤fwriteБ─≥, declared with attribute warn_unused_result

    "i686-pc-linux-gnu-gcc"   -o bin.linuxx86/bjam "-DNDEBUG" "-DOPT_HEADER_CACHE_EXT" "-DOPT_GRAPH_DEBUG_EXT" "-DOPT_SEMAPHORE" "-DOPT_AT_FILES" "-DOPT_DEBUG_PROFILE" "-DOPT_FIX_TARGET_VARIABLES_EXT" "-DOPT_IMPROVED_PATIENCE_EXT" "-DYYSTACKSIZE=5000" "-O2" "" "-march=native" "-pipe" "" "-fno-strict-aliasing" "-O" "-Wl,-O1" "command.c" "compile.c" "debug.c" "expand.c" "glob.c" "hash.c" "hcache.c" "headers.c" "hdrmacro.c" "jam.c" "jambase.c" "jamgram.c" "lists.c" "make.c" "make1.c" "mem.c" "newstr.c" "option.c" "output.c" "parse.c" "regexp.c" "rules.c" "scan.c" "search.c" "subst.c" "w32_getreg.c" "timestamp.c" "variable.c" "modules.c" "strings.c" "filesys.c" "builtins.c" "pwd.c" "class.c" "native.c" "modules/set.c" "modules/path.c" "modules/regex.c" "modules/property-set.c" "modules/sequence.c" "modules/order.c" "execunix.c" "fileunix.c" "pathunix.c"

...failed [COMPILE] bin.linuxx86/bjam...
...failed updating 1 target...
...updated 1 target...

 *
 * ERROR: dev-util/boost-build-1.39.0 failed.
 * Call stack:
 *               ebuild.sh, line   49:  Called src_compile
 *             environment, line 2745:  Called die
 * The specific snippet of code:
 *           LIBS=${LDFLAGS} CC=$(tc-getCC) ./build.sh ${toolset} $(use_with python) || die "building bjam failed";
 *  The die message:
 *   building bjam failed
 *
 * If you need support, post the topmost build error, and the call stack if relevant.
 * A complete build log is located at '/var/tmp/portage/dev-util/boost-build-1.39.0/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/dev-util/boost-build-1.39.0/temp/environment'.
 *

>>> Failed to emerge dev-util/boost-build-1.39.0, Log file:

>>>  '/var/tmp/portage/dev-util/boost-build-1.39.0/temp/build.log'

 * Messages for package dev-util/boost-build-1.39.0:

 *
 * ERROR: dev-util/boost-build-1.39.0 failed.
 * Call stack:
 *               ebuild.sh, line   49:  Called src_compile
 *             environment, line 2745:  Called die
 * The specific snippet of code:
 *           LIBS=${LDFLAGS} CC=$(tc-getCC) ./build.sh ${toolset} $(use_with python) || die "building bjam failed";
 *  The die message:
 *   building bjam failed


gcc version 4.3.3 (Gentoo 4.3.3-r2 p1.2, pie-10.1.5)




Reproducible: Always

Actual Results:  
emerge -auvDN world
Comment 1 Lars Wendler (Polynomial-C) (RETIRED) gentoo-dev 2009-07-17 14:19:22 UTC
Please post the output of 

  emerge --info boost-build

and attach the build.log file after running

  LANG="C" emerge -1 boost-build:1.39
Comment 2 George Sitov 2009-07-17 14:41:55 UTC
Created attachment 198302 [details]
build.log for boost-build-1.39
Comment 3 George Sitov 2009-07-17 14:43:27 UTC
(In reply to comment #1)
> Please post the output of 
> 
>   emerge --info boost-build
> 
> and attach the build.log file after running
> 
>   LANG="C" emerge -1 boost-build:1.39
> 

emerge --info boost-build
Portage 2.1.6.13 (default/linux/x86/2008.0/desktop, gcc-4.3.2, glibc-2.10.1-r0, 2.6.29-gentoo i686)
=================================================================
                        System Settings
=================================================================
System uname: Linux-2.6.29-gentoo-i686-Intel-R-_Core-TM-2_Duo_CPU_E7200_@_2.53GHz-with-gentoo-2.0.1
Timestamp of tree: Fri, 17 Jul 2009 03:45:01 +0000
app-shells/bash:     4.0_p24
dev-java/java-config: 1.3.7-r1, 2.1.8-r1
dev-lang/python:     2.4.6, 2.5.4-r3, 2.6.2-r1
dev-python/pycrypto: 2.0.1-r8
dev-util/cmake:      2.6.4
sys-apps/baselayout: 2.0.1
sys-apps/openrc:     0.4.3-r3
sys-apps/sandbox:    2.0
sys-devel/autoconf:  2.13, 2.63-r1
sys-devel/automake:  1.5, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2, 1.10.2, 1.11
sys-devel/binutils:  2.19.1-r1
sys-devel/gcc-config: 1.4.1
sys-devel/libtool:   2.2.6a
virtual/os-headers:  2.6.30
ACCEPT_KEYWORDS="x86 ~x86"
CBUILD="i686-pc-linux-gnu"
CFLAGS="-O2  -march=native -pipe "
CHOST="i686-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/kde/3.5/env /usr/kde/3.5/share/config /usr/kde/3.5/shutdown /usr/share/config"
CONFIG_PROTECT_MASK="/etc/ca-certificates.conf /etc/env.d /etc/env.d/java/ /etc/fonts/fonts.conf /etc/gconf /etc/gentoo-release /etc/revdep-rebuild /etc/sandbox.d /etc/terminfo /etc/udev/rules.d"
CXXFLAGS="-O2  -march=native -pipe "
DISTDIR="/usr/portage/distfiles"
FEATURES="ccache distlocks fixpackages parallel-fetch protect-owned sandbox sfperms strict unmerge-orphans userfetch"
GENTOO_MIRRORS="http://mirror.zet/gentoo-distfiles/"
LANG="ru_RU.UTF-8"
LC_ALL="en_US.UTF-8"
LDFLAGS="-Wl,-O1"
LINGUAS="ru en"
MAKEOPTS=" -j3"
PKGDIR="/usr/portage/packages"
PORTAGE_CONFIGROOT="/"
PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --stats --timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY="/usr/local/portage/layman/qutim-overlay /usr/local/portage"
SYNC="rsync://mirror.zet/gentoo-portage"
USE="X acl acpi alsa bash-completion berkdb bluetooth branding bzip2 cairo cdr cli cracklib crypt cups dbus dga dri dvd dvdr dvdread eds emboss encode esd evo fam fbcon firefox fortran gdbm gif gpm gstreamer hal iconv isdnlog jpeg kde ldap libffi libnotify mad mdnsresponder-comtat midi mikmod mmx mng mp3 mpeg mudflap mysql ncurses nls nptl nptlonly ogg opengl openmp pam pcre pdf pdflib perl png ppds python qt3 qt3support qt4 quicktime readline reflection sdl session slang spell spl sse sse2 ssl startup-notification svg sysfs tcpd tiff truetype unicode usb vorbis webkit win32codecs x86 xml xorg xscreensaver xulrunner xv zlib" ALSA_CARDS="ali5451 als4000 atiixp atiixp-modem bt87x ca0106 cmipci emu10k1 emu10k1x ens1370 ens1371 es1938 es1968 fm801 hda-intel intel8x0 intel8x0m maestro3 trident usb-audio via82xx via82xx-modem ymfpci" ALSA_PCM_PLUGINS="adpcm alaw asym copy dmix dshare dsnoop empty extplug file hooks iec958 ioplug ladspa lfloat linear meter mmap_emul mulaw multi null plug rate route share shm softvol" APACHE2_MODULES="actions alias auth_basic authn_alias authn_anon authn_dbm authn_default authn_file authz_dbm authz_default authz_groupfile authz_host authz_owner authz_user autoindex cache dav dav_fs dav_lock deflate dir disk_cache env expires ext_filter file_cache filter headers include info log_config logio mem_cache mime mime_magic negotiation rewrite setenvif speling status unique_id userdir usertrack vhost_alias" ELIBC="glibc" INPUT_DEVICES="evdev" KERNEL="linux" LCD_DEVICES="bayrad cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb ncurses text" LINGUAS="ru en" USERLAND="GNU" VIDEO_CARDS="intel"
Unset:  CPPFLAGS, CTARGET, EMERGE_DEFAULT_OPTS, FFLAGS, INSTALL_MASK, PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS, PORTAGE_RSYNC_EXTRA_OPTS

=================================================================
                        Package Settings
=================================================================

dev-util/boost-build-1.37.0 was built with the following:
USE="python -examples"
CFLAGS="-O2 -march=native -pipe -fno-strict-aliasing"
CXXFLAGS="-O2 -march=native -pipe -fno-strict-aliasing"


ps: i downgrade gcc to 4.3.2
Comment 4 Lars Wendler (Polynomial-C) (RETIRED) gentoo-dev 2009-07-17 14:55:52 UTC
Please psot the output of

  gcc-config -l
Comment 5 George Sitov 2009-07-17 15:11:15 UTC
(In reply to comment #4)
> Please psot the output of
> 
>   gcc-config -l
> 

# gcc-config  -l
 [1] i686-pc-linux-gnu-4.3.2 *
Comment 6 Lars Wendler (Polynomial-C) (RETIRED) gentoo-dev 2009-07-18 09:47:28 UTC
Please run

  gcc-config 1

and try again. Report back the result please.
Comment 7 Cănărău Constantin 2009-07-18 11:05:45 UTC
Created attachment 198407 [details]
emerge --info for my machines
Comment 8 Cănărău Constantin 2009-07-18 11:09:12 UTC
I can confirm this bug on my desktops. 
Switching between gcc profiles or setting LANG or LC_ALL to C didn't help.
I attached previously emerge --info for both machines. One of them it's build using gcc-4 hardened witch I know it's not officially supported, but maybe it'll provide you usefully infos. 

Thank you!
Comment 9 Łukasz Michalik 2009-07-18 17:34:32 UTC
CFLAGS="-O2  -march=native -pipe "

Remove those trailing whitespace from CFLAGS and CXXFLAGS.  It's jam going wrong in newer versions.
Comment 10 Cyrius 2009-07-19 16:31:38 UTC
By commenting CFLAGS in make.conf, it works. It seems it's a problem of the ebuild.



(In reply to comment #9)
> CFLAGS="-O2  -march=native -pipe "
> 
> Remove those trailing whitespace from CFLAGS and CXXFLAGS.  It's jam going
> wrong in newer versions.
> 

Comment 11 Andrey 2009-07-19 19:53:33 UTC
(In reply to comment #10)
> By commenting CFLAGS in make.conf, it works. It seems it's a problem of the
> ebuild.
> 
I confirm this bug.
I have CFLAGS=" -O2 -mtune=pentium-m -msse2 -pipe -fomit-frame-pointer -s"
Comment 12 George Sitov 2009-07-20 06:18:34 UTC
I just remove from CFLAGS -02 and pipe:
CFLAGS="-march=i686"
and emerge was successfully.
pleas, repair the build.
Comment 13 Tiziano Müller (RETIRED) gentoo-dev 2009-07-20 07:19:10 UTC
ok, just to be clear: the issue here is that bjam's built system has a problem with extra spaces in CFLAGS (leading or somewhere in the middle).
You don't have to deactivate your CFLAGS entirely, removed additional spaces is enough until we resolve the issue.
Comment 14 clockover 2009-07-20 10:05:25 UTC
add to make.conf:

CFLAGS="-march=i686     -O3     -fomit-frame-pointer     -pipe"
#CXXFLAGS="${CFLAGS}"

CFLAGS=$(strip $(CFLAGS))
CXXFLAGS="${CFLAGS}"
Comment 15 Jochen Schlick 2009-07-25 16:42:27 UTC
(In reply to comment #13)
> ok, just to be clear: the issue here is that bjam's built system has a problem
> with extra spaces in CFLAGS (leading or somewhere in the middle).
> You don't have to deactivate your CFLAGS entirely, removed additional spaces is
> enough until we resolve the issue.
> 

in my case the extra space was at the end.
Comment 16 Sebastian Luther (few) 2009-11-18 19:42:18 UTC

*** This bug has been marked as a duplicate of bug 293652 ***