| View previous topic :: View next topic |
| Author |
Message |
roki942
Apprentice
Joined: 18 Apr 2005
Posts: 285
Location: Seattle
|
 Posted: Mon Apr 23, 2012 4:45 am Post subject: [SOLVED] glibc-2.14.1-r3 builds in 32 bit but not 64bit |
 |
|
I've just about finished switching from a 32 to 64 bit system but while sys-libs/glibc-2.14.1-r3 builds just fine as 32 bit it's not working in the new 64bit build.
The 1st error I find is | Code: | /bin/sh: /var/tmp/portage/sys-libs/glibc-2.14.1-r3/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.14.1-r3/work/build-x86-x86_64-pc-linux-gnu-nptl/sunrpc/xnlm_prot.stmp] Error 126 |
The summary is | Code: | emake failed
* ERROR: sys-libs/glibc-2.14.1-r3 failed (compile phase):
* make for x86 failed
*
* Call stack:
* ebuild.sh, line 85: Called src_compile
* environment, line 3268: Called eblit-run 'src_compile'
* environment, line 805: Called eblit-glibc-src_compile
* src_compile.eblit, line 211: Called src_compile
* environment, line 3268: Called eblit-run 'src_compile'
* environment, line 805: Called eblit-glibc-src_compile
* src_compile.eblit, line 219: Called toolchain-glibc_src_compile
* src_compile.eblit, line 130: Called die
* The specific snippet of code:
* emake || die "make for ${ABI} failed"
*
|
Can anyone help me out please?
Last edited by roki942 on Sat Apr 28, 2012 7:05 am; edited 1 time in total |
|
| Back to top |
|
 |
roki942
Apprentice
Joined: 18 Apr 2005
Posts: 285
Location: Seattle
|
| Posted: Wed Apr 25, 2012 5:15 am Post subject: |
|
|
I tried doing and emerge -e system but it didn't help - same error.
I did find out though that sandbox isn't building either. | Code: | >>> Emerging (1 of 1) sys-apps/sandbox-2.5
* sandbox-2.5.tar.xz RMD160 SHA1 SHA256 size ;-) ... [ ok ]
>>> Unpacking source...
>>> Unpacking sandbox-2.5.tar.xz to /var/tmp/portage/sys-apps/sandbox-2.5/work
>>> Source unpacked in /var/tmp/portage/sys-apps/sandbox-2.5/work
>>> Compiling source in /var/tmp/portage/sys-apps/sandbox-2.5/work/sandbox-2.5 ...
* Configuring sandbox for ABI=x86...
* econf: updating sandbox-2.5/config.guess with /usr/share/gnuconfig/config.guess
* econf: updating sandbox-2.5/config.sub with /usr/share/gnuconfig/config.sub
../sandbox-2.5//configure --prefix=/usr --build=i686-pc-linux-gnu --host=i686-pc-linux-gnu --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc --localstatedir=/var/lib --libdir=/usr/lib32
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking environment state... ok
checking for i686-pc-linux-gnu-gcc... x86_64-pc-linux-gnu-gcc -m32
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... configure: error: in `/var/tmp/portage/sys-apps/sandbox-2.5/work/build-x86':
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 seeking support:
!!! /var/tmp/portage/sys-apps/sandbox-2.5/work/build-x86/config.log
* ERROR: sys-apps/sandbox-2.5 failed (compile phase):
* econf failed
*
* Call stack:
* ebuild.sh, line 85: Called src_compile
* environment, line 2264: Called econf
* phase-helpers.sh, line 467: Called die
* The specific snippet of code:
* die "econf failed" |
The config.log gives this | Code: | This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.
It was created by sandbox configure 2.5, which was
generated by GNU Autoconf 2.68. Invocation command line was
$ ../sandbox-2.5//configure --prefix=/usr --build=i686-pc-linux-gnu --host=i686-pc-linux-gnu --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc --localstatedir=/var/lib --libdir=/usr/lib32
## --------- ##
## Platform. ##
## --------- ##
hostname = Desktop
uname -m = x86_64
uname -r = 3.2.12-gentoo
uname -s = Linux
uname -v = #2 SMP PREEMPT Fri Apr 20 22:24:14 PDT 2012
/usr/bin/uname -p = Intel(R) Core(TM)2 Quad CPU Q6700 @ 2.66GHz
/bin/uname -X = unknown
/bin/arch = unknown
/usr/bin/arch -k = unknown
/usr/convex/getsysinfo = unknown
/usr/bin/hostinfo = unknown
/bin/machine = unknown
/usr/bin/oslevel = unknown
/bin/universe = unknown
PATH: /usr/lib64/portage/bin/ebuild-helpers
PATH: /usr/local/sbin
PATH: /usr/local/bin
PATH: /usr/sbin
PATH: /usr/bin
PATH: /sbin
PATH: /bin
PATH: /opt/bin
PATH: /usr/x86_64-pc-linux-gnu/gcc-bin/4.5.3
|
Can anyone point me in the right direction?
Thanks |
|
| Back to top |
|
|
mv
Watchman
Joined: 20 Apr 2005
Posts: 6780
|
| Posted: Wed Apr 25, 2012 5:38 am Post subject: Re: sys-libs/glibc-2.14.1-r3 builds in 32 bit but not 64bit |
|
|
| roki942 wrote: | | I've just about finished switching from a 32 to 64 bit system |
Short answer: This is not possible. If you had 32 bit and want 64 bit you have to reinstall from scratch.
Long answer: If you are an expert in working with cross-compilers and installing LFS manually you might succeed (with much more work and probably even more recompiles due to building cross-compilers than with a reinstall), but if you are such an expert you would not need to ask here. |
|
| Back to top |
|
|
roki942
Apprentice
Joined: 18 Apr 2005
Posts: 285
Location: Seattle
|
| Posted: Wed Apr 25, 2012 6:26 am Post subject: Re: sys-libs/glibc-2.14.1-r3 builds in 32 bit but not 64bit |
|
|
| mv wrote: | | roki942 wrote: | | I've just about finished switching from a 32 to 64 bit system |
Short answer: This is not possible. If you had 32 bit and want 64 bit you have to reinstall from scratch.
Long answer: If you are an expert in working with cross-compilers and installing LFS manually you might succeed (with much more work and probably even more recompiles due to building cross-compilers than with a reinstall), but if you are such an expert you would not need to ask here. |
Short answer: They are 2 different installs on 2 different drives in the same computer.
Long answer: The 64bit is a reinstall from scratch on a different drive keeping the 32bit installation available until everything is setup and working properly.
That does bring a question to mind: I have /usr/portage on it's own partition and use it for both installs. Could that be causing the problem with either glibs or sandbox?
Edit: Nope, didn't use the shared /usr/portage and got the same result. |
|
| Back to top |
|
|
roki942
Apprentice
Joined: 18 Apr 2005
Posts: 285
Location: Seattle
|
| Posted: Sat Apr 28, 2012 7:04 am Post subject: |
|
|
Turns out Glibc & sandbox had the same cause for not building: When amd64 & use=multilib, then IA32_EMULATION=y is required.
This is the tread that pointed me in the right direction. https://forums.gentoo.org/viewtopic-t-905184-start-0.html |
|
| Back to top |
|
|
diablo465
Apprentice
Joined: 10 Sep 2013
Posts: 194
|
| Posted: Wed Feb 19, 2014 5:34 am Post subject: |
|
|
| I will have a try |
|
| Back to top |
|
|
|
Gentoo on AMD64
