View previous topic :: View next topic |
Author |
Message |
raddaqii Tux's lil' helper
Joined: 27 Mar 2005 Posts: 110 Location: Berlin, Old Europe
|
Posted: Fri Aug 30, 2013 1:44 pm Post subject: Crossdev -t i686 pulls ancient glibc-2.8-20080602 [SOLVED] |
|
|
I'm setting up a crossdev environment on my x86_64 desktop, I want to help emerge stuff on an x86 T40. I read the Gentoo Distcc Guide, and the Gentoo Crossdev Distcc and Crossdev Guides. (And I have indeed seen the thread that just makes it work by adding -m32 to x86_64 compiles. But I'm going traditional.)
The official guide seems to omit the first of these next steps
Code: | crossdev --init-target |
and starts with this. Here I run into problems.
The latter one downloads and compiles quite a lot of packages, but fails with cross-i686-pc-linux-gnu/glibc-2.8_p20080602-r1, different from Crossdev Guide Listing 2.3
Code: | # crossdev -t i686-pc-linux-gnu
--------------------------------------------------------------------------------------------------------------------------------------
* crossdev version: 20120913
* Host Portage ARCH: amd64
* Target Portage ARCH: x86
* Target System: i686-pc-linux-gnu
* Stage: 4 (C/C++ compiler)
* ABIs: default
* binutils: binutils-[latest]
* gcc: gcc-[latest]
* headers: linux-headers-[latest]
* libc: glibc-[latest]
* CROSSDEV_OVERLAY: /var/lib/layman/init6
* PORT_LOGDIR: /var/log/portage
* PORTAGE_CONFIGROOT:
* Portage flags:
_ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ -
* leaving sys-devel/binutils in /var/lib/layman/init6
* leaving sys-devel/gcc in /var/lib/layman/init6
* leaving sys-kernel/linux-headers in /var/lib/layman/init6
* leaving sys-libs/glibc in /var/lib/layman/init6
* leaving sys-devel/gdb in /var/lib/layman/init6
* enabling thin-manifests due to /var/lib/layman/mozilla
_ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ -
* Log: /var/log/portage/cross-i686-pc-linux-gnu-binutils.log
* Emerging cross-binutils ... [ ok ]
* Log: /var/log/portage/cross-i686-pc-linux-gnu-linux-headers-quick.log
* Emerging cross-linux-headers-quick ... [ ok ]
* Log: /var/log/portage/cross-i686-pc-linux-gnu-glibc-headers.log
* Emerging cross-glibc-headers ...
...
|
From the log I see it tries to find glibc-2.8-20080602.tar.bz2 like almost everywhere, on any of this planet's ftp servers, but won't find it. Manually locating and downloading th package was easy though, and it matches the size 16235726 bytes portage expects.
I'm confused, how do I go on? I see two possibilities, no, three actually:
a) Handing over the manually downloaded file to portage. I couldn't see emerge noticing when I copied it to /usr/portage/distfiles how do I make it recognize it is there?
b) Why does it need such an ancient version anyhow? How would I tame it and have it use another version? (bonsaikitten offered to help in #gentoo-chat, but I did not see the wood for the trees, so came here)
c) Other suggestions?
Last edited by raddaqii on Thu Sep 26, 2013 9:37 am; edited 1 time in total |
|
Back to top |
|
|
raddaqii Tux's lil' helper
Joined: 27 Mar 2005 Posts: 110 Location: Berlin, Old Europe
|
Posted: Wed Sep 11, 2013 9:10 am Post subject: |
|
|
Bump.
Hint: I don't mind being helped with anything obvious. Atm I have no idea how to usefully proceed. |
|
Back to top |
|
|
cwr Veteran
Joined: 17 Dec 2005 Posts: 1969
|
Posted: Wed Sep 11, 2013 3:29 pm Post subject: |
|
|
I don't understand why crossdev sees glibc-2.8 as current, but if you check the
crossdev scritpts arguments you'll see that you can call it with explicit gcc/binutils/glibc
versions. Check the current versions on your system and try that approach.
Will |
|
Back to top |
|
|
raddaqii Tux's lil' helper
Joined: 27 Mar 2005 Posts: 110 Location: Berlin, Old Europe
|
Posted: Thu Sep 26, 2013 9:37 am Post subject: |
|
|
Thanks for the reply. Did not follow your suggestion (although I should sometime), but I'll be marking this as solved anyway.
In my errorlog I noticed a complaint of layman about paths not being set correctly. I apparently "fixed" it aka found a workaround, by doing the following.
Code: |
# mkdir /var/lib/layman/profiles
# mv /var/lib/layman/i686-pc-linux-gnu /var/lib/layman/profiles/i686-pc-linux-gnu
|
Likely I did not understand the layman tutorial, and layman naming conventions and/or folder structure properly, but moving as described lets crossdev find what it needs, and it behaves as it should. I can now crossdevly compile packages for the old T40's Pentium M on my amd64 box. :) |
|
Back to top |
|
|
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|