Re: Fixing a.out compatibility

2000-12-29 Thread Nate Williams
> It seems feasable to generate a new binary on a recent or an old patched > FreeBSD version. The question is which is better. I think the newer > the better. Otherwise, who is going to build the 2.2.8-stable box > to make this one binary? I've already built a binary on 4.2-release > that work

Re: Fixing a.out compatibility

2000-12-26 Thread Stephen McKay
[Noted that you don't like being cc:'d, David. On the other hand, I like to be kept in the cc: list.] On Tuesday, 26th December 2000, "David O'Brien" wrote: >On Wed, Dec 27, 2000 at 02:01:24AM +1000, Stephen McKay wrote: >> I'll try to summarise the position so far: >> >> 1) Legacy a.out execu

Re: Fixing a.out compatibility

2000-12-26 Thread David O'Brien
On Wed, Dec 27, 2000 at 02:01:24AM +1000, Stephen McKay wrote: > I'll try to summarise the position so far: > > 1) Legacy a.out executable support is broken for a subset (size unknown) > of such executables. Define "legacy". I have been speaking specifically about FreeBSD 2.2 support. That jus

Fixing a.out compatibility

2000-12-26 Thread Stephen McKay
I'll try to summarise the position so far: 1) Legacy a.out executable support is broken for a subset (size unknown) of such executables. 2) We can ignore this or repair this. 3) We can build a new binary or just look around on old 3.x CDs until we find one that works. 4) We can generate a work