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] |
On Sun, 2007-05-06 12:49:20 +0200, Yann E. MORIN <yann.morin.1998@anciens.enib.fr> wrote: > On Sunday 06 May 2007 12:44, Robert P. J. Day wrote: > > actually, i would probably start *precisely* with the headers based on > > "git pull" just so, if there was a recently introduced problem, i'd > > spot it immediately and could fix it ASAP. > > I'm not buying a toolchain that is made of HEAD from any of its components, > unless there is a real good reason. And when I mean real good, I mean it. I wouldn't "buy" it either, but for development, I'd *prefer* to be able to build gcc, binutils, GNU libc, Linux right out of their CVS/SVN/GIT repositories to catch breakages early. I've hacked a script that builds me a vax-linux-uclibc toolchain exactly for that purpose. And it does a good job (except that there's an unfixed GCC bug which makes GCC unuseable for this target right now.) But after all, the rarely used architectures break too easy in midend changes, so that should be easy to monitor. MfG, JBG -- Jan-Benedict Glaw jbglaw@lug-owl.de +49-172-7608481 Signature of: http://perl.plover.com/Questions.html the second :
Attachment:
signature.asc
Description: Digital signature
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |