crossgcc build script thoughts

[Dan Kegel]

I'm mulling over the idea of parameterizing the crossgcc
build script a bit differently.  Since in my experience,
just about any component may need patching, I'm tempted
to put the patches in a directory named after the component,
and just apply any patches in that directory when untarring
the component.  e.g. glibc-2.2.5-patches would contain the
one patch needed to build glibc-2.2.5.

I also feel that, at least for the purposes of my
experiments, supporting newlib targets is getting in
the way, so I'm tempted to make a version of the script
that is specialized for linux targets.

And since I'm into automation, I'm tempted to remove
any interactive prompts from this new script.

Anyway, here's the kind of script I'm thinking about.
It's a bit more terse and concise.  I haven't tested it
yet, just thought I'd post it to see what folks think
of the idea.
- Dan
-------------- next part --------------
A non-text attachment was scrubbed...
Name: crosstool.sh
Type: application/x-sh
Size: 5355 bytes
Desc: not available
URL: <http://sourceware.org/pipermail/crossgcc/attachments/20030523/fb94f235/attachment.sh>
-------------- next part --------------
------
Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sources.redhat.com