On Mon, 27 Sep 1999, Philip Blundell wrote:
> Making that work in 2.1.1 would actually require only a pretty trivial change
> to the configure script...
>
> p.
Is it possible to quickly patch 2.1.1 and fix the unknown 2.1.2 problem later?
I mean, is it possible to know that "pretty trivial change" to the glibc-2.1.1
configure script, that would enable me to complete my toolchain ?
In order to see my bosses calm down a bit, and maintain trust in this
project, I need my toolchain to be completed asap. I use most of my
spare time at learning bash, make, grep, sed, awk and all those tools needed in
order to fix the trivial bug in 2.1.1 configure script and the 2.1.2 unknown
one. However, I've largely underestimated the learning curve that I would have
to swallow (stupid me; I mean, this thing is HUGE), and I'm totally out of
track from my original schedule :-(.
I really want to contribute on this 2.1.2 problem. But, I must show the big
boys a working kernel on my EBSA before.
Thanks
--
Fran�ois Desloges
[EMAIL PROTECTED]
unsubscribe: body of `unsubscribe linux-arm' to [EMAIL PROTECTED]
