This is the mail archive of the crossgcc@sources.redhat.com mailing list for the crossgcc project.

See the CrossGCC FAQ for lots more information.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: crosstool and uClibc


Hi!

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, or I find  way to tell it globally, with a configure
swith I still didn't find. A third way would be to patch the libiberty
configure to not try to search these function and assume they do exist.

 > Gentoo ran into something similar in libstdc++:
 > http://bugs.gentoo.org/show_bug.cgi?id=55108
 > http://www.ldsys.net/~cgs/linux-mips/portage-20040916/sys-devel/gcc/files/
 >3.4.1/gcc-3.4.1-glibc-is-native.patch and worked around it by hacking
 > libiberty's configure script to simply not call GCC_NO_EXECUTABLES, since
 > they knew it was wrong.

That I tried, but it was agains libstdc++, not libiberty (or did I miss a
point there?). So I applied a similar fix for libiberty, but it did no good.

Ah, yes, if I disable --enable-serial-configure for final gcc, then a
similar error occurs in libstdc++, and Gentoo's patch does no good either.

 > Good luck.  Let us know what happens.

So...

So far I managed a C-only toolchain that builds OK and builds a trivial C
program OK. To do next is finished to clean up crosstool, rebuild the
toolchain, and test it.

For now, because we won't be using C++ for now, and because of time, I'll keep
the C-only uClibc toolchain and will come back later regarding C++ with uClibc
(I'll have to ask people there, I guess :-) ).

Thanks for the help! :-)
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +0/33 662376056 | Software  Designer | \ / CAMPAIGN     |   ^                |
| --==< °_° >==-- °---.----------------:  X  AGAINST      |  /e\  There is no  |
| web: ymorin.free.fr | SETI@home 3808 | / \ HTML MAIL    |  """  conspiracy.  |
°---------------------°----------------°------------------°--------------------°
 \__ np:  [Stopped] __________________________________________________________/


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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]