Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 325031 - sys-libs/glibc-2.11.2 - build-x86-x86_64-pc-linux-gnu-nptl/elf/ld-linux.so.2: cannot execute binary file
Summary: sys-libs/glibc-2.11.2 - build-x86-x86_64-pc-linux-gnu-nptl/elf/ld-linux.so.2:...
Status: RESOLVED INVALID
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Core system (show other bugs)
Hardware: AMD64 Linux
: High normal (vote)
Assignee: Gentoo Toolchain Maintainers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-06-22 09:40 UTC by kavol
Modified: 2010-07-02 23:09 UTC (History)
0 users

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


Attachments
build.log.lzma (build.log.lzma,135.11 KB, application/octet-stream)
2010-06-22 09:41 UTC, kavol
Details

Note You need to log in before you can comment on or make changes to this bug.
Description kavol 2010-06-22 09:40:39 UTC
please see the attached build log

regarding bug #195942, note that setting MAKEOPTS="-j1" does not help
Comment 1 kavol 2010-06-22 09:41:11 UTC
Created attachment 236227 [details]
build.log.lzma
Comment 2 Rafał Mużyło 2010-06-22 11:42:14 UTC
Translate that error message and post your 'emerge --info'.
Comment 3 kavol 2010-06-22 12:08:39 UTC
(In reply to comment #2)
> Translate that error message

make[2]: *** [/var/tmp/portage/sys-libs/glibc-2.11.1/work/build-x86-x86_64-pc-linux-gnu-nptl/sunrpc/xnlm_prot.stmp] Error 126
/bin/sh: /var/tmp/portage/sys-libs/glibc-2.11.1/work/build-x86-x86_64-pc-linux-gnu-nptl/elf/ld-linux.so.2: cannot execute binary file
make[2]: *** [/var/tmp/portage/sys-libs/glibc-2.11.1/work/build-x86-x86_64-pc-linux-gnu-nptl/sunrpc/xrstat.stmp] Error 126
/bin/sh: /var/tmp/portage/sys-libs/glibc-2.11.1/work/build-x86-x86_64-pc-linux-gnu-nptl/elf/ld-linux.so.2: cannot execute binary file
/bin/sh: /var/tmp/portage/sys-libs/glibc-2.11.1/work/build-x86-x86_64-pc-linux-gnu-nptl/elf/ld-linux.so.2: cannot execute binary file
make[2]: *** [/var/tmp/portage/sys-libs/glibc-2.11.1/work/build-x86-x86_64-pc-linux-gnu-nptl/sunrpc/rpcsvc/bootparam_prot.stmp] Error 126
make[2]: *** [/var/tmp/portage/sys-libs/glibc-2.11.1/work/build-x86-x86_64-pc-linux-gnu-nptl/sunrpc/rpcsvc/nlm_prot.stmp] Error 126

> and post your 'emerge --info'.

Portage 2.1.8.3 (default/linux/amd64/10.0/desktop/kde, gcc-4.4.3, glibc-2.10.1-r1, 2.6.33-gentoo-r2 x86_64)
=================================================================
System uname: Linux-2.6.33-gentoo-r2-x86_64-Intel-R-_Core-TM-_i5_CPU_750_@_2.67GHz-with-gentoo-1.12.13
Timestamp of tree: Tue, 22 Jun 2010 08:00:01 +0000
app-shells/bash:     4.0_p37
dev-lang/python:     2.6.5-r2, 3.1.2-r3
dev-util/cmake:      2.6.4-r3
sys-apps/baselayout: 1.12.13
sys-apps/sandbox:    1.6-r2
sys-devel/autoconf:  2.65
sys-devel/automake:  1.8.5-r4, 1.9.6-r3, 1.10.3, 1.11.1
sys-devel/binutils:  2.20.1-r1
sys-devel/gcc:       4.3.4, 4.4.3-r2
sys-devel/gcc-config: 1.4.1
sys-devel/libtool:   2.2.6b
virtual/os-headers:  2.6.30-r1
ACCEPT_KEYWORDS="amd64"
ACCEPT_LICENSE="* -@EULA"
CBUILD="x86_64-pc-linux-gnu"
CFLAGS="-march=native -O2 -pipe -ggdb"
CHOST="x86_64-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/share/X11/xkb /usr/share/config"
CONFIG_PROTECT_MASK="/etc/ca-certificates.conf /etc/env.d /etc/fonts/fonts.conf /etc/gconf /etc/revdep-rebuild /etc/sandbox.d /etc/terminfo"
CXXFLAGS="-march=native -O2 -pipe -ggdb"
DISTDIR="/usr/portage/distfiles"
FEATURES="assume-digests distlocks fixpackages news parallel-fetch protect-owned sandbox sfperms splitdebug strict unmerge-logs unmerge-orphans userfetch"
GENTOO_MIRRORS="http://distfiles.gentoo.org"
LANG="C"
LDFLAGS="-Wl,-O1"
LINGUAS="cs"
MAKEOPTS="-j5"
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"
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
USE="X a52 aac acpi alsa amd64 berkdb branding bzip2 cdr cli cracklib crypt cups cxx dbus dri dts dvd dvdr emboss encode exif ffmpeg firefox flac fortran gallium gdbm gif hal iconv jpeg jpeg2k kde kerberos kvm libnotify lzma mad mikmod mmx mng modules mp3 mp4 mpeg mudflap multilib ncurses nls nptl nptlonly ogg opengl openmp pam pango pcre pdf perl png ppds pppd python qt3support qt4 readline reflection scrobbler sdl session spell spl sse sse2 ssl ssse3 startup-notification svg symlink sysfs tiff truetype unicode usb vorbis x264 xcb xcomposite xml xorg xulrunner xv xvid zlib" ALSA_CARDS="ali5451 als4000 atiixp atiixp-modem bt87x ca0106 cmipci 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="keyboard mouse evdev" KERNEL="linux" LCD_DEVICES="bayrad cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb ncurses text" LINGUAS="cs" RUBY_TARGETS="ruby18" USERLAND="GNU" VIDEO_CARDS="nouveau nv" XTABLES_ADDONS="quota2 psd pknock lscan length2 ipv4options ipset ipp2p iface geoip fuzzy condition tee tarpit sysrq steal rawnat logmark ipmark dhcpmac delude chaos account" 
Unset:  CPPFLAGS, CTARGET, EMERGE_DEFAULT_OPTS, FFLAGS, INSTALL_MASK, LC_ALL, PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS, PORTAGE_RSYNC_EXTRA_OPTS, PORTDIR_OVERLAY
Comment 4 kavol 2010-06-27 21:16:01 UTC
the same with glibc-2.11.2 ...
Comment 5 Jeroen Roovers (RETIRED) gentoo-dev 2010-06-28 05:46:07 UTC
binární soubor nelze spustit -> cannot execute binary file
Comment 6 SpanKY gentoo-dev 2010-06-28 21:18:23 UTC
only time we've seen these errors is when the user screwed up their config and disabled 32bit support in their kernel
Comment 7 kavol 2010-06-29 08:46:57 UTC
(In reply to comment #6)
> only time we've seen these errors is when the user screwed up their config and
> disabled 32bit support in their kernel

http://www.gentoo.org/doc/en/handbook/handbook-amd64.xml?part=1&chap=7

"Make sure you select IA32 Emulation if you want to be able to run 32-bit programs. Gentoo will install a multilib system (mixed 32-bit/64-bit computing) by default, so you probably want this option."

1. No, I do NOT want to be able to run 32-bit programs, why the heck I'd buy 64bit CPU then?

2. "probably want" does not sound like "you won't be able to compile glibc without this"

3. I have the same kernel settings since I've installed the system about two months ago (except for features added in newer kernels - make oldconfig ...) It has worked on installation. Now it stopped working which seems like a regression => reopening.
Comment 8 kavol 2010-06-29 10:32:29 UTC
ok, so now I'm on the right track with the 32/64 issue ...

it helps to choose no-multilib profile, I can recompile glibc with default/linux/amd64/10.0/no-multilib set

so I see three problems here:

1) Gentoo Handbook - Configuring the Kernel does not state that IA32 emulation is a must under some circumstances - a docs bug

2) glibc ebuild does not check for the build prerequisites - just as various drivers do check for kernel settings that are required, this should be implemented also for CONFIG_X86_32 when glibc is built with multilib on

