Opened 16 years ago

Closed 14 years ago

Last modified 12 years ago

#120 closed task (fixed)

Embedded ARM uClibc-0.9.29 Build Problem

Reported by: tomo Owned by: Joe Ciccone
Priority: blocker Milestone: CLFS Embedded 1.0.0
Component: BOOK Version: CLFS Embedded 1.0.0
Keywords: uClibc-0.9.29, make, headers, -mbig-endian Cc:

Description

Book: Version SVN-0.0.1-20070214-arm Section: 6.7.1 Host: Fedora 7, 2.6.21-1.3228.fc7 #1 SMP Tue Jun 12 15:37:31 EDT 2007 i686 i686 i386 GNU/Linux

the "make headers" command fails with the following error:

[root@man-o-war uClibc-0.9.29]# make ARCH=arm headers make[1]: `conf' is up to date. cc1: error: unrecognized command line option "-mbig-endian" cc1: error: unrecognized command line option "-mbig-endian"

this looks like the modifiers are for ARM whereas we are trying to build the headers using the host CC. Does anyone know of a workaround for now?

I apologise in advance if I don't have the ticket properties correct as I'm new to CLFS :-)

tomo

Change History (6)

comment:1 in reply to:  description Changed 16 years ago by Yang Zhang

i have the same problem...can somebody help? Replying to tomo:

Book: Version SVN-0.0.1-20070214-arm Section: 6.7.1 Host: Fedora 7, 2.6.21-1.3228.fc7 #1 SMP Tue Jun 12 15:37:31 EDT 2007 i686 i686 i386 GNU/Linux

the "make headers" command fails with the following error:

[root@man-o-war uClibc-0.9.29]# make ARCH=arm headers make[1]: `conf' is up to date. cc1: error: unrecognized command line option "-mbig-endian" cc1: error: unrecognized command line option "-mbig-endian"

this looks like the modifiers are for ARM whereas we are trying to build the headers using the host CC. Does anyone know of a workaround for now?

I apologise in advance if I don't have the ticket properties correct as I'm new to CLFS :-)

tomo

comment:2 Changed 15 years ago by Francesco P. Lovergine

Here you are: the procedure detailed in the book is roughly wrong. You have NOT to create/install uclibc headers before the cross-compiler, because it needs the cross-compiler to do that. So simply ignore the headers step and go straight on. That is wrong with both uclibc and glibc AFAIK since many years. See a recent post like http://uclibc.org/lists/uclibc/2007-July/018217.html, but anyway that is the same suggested in other sources.

comment:3 in reply to:  2 Changed 15 years ago by Francesco P. Lovergine

To be more complete, the intermediate step should be removed, but the successive bootstrap gcc configuration should include --without-headers --with-newlib. Historically, there is at least one version (3.2.x) where --without-headers was broken and a pre-installation of headers was indeed required for both uclibc and glibc as a possible work around. But the book deals with 4.x and it is not broken on that regard. Note that it was ok with gcc 2.95. The use of newlib is not problematic even if the regular gcc will use the ulibc.

comment:4 Changed 14 years ago by Joe Ciccone

Owner: changed from clfs-commits@… to Joe Ciccone

comment:5 Changed 14 years ago by Joe Ciccone

Fix in progress, will commit within the next few days.

comment:6 Changed 14 years ago by Joe Ciccone

Resolution: fixed
Status: newclosed

This issue should now be resolved.

r4070

Note: See TracTickets for help on using tickets.