This is the mail archive of the crossgcc@sourceware.org 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] |
Hi, On Fri, Sep 3, 2010 at 1:04 AM, loody <miloody@gmail.com> wrote: > hi: > > 2010/9/3 Arnaud Lacombe <lacombar@gmail.com>: >> Hi, >> >> On Thu, Sep 2, 2010 at 11:02 PM, loody <miloody@gmail.com> wrote: >>>> I'm on the move until next Tuesday (at least), so will most probably not be able to reply >>>> (internet at the hotel is expensive here :-( ). >>> I attach the configs and logs of not successfully compiling. >> build.log.mipsel.uC30.1: >> I guess your uClibc configuration is missing UCLIBC_HAS_FLOATS. >> >> build.log.mipsel.uC30.2: >> cf. http://lists.uclibc.org/pipermail/uclibc-cvs/2006-April/022762.html >> >> build.log.x86.uC30.1: >> I guess your uClibc configuration is missing UCLIBC_HAS_FENV. > I will add your suggestion and report the result. > BTW, if I remember correctly, crossng will first ask me to fill the > default uClibc config location then it will replace by the default > one. > if so, why should I give the place at first time? > to be more precise, you give ct-ng how you want uClibc, then ct-ng amends it features-wise with various things. <personal-opinion>this really _sucks_.<personal-opinion/> Fixing this cleanly would leads to a more clever uClibc build script, tighter communication between the C library configuration and the compiler, and eventually structural changes in ct-ng. While there, gcc can definitively build without UCLIBC_HAS_FENV, however, it requires SUSV[34] legacy stuff. This dependency may in turn vary depending on versions... - Arnaud -- For unsubscribe information see http://sourceware.org/lists.html#faq
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |