View previous topic :: View next topic |
Author |
Message |
shade130 n00b
Joined: 25 May 2008 Posts: 2
|
Posted: Fri Jul 25, 2008 8:25 pm Post subject: crossdev --target i386-pc-linux-uclibc fails |
|
|
Hi Iam trying to compile gentoo for 80386DX (without 387) but crossdev --target i386-pc-linux-uclibc fails with:
* Forcing the latest versions of {binutils,gcc}-config/gnuconfig ... [ ok ]
* Log: /var/log/portage/cross-i386-pc-linux-uclibc-binutils.log
* Emerging cross-binutils ... [ ok ]
* Log: /var/log/portage/cross-i386-pc-linux-uclibc-linux-headers-quick.log
* Emerging cross-linux-headers-quick ... [ ok ]
* Log: /var/log/portage/cross-i386-pc-linux-uclibc-uclibc-headers.log
* Emerging cross-uclibc-headers ...
* uclibc failed
* If you file a bug, please attach the following logfiles:
* /var/log/portage/cross-i386-pc-linux-uclibc-info.log
* /var/log/portage/cross-i386-pc-linux-uclibc-uclibc-headers.log
/var/log/portage/cross-i386-pc-linux-uclibc-uclibc-headers.log:
...
find: `lib/': No such file or directory
# Ugh!!! Remember that libdl.a and libdl_pic.a are different. Since
# libdl is pretty small, and not likely to benefit from mklibs.py and
# similar, lets just remove libdl_pic.a and avoid the issue
rm -f /var/tmp/cross/i386-pc-linux-uclibc/portage/cross-i386-pc-linux-uclibc/ucl
ibc-0.9.28.3-r7/image//usr/i386-pc-linux-uclibc/usr/lib/libdl_pic.a
cp: cannot stat `utils/ldconfig.host': No such file or directory
*
* ERROR: cross-i386-pc-linux-uclibc/uclibc-0.9.28.3-r7 failed.
* Call stack:
* ebuild.sh, line 49: Called src_install
* environment, line 2509: Called die
* The specific snippet of code:
* newbin utils/ldconfig.host ${CTARGET}-ldconfig || die;
* The die message:
* (no error message)
*
...
What I am doing wrong?
Also uclib is configured as:
Target x86 Processor Family
> 1. Generic 386 (CONFIG_GENERIC_386)
How can I force it to:
2. 386 (CONFIG_386)
?
If you could provide a step by step guide how to compile gentoo (or linux) for 80386 (not i386) i would be glad. Thanks. |
|
Back to top |
|
|
ali3nx l33t
Joined: 21 Sep 2003 Posts: 732 Location: Winnipeg, Canada
|
Posted: Fri Jul 25, 2008 8:33 pm Post subject: |
|
|
i386 chost has been depreciated and removed from glibc since glibc 2.4. You could possibly use i486 but i'm not familiar with your hardware. |
|
Back to top |
|
|
shade130 n00b
Joined: 25 May 2008 Posts: 2
|
Posted: Fri Jul 25, 2008 8:40 pm Post subject: |
|
|
I know this and thats why I m trying to build system with uClibc instead of glibc using crossdev. My hardware is standard pc (ok, fifteen years back standard pc) 80386DX with 8 MB of RAM,
PS: I want this as hobby, I am not that desperate to need to use this as main computer. |
|
Back to top |
|
|
ali3nx l33t
Joined: 21 Sep 2003 Posts: 732 Location: Winnipeg, Canada
|
Posted: Fri Jul 25, 2008 11:53 pm Post subject: |
|
|
I'm assuming that uclibc closely glibc both follow fairly similar developments. The major reason it was decided that the i386 chost was to be buried and forgotten is the transition to nptl threading defaults. It's likely that uclibc would not use linuxthreads given the overall direction towards nptl in glibc. This also may not be the case but i find it highly unlikely. The only way you could build for i386 chost would be to use linuxthreads instead of nptl however the benefits largely wouldn't outweigh the hassles. If there is an i386 chost target for uclibc the one place i'm certain you would be able to find out is #gentoo-embedded on freenode. Most of gentoo's uclibc devel is done in that irc channel. |
|
Back to top |
|
|
|