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] |
Bart, Remy, All, On Monday 31 May 2010 09:11:40 Bart van der Meulen wrote: > 2010/5/29 Remy Bohmer <linux@bohmer.net>: > > 2010/5/29 Yann E. MORIN <yann.morin.1998@anciens.enib.fr>: > >> On Thursday 27 May 2010 23:18:10 Remy Bohmer wrote: > >>> - ? ? ? ? ? ? ? ?CT_DoExecLog ALL autoreconf > >>> + ? ? ? ? ? ? ? ?CT_DoExecLog ALL autoreconf -fi > >> I'd like that you explain what those "exotic cases" are. The patch breaks > >> the build on my machine (Debian Lenny + backports): > Like Remy said our build server is a RHEL5 machine, that what our IT > wants to support, while our own build is based on a Ubuntu 8 > installation, > so in order to build on the build server, during the build we perform > a chroot to a ext2-image file containing a Ubuntu installation and > perform the actual > build inside this environment (how is that for exotic) Thanks for clarifying the situation. And I've seen far more /exotic/ configurations! :-[ > During the toolchain build we got some errors on in the mpfr build. It > was some time ago I traced the problem and I forgot most of the > details, > but what I remember is that reconf failed to update some files, > resulting is a build failure unless it was forced to recreate all > files. > Using the '-fi' option fixed the build in Ubuntu environment on build > server and did not break the build on our own native Ubuntu machines. Oh, I think I remember something about the Ubuntu folks doing some sanity check on the autostuff, and erroring out in a rather nasty way. I can't remember what they did either, but they were not entirely wrong, just that the check was over-conservative... Unfortunately, I can't remember how that was solved/worked around last time. Anyway, I don't want that a bug on a system be fixed by introducing another bug on another system. Let's just *properly fix* it. Regards, Yann E. MORIN. -- .-----------------.--------------------.------------------.--------------------. | Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: | | +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ | | +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no | | http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. | '------------------------------^-------^------------------^--------------------' -- 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] |