Re: Bug#4550: Build of "ae" fails since it's statically linked
firstname.lastname@example.org (llucius) wrote on 22.09.96 in <Pine.3.89.9609221533.A27976-0100000@mill2.MillComm.COM>:
> On Sun, 22 Sep 1996, Dale Scheetz wrote:
> > On Sat, 21 Sep 1996, llucius wrote:
> > > I'm sorry it was the "-N" link option that causes "ae" to be linked
> > > statically. Is it really necessary to use the option?
> > >
> > Well, my man page says:
> > -N specifies readable and writable text and data sec-
> > tions. If the output format supports Unix style
> > magic numbers, the output is marked as OMAGIC.
> > When you use the `-N' option, the linker does not
> > page-align the data segment.
> > none of which seems to have anything to do with static vs shared
> > libraries.
> It was never explained to me either why it does this, but it seems to be
> a known (and expected) action.
I remember this was discussed on the linux-gcc list some time ago. The
above explanation is ok for a.out, and was primarily used to build small
programs (the page-alignment bit). That's probably why ae used it. Under
ELF, this part doesn't work anyway; I *think* that you get a static link
because of the "writable text" part.
Anyway, the consensus seems to be that -N is completely obsolete under