Re: crosstool and uClibc

[Kai Ruottu <karuottu at mbnet dot fi>]

Dan Kegel kirjoitti:
> Yann E. MORIN wrote:
>
> > Once upon a time (on Monday 04 July 2005 14:53), Dan Kegel wrote :
> >  > Yann E. MORIN wrote:
> >  > > checking for library containing strerror... configure: error: 
> > Link tests
> >  > > are not allowed after GCC_NO_EXECUTABLES.
> >  > > make: *** [configure-target-libiberty] Error 1
> >  > In this case, I looked a bit, and the magic value might be
> >  >   ac_cv_search_strerror="none required"
> >  >   export ac_cv_search_strerror
> >
> > Well, indeed that solved the problem somewhat, but the next test 
> > fails, and
> > the next, and so on for every function that libiberty requires. So I 
> > have to
> > tell libiberty that all functions it requires really do exist. I 
> > either do
> > that by defining every ac_cv_search_* and ac_cv_func_* before calling
> > configure, which is a rather painfull method and in my opinion not the
> > right way to do it
>
>
> Nope, it's the right way to do it.  A little work with grep
> and the configure.ac file should produce a full list without
> much effort.  Alternately, you could run configure natively
> and grab all the values that libiberty sets, and use them.

 Or if you now have binutils, some kind of GCC and some kind of C
library for your target, why not simply try the obvious thing, to
try to compile and link that "Hello World"?  And then see what on
earth is wrong with your new (but not yet fully ready) GCC ?

 If you have a car where the lightbulbs are not yet installed, you
will receive my permission to drive your car at daytime (but not in
Finland where one must use light even at daytime). Using a not yet
ready GCC for compiling something simple is just as allowed by me,
maybe not by Dan because he has not suggested that :-)

 Just try your "$target-gcc -o hello_$target hello.c" and then report
what it says and I think we see many suggestions for fixing your 
existing GCC or how to rearrange the target libraries and such...

------
Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sources.redhat.com