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
The N option is used to statically link a program. What manpage were you
looking at?
On Sun, 22 Sep 1996, Dale Scheetz wrote:
dwarfOn Sat, 21 Sep 1996, llucius wrote:
dwarf
dwarf I'm sorry it was the -N link option that causes ae to be linked
dwarf statically. Is it really necessary to use the
On Sun, 22 Sep 1996, Christoph Lameter wrote:
The N option is used to statically link a program. What manpage were you
looking at?
The man page is for ld. The gcc man page says ld is used to link.
The gcc man page also says that -static is the proper option for creating
static linked
On Sun, 22 Sep 1996, Dale Scheetz wrote:
On Sun, 22 Sep 1996, Christoph Lameter wrote:
The N option is used to statically link a program. What manpage were you
looking at?
The man page is for ld. The gcc man page says ld is used to link.
The gcc man page also says that -static is the
Here's something I just found in chapter 4.1 of the policy manual:
The -N flag should not be used. On a.out systems it may have been
useful for some very small binaries, but for ELF it has no good
effect.
I wish it explained why it shouldn't be used so we could understand it
rather
'Dale Scheetz wrote:'
On Sun, 22 Sep 1996, Christoph Lameter wrote:
The N option is used to statically link a program. What manpage were you
looking at?
The man page is for ld. The gcc man page says ld is used to link.
The gcc man page also says that -static is the proper option for creating
On Sun, 22 Sep 1996, Dale Scheetz wrote:
On Sun, 22 Sep 1996, Christoph Lameter wrote:
The N option is used to statically link a program. What manpage were you
looking at?
The man page is for ld. The gcc man page says ld is used to link.
The gcc man page also says that -static is the
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
Chris Fearnley:
It isn't relevant. I strongly remember that -N is for static linking
of a.out binaries.
You remember wrong.
The usual a.out executable file format consists of three parts:
a 1 kB header, one or more 4 kB code pages, and one more 4 kB
data pages. Thus, the minimum size is 9
Thanks for all the discussion guys. I have rebuilt ae without the -N
linker option. It seems to work as well as it ever did, so I will release
it as soon as I can get to master.
Thanks again for all the pointers,
Dwarf
--
aka
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
Package: ae
Version: 962-9
1) debian/rules uses dpkg-shlibdeps as you normally would, but
for ae it's not necessary since ae is compiled statically.
Unfortunately, dpkg-shlibdeps does not handle this case.
The following patch corrects the problem:
diff -ruN orig/ae-962/debian/rules
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
13 matches
Mail list logo
