[uClibc] 0.9.23 and TARGET_ARCH

wct2003jm at comcast.net wct2003jm at comcast.net
Mon Mar 8 23:02:35 UTC 2004


I don't think many will find this to be a well-formed question.

I'm toying with uClibc 0.9.23 to make a user-mode MIPS world. The point being, I have modified the build. Beware! I created a new ARCH which has mips (big-endian) as its underlying machine.

But try as I might I  cannot fathom the problem that has cropped up. uClibc configures, binutils builds, and GCC goes through its first pass. The build then fires back into uClibc's  'oldconfig' target to do more work in uClibc, but TARGET_ARCH has been set to the empty string. fix_includes.sh throws up its usage() message and the game is over.

I've spun my wheels on this for far far too long. My question is simply if someone can provide a brief sequence of events in building uClibc for a cross-compilation target. I'm still trying to find out where TARGET_ARCH gets altered, if it is MEANT to be altered, and which of ever so many hard-coded lists I must have missed with my change.

I cannot easily upgrade to any newer version as time is now in short supply... but, how did 0.9.23 intend for TARGET_ARCH to vary through a build?

Thanks for any advice! -wt

--
Busily building the unknown.



More information about the uClibc mailing list