Re: why 'The legacy aout build' was removed from current ?

1999-12-11 Thread David O'Brien
On Thu, Dec 09, 1999 at 10:23:40AM +0200, Sheldon Hearn wrote: Are you sure? Any a.out binaries for FreeBSD are going to be desgined to work with 3.x or older. Why??? A.out runs just fine on 4.0-R, and had better on 5.0-R. So producing a.out libraries for CURRENT is silly. :-) Nope.

Re: why 'The legacy aout build' was removed from current ?

1999-12-11 Thread Garrett Wollman
On Sat, 11 Dec 1999 13:09:02 -0800, "David O'Brien" [EMAIL PROTECTED] said: [Attribution lost.] So producing a.out libraries for CURRENT is silly. :-) Nope. You really need to think about the ISV's. Why do you think Netscape is still a.out? ISV's want to produce one binary that runs

Re: why 'The legacy aout build' was removed from current ?

1999-12-10 Thread Daniel C. Sobral
Chuck Robey wrote: This isn't taking the execution of aout binaries out, just stopping a world build. This is only going to stop 3rd party developers from making a 4.0 aout platform to create *more* aout binaries. They'll probably hang on for dear life on 2.2, just as long as they can.

Re: why 'The legacy aout build' was removed from current ?

1999-12-10 Thread Chuck Robey
On Fri, 10 Dec 1999, Daniel C. Sobral wrote: What Motoyuki-san is complaining about is that applications that depend on a.out libraries will suffer. Alas, I don't think that's the case, since all these libraries are (or ought to be, anyway) in compat. Looking at copious examples from

Re: why 'The legacy aout build' was removed from current ?

1999-12-09 Thread Motoyuki Konno
Hi, YAMAMOTO Shigeru [EMAIL PROTECTED]wrote: In a log of @src/Makefile, revision 1.230, o The legacy aout build has been removed. Why 'The legacy aout build' was removed from current? Are we now living in the TRUE ELF world? I also wonder why a.out support was removed from -current

Re: why 'The legacy aout build' was removed from current ?

1999-12-09 Thread Sheldon Hearn
On Thu, 09 Dec 1999 17:00:50 +0900, Motoyuki Konno wrote: I think we don't need "a.out world" any more, but a.out support (a.out lib/shared lib, etc.) is still needed. Some commercial programs such as Netscape are in a.out only, so we still have to make a.out binaries. Are you sure? Any

Re: why 'The legacy aout build' was removed from current ?

1999-12-09 Thread Marcel Moolenaar
YAMAMOTO Shigeru wrote: In a log of @src/Makefile, revision 1.230, o The legacy aout build has been removed. Why 'The legacy aout build' was removed from current? There's no point in building legacy a.out stuff from -current sources. The result has nothing to do with legacy but only

Re: why 'The legacy aout build' was removed from current ?

1999-12-09 Thread Marcel Moolenaar
Motoyuki Konno wrote: I also wonder why a.out support was removed from -current. a.out support has not been removed. We just don't do any legacy a.out building. I think we don't need "a.out world" any more, but a.out support (a.out lib/shared lib, etc.) is still needed. For this, the

Re: why 'The legacy aout build' was removed from current ?

1999-12-09 Thread Marcel Moolenaar
Motoyuki Konno wrote: I also wonder why a.out support was removed from -current. a.out support has not been removed. We just don't do any legacy a.out building. I think we don't need "a.out world" any more, but a.out support (a.out lib/shared lib, etc.) is still needed. For this, the

Re: why 'The legacy aout build' was removed from current ?

1999-12-09 Thread Andrzej Bialecki
On Thu, 9 Dec 1999, Marcel Moolenaar wrote: Please see Netscape plugin port (ports/www/flashplugin) to find out why we still have to need a.out support. The port has nothing to do with building a legacy a.out world and consequently works fine (yes, I tested it :-) Not really. You have

Re: why 'The legacy aout build' was removed from current ?

1999-12-09 Thread Marcel Moolenaar
Andrzej Bialecki wrote: On Thu, 9 Dec 1999, Marcel Moolenaar wrote: Please see Netscape plugin port (ports/www/flashplugin) to find out why we still have to need a.out support. The port has nothing to do with building a legacy a.out world and consequently works fine (yes, I

Re: why 'The legacy aout build' was removed from current ?

1999-12-09 Thread Andrzej Bialecki
On Thu, 9 Dec 1999, Marcel Moolenaar wrote: Andrzej Bialecki wrote: On Thu, 9 Dec 1999, Marcel Moolenaar wrote: Please see Netscape plugin port (ports/www/flashplugin) to find out why we still have to need a.out support. The port has nothing to do with building a legacy

Re: why 'The legacy aout build' was removed from current ?

1999-12-09 Thread Marcel Moolenaar
Andrzej Bialecki wrote: 1. extract /usr/src/lib (distribution files: src/slib.??) 2. cd /usr/src/lib/csu/i386 3. make depend 4. make OBJFORMAT=aout clean all install True. But this adds a dependency for this port on the src/lib tree. I was thinking about average people that have

Re: why 'The legacy aout build' was removed from current ?

1999-12-09 Thread Daniel C. Sobral
Motoyuki Konno wrote: I think we don't need "a.out world" any more, but a.out support (a.out lib/shared lib, etc.) is still needed. Some commercial programs such as Netscape are in a.out only, so we still have to make a.out binaries. Please see Netscape plugin port

Re: why 'The legacy aout build' was removed from current ?

1999-12-09 Thread Chuck Robey
On Thu, 9 Dec 1999, Daniel C. Sobral wrote: Motoyuki Konno wrote: I think we don't need "a.out world" any more, but a.out support (a.out lib/shared lib, etc.) is still needed. Some commercial programs such as Netscape are in a.out only, so we still have to make a.out binaries.

why 'The legacy aout build' was removed from current ?

1999-12-08 Thread YAMAMOTO Shigeru
In a log of @src/Makefile, revision 1.230, o The legacy aout build has been removed. Why 'The legacy aout build' was removed from current? Are we now living in the TRUE ELF world? Thanks, --- YAMAMOTO ShigeruInternet Initiative Japan Inc. [EMAIL PROTECTED