[uClibc]Anyone found the cause...

[Thomas Cameron]

Hello again,

	Okay, the build is getting better, I swear.  And I think I'm closer that 
before to figuring out what is happening.  It seems that when I do not have 
WCHAR support enabled and/or LFS enabled, things go haywire.  I'm not really 
sure why, or why changing things back before didn't fix it, but hey.
	Anyway, I am going to continue building this thing with different options 
until I break it again.  I am going to leave LFS and WCHAR enabled though.  
One other note.  Can we add a test the the uClibc make that checks if we have 
enabled LFS support, and override the .config options?  It's a pain to change 
things in both places (read: I hate compiling just to find out I forgot the 
make file).  ;-)

Joseph,
	I appreciate the heads-up. I was thinking the same thing, until I realised 
that the system _does_ compile with the default options as found in CVS.  
Once I saw that, I pretty much ruled out a flaky `make` implementation.  
Although, I do know that it is not a total impossibility.

Thanks again for the help,
Thomas Cameron
CEI Systems, Inc.


On Wednesday 08 January 2003 04:37 pm, Erik Andersen wrote:
> On Wed Jan 08, 2003 at 04:28:22PM -0500, Thomas Cameron wrote:
> > Erik,
> > 	The build was looking VERY promising, intil I got a message about not
> > being able to find a ".gcc_build_hacks" file in `build/gcc-target`.  This
> > is an obvious error, as ther is no directory by that name.
>
> Already fixed.  'cvs up'
>
>  -Erik