| Summary: | sys-apps/sandbox-1.2.18.1-r2 emerge fails - cannot run C compiled programs. | ||
|---|---|---|---|
| Product: | Portage Development | Reporter: | muhsin <mrfroasty> |
| Component: | Sandbox | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
| Status: | VERIFIED NEEDINFO | ||
| Severity: | normal | CC: | dhp_gentoo |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | AMD64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: |
build log
emerge --info config.log |
||
1/ Don't ever refer to forums.g.o. for a bug description. 2/ Please, read the messages provided before filing a bug. <snip> !!! Please attach the following file when filing a report to bugs.gentoo.org: !!! /var/tmp/portage/sys-apps/sandbox-1.2.18.1-r2/work/build-x86-x86_64-pc-linux-gnu/config.log </snip> 3/ emerge --info missing as well. Created attachment 140625 [details]
build log
Created attachment 140627 [details]
emerge --info
Well, if you are installing, then you pretty like are missing IA32 emulation in your kernel. Otherwise there's tons of duplicates about system getting screwed by eselect-compiler. (In reply to comment #4) > Well, if you are installing, then you pretty like are missing IA32 emulation in > your kernel. Otherwise there's tons of duplicates about system getting screwed > by eselect-compiler. > But I can build one in a chrooted enviroment...will that help?...as till now I am only capable only accessing with chroot... Well no it won't really help at all until you post the config.log as the error message told you... :) (In reply to comment #6) > Well no it won't really help at all until you post the config.log as the error > message told you... :) > config.log...isnt that the file i attached later en call it build.log?.. (In reply to comment #7) > config.log...isnt that the file i attached later en call it build.log?.. No, it isn't... The message even told you the exact path to the file. (In reply to comment #8) > (In reply to comment #7) > > config.log...isnt that the file i attached later en call it build.log?.. > > No, it isn't... The message even told you the exact path to the file. > sorry man...i got totally lost of what is config.log[even after googlin]...take it easy on me, u are talkin to a noob here....I only know that build.log which I have attached in this bug...got no idea if there is another file, so pls be specific...if possible with the full path to the location of the file....thanks. (In reply to comment #0) > !!! Please attach the following file when filing a report to bugs.gentoo.org: > !!! > /var/tmp/portage/sys-apps/sandbox-1.2.18.1-r2/work/build-x86-x86_64-pc-linux-gnu/config.log Created attachment 140631 [details]
config.log
(In reply to comment #10) > (In reply to comment #0) > > !!! Please attach the following file when filing a report to bugs.gentoo.org: > > !!! > > /var/tmp/portage/sys-apps/sandbox-1.2.18.1-r2/work/build-x86-x86_64-pc-linux-gnu/config.log > sorry man its my first time to report a bug.... > ../sandbox-1.2.18.1//configure: line 2353: ./a.out: cannot execute binary file Well, as noted, this won't work w/o IA32 emulation support; closing. http://www.gentoo.org/doc/en/gentoo-amd64-faq.xml#kernel (In reply to comment #13) > > ../sandbox-1.2.18.1//configure: line 2353: ./a.out: cannot execute binary file > > Well, as noted, this won't work w/o IA32 emulation support; closing. > > http://www.gentoo.org/doc/en/gentoo-amd64-faq.xml#kernel > I havent build a kernel yet...but even if build one I am going to stuck on emerge grub [this will fail on almost same errors c/c++ compiler]...that means no chance to boot my system. ..any idea to get gentoo on this machine? (In reply to comment #13) > > ../sandbox-1.2.18.1//configure: line 2353: ./a.out: cannot execute binary file > > Well, as noted, this won't work w/o IA32 emulation support; closing. > > http://www.gentoo.org/doc/en/gentoo-amd64-faq.xml#kernel > Does this mean that <<sandbox can not be compiled in non-multilib x86_64-pc-linux-gnu>> ? no => I don't understand ... yes => non-multilib profile should not exist in x86_64 stages. I understood: we just need to activate IA32 support ( CONFIG_IA32_EMULATION ) in kernel, and do not need multilib (any way, multilib is supported in the default profile). So, we (users) just need to recompile & reboot to fix this. In theory ;) |
My installation is stuck when i want to update portage, and the compiler included in the tarballs is gcc 4.1.1 which fail to compile not only sandbox but some other packages as well including grub and gcc!. I have tried FEATURES="-sandbox -usersandbox" emerge -1av sandbox [playin around as well] I have tried emerge glibc I have tried to check in /usr/bin for i686 like some other forum members. I have tried emerge gcc ....the story goes on and on. Finally, after 2 days of waiting from the forum and irc no luck... this is make.conf just incase somebody dont want to go through the forum topic that i left it there: # These settings were set by the catalyst build script that automatically # built this stage. # Please consult /etc/make.conf.example for a more detailed example. CFLAGS="-march=nocona -O2 -pipe" CXXFLAGS="${CFLAGS}" # This should not be changed unless you know exactly what you are doing. You # should probably be using a different stage, instead. CHOST="x86_64-pc-linux-gnu" ACCEPT_KEYWORDS="amd64" VIDEO_CARDS="nvidia" MAKEOPTS="-j2" #FEATURES="ccache collision-protect strict userfetch userpriv metadata-transfer parallel-fetch assume-digest digest" #setting language LINGUAS="en" CCACHE_SIZE="2G" CCACHE_DIR=/var/tmp/ccache GENTOO_MIRRORS="http://mirror.muntinternet.net/pub/gentoo/ http://ftp.heanet.ie/pub/gentoo/ http://mirror.ovh.net/gentoo-distfiles/ http://gentoo.tiscali.nl/" #use flags USE="multilib X gtk gnome -kde dvd cdr alsa nvidia qt3 qt4 unicode nptlonly" Reproducible: Always Actual Results: some packages cant be compiled eg grub,gcc and sandbox Expected Results: I expected portage emerged and gcc compilling all packages. >>> Unpacking source... >>> Unpacking sandbox-1.2.18.1.tar.bz2 to /var/tmp/portage/sys-apps/sandbox-1.2.18.1-r2/work * Applying sandbox-1.2.18.1-open-normal-fail.patch ... [ ok ] * Applying sandbox-1.2.18.1-open-cloexec.patch ... [ ok ] >>> Source unpacked. >>> Compiling source in /var/tmp/portage/sys-apps/sandbox-1.2.18.1-r2/work/sandbox-1.2.18.1 ... * If configure fails with a 'cannot run C compiled programs' error, try this: * FEATURES=-sandbox emerge sandbox * Configuring sandbox for ABI=x86... * econf: updating sandbox-1.2.18.1/config.guess with /usr/share/gnuconfig/config.guess * econf: updating sandbox-1.2.18.1/config.sub with /usr/share/gnuconfig/config.sub ../sandbox-1.2.18.1//configure --prefix=/usr --host=i686-pc-linux-gnu --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc --localstatedir=/var/lib --libdir=/usr/lib32 --enable-multilib --build=i686-pc-linux-gnu checking for a BSD-compatible install... /bin/install -c checking whether build environment is sane... yes checking for gawk... gawk checking whether make sets $(MAKE)... yes checking for i686-pc-linux-gnu-gcc... no checking for gcc... gcc checking for C compiler default output file name... a.out checking whether the C compiler works... configure: error: cannot run C compiled programs. If you meant to cross compile, use `--host'. See `config.log' for more details. !!! Please attach the following file when filing a report to bugs.gentoo.org: !!! /var/tmp/portage/sys-apps/sandbox-1.2.18.1-r2/work/build-x86-x86_64-pc-linux-gnu/config.log !!! ERROR: sys-apps/sandbox-1.2.18.1-r2 failed. Call stack: ebuild.sh, line 1614: Called dyn_compile ebuild.sh, line 971: Called qa_call 'src_compile' environment, line 3379: Called src_compile sandbox-1.2.18.1-r2.ebuild, line 87: Called econf '--libdir=/usr/lib32' '--enable-multilib' ebuild.sh, line 577: Called die !!! econf 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/sys-apps/sandbox-1.2.18.1-r2/temp/build.log'.