3) Portage does not provide no-multilib flavours of various profiles (I'd need desktop/kde) - a RFE material ...

therefore I'd file those as new bugs and make it blocking this one, if it is appropriate?
Comment 9 SpanKY gentoo-dev 2010-06-29 18:51:49 UTC
your setup is invalid.  seek assistance on forums/mailing lists.  bugzilla is not a support center for user questions.
Comment 10 kavol 2010-06-29 19:31:17 UTC
(In reply to comment #9)
> your setup is invalid.

maybe, but just because your documentation is invalid - I repeat:

http://www.gentoo.org/doc/en/handbook/handbook-amd64.xml?part=1&chap=7

"Make sure you select IA32 Emulation if you want to be able to run 32-bit
programs. Gentoo will install a multilib system (mixed 32-bit/64-bit computing)
by default, so you probably want this option."

2. "probably want" does not sound like "you won't be able to compile glibc
without this"


note also that http://www.gentoo.org/doc/en/handbook/handbook-amd64.xml?part=1&chap=6#doc_chap2 does NOT mention any link between profiles and kernel config

and it says:

"If you want to have a pure 64-bit environment, with no 32-bit applications or libraries, you should use a non-multilib profile:"

I'm not a native English speaker, but I remember we've been taught there is a difference between "should" and "must" (or "have to") ...

> seek assistance on forums/mailing lists.  bugzilla is
> not a support center for user questions.

neither this is a place to show your arrogance

requests for enhancements (I proposed two within the previous comment) are perfectly valid for bugzilla, there is even a special value in the Severity field for them, these are not "user questions" to be posted on forums
Comment 11 SpanKY gentoo-dev 2010-06-29 20:26:27 UTC
the language is fine for native english speakers as it isnt taken to be a strict spec.  if you want something localized, contribute a translation.

this bug is full of crap at this point, so clone a new one with only your documentation suggestions for clarification.  you original report is still invalid: glibc cannot compile when the user has an invalid configuration.
Comment 12 kavol 2010-07-02 23:09:38 UTC
(In reply to comment #11)
> the language is fine for native english speakers as it isnt taken to be a
> strict spec.  if you want something localized, contribute a translation.

a "strict spec"? - ahem, what are you talking about?

... seems like I'm missing something here, if mentioning clearly which configuration is considered invalid is impossible because it would no longer be "Handbook" but a "Strict spec" then what is all the chapter "Activating Required Options" about, shouldn't that be removed?

and how do you express (how the user can know) which configuration do you consider invalid if it is not specified in the docs?

> this bug is full of crap at this point, so clone a new one with only your
> documentation suggestions for clarification.  you original report is still
> invalid: glibc cannot compile when the user has an invalid configuration.

if you'd bother to read it, try to understand, then answer the question, there would be less crap in this bugreport ...

anyways, here you go:

1. bug #326691
2. bug #326693
3. bug #326695