> I guess it's possible to change over entirely. That would
> mean we would loase a.out support because the GNU tools are
> becoming incapable of supporting a.out ("all machines we
> run on are Linux machines" syndrome).
>
> If we really wanted to avoid problems like this in the future,
> we'd just scrap FreeBSD entirely, and go to Linux, a bit at a
> time, starting with ELF, then DWARF2 exceptions, and then
> the Linux ABI instead of the FreeBSD ABI, and then all of Linux,
> a piece at a time.
At the risk of being yelled at, I have a question: Why do we still need to
support a.out? I know that a lot of people MIGHT still have some a.out
binaries lying around, but FreeBSD's default binary format has been ELF
for 3 or 4 years (Since 3.0-3.1 I believe). I'm not saying that we should
entirely switch over to the regular gnu toolchain, but is it really
necessary to keep supporting a.out? Just my $0.02
Ken
>
> PS: If I sound annoyed, it's because it's sometimes annoying
> to have your toolchain controlled by someone with an interest
> in a product that competes with yours; that works for people
> competing with Microsoft products on Microsoft platforms with
> a need to use Microsoft tools, and it applies to Cygnus being
> owned by RedHat and them controlling the FreeBSD tools.
>
> -- Terry
>
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-current" in the body of the message
>
>
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
