In article <local.mail.freebsd-current/15359.920308...@critter.freebsd.dk> you 
write:
>In message <199903011709.jaa48...@vashon.polstra.com>, John Polstra writes:
>>In article <31122.920241...@zippy.cdrom.com>,
>>Jordan K. Hubbard <j...@zippy.cdrom.com> wrote:
>>> 
>>> I'd personally be happy with an egcs that just did sensible things
>>> with ELF,
>>
>>Me too.  We _must_ not let a.out become a ball and chain.  We have
>>stressed over and over all along that we were not going to become a
>>dual-object-format OS.  That means we _must_ be willing to abandon
>>a.out support for new code.  We will keep the legacy a.out libraries
>>for old applications to link against, but we don't have to keep the
>>ability to generate new ones.  To do so would hold us back (_is_
>>holding us back) with very little to show for it.
>
>Wouldn't the first logical step be to stop generating the a.out libs
>in make world, and check in the "final version" like with the rest
>of the compat libs ?

How about getting profiling working for ELF kernels before
before completely abandoning a.out? 
--
Jonathan


To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message

Reply via email to