From: Nick Clifton <nickc@cygnus.com>
To: binutils@sourceware.cygnus.com
Subject: Re: Linker documentation patch
Date: Fri, 07 Jan 2000 11:44:00 -0000 [thread overview]
Message-ID: <200001071944.LAA09118@elmo.cygnus.com> (raw)
Hi Guys,
I have applied the following supplimental patch to my previous patch
updating the linker documentation. This patch adds a note that
other (non-GNU) compiler drivers may not use -Wl, as the linker
command line option prefix.
It also fixes a error in the documentation of the -n command line
switch. This option does not mark the text section as read-only.
(It is marked as such by default, and the -N option can be used to
make it read-write, but -n will not set it back to being
read-only). What it does do, however, is to turn off page
alignment of the sections, so I have added this to the
documentation.
Cheers
Nick
2000-01-07 Nick Clifton <nickc@cygnus.com>
* ld.texinfo (Options): Remind users to preceed linker command
line switches with -Wl, (or whatever is appropriate) if it is
being invoked by a comnpiler driver program.
Fix description of the behaviour of the -n command line switch.
Index: ld.texinfo
===================================================================
RCS file: /cvs/binutils/binutils/ld/ld.texinfo,v
retrieving revision 1.9
diff -p -r1.9 ld.texinfo
*** ld.texinfo 2000/01/07 19:06:46 1.9
--- ld.texinfo 2000/01/07 19:34:02
*************** of multiple-letter options are accepted.
*** 230,236 ****
Note - if the linker is being invoked indirectly, via a compiler driver
(eg @samp{gcc}) then all the linker command line options should be
! prefixed by @samp{-Wl,} like this:
@smallexample
gcc -Wl,--startgroup foo.o bar.o -Wl,--endgroup
--- 230,237 ----
Note - if the linker is being invoked indirectly, via a compiler driver
(eg @samp{gcc}) then all the linker command line options should be
! prefixed by @samp{-Wl,} (or whatever is appropriate for the particular
! compiler driver) like this:
@smallexample
gcc -Wl,--startgroup foo.o bar.o -Wl,--endgroup
*************** which caused the archive member to be br
*** 558,565 ****
@kindex --nmagic
@item -n
@itemx --nmagic
! Set the text segment to be read only, and mark the output as
! @code{NMAGIC} if possible.
@kindex -N
@kindex --omagic
--- 559,566 ----
@kindex --nmagic
@item -n
@itemx --nmagic
! Turn off page alignment of sections, and mark the output as
! @code{NMAGIC} if possible.
@kindex -N
@kindex --omagic
WARNING: multiple messages have this Message-ID
From: Nick Clifton <nickc@cygnus.com>
To: binutils@sourceware.cygnus.com
Subject: Re: Linker documentation patch
Date: Sat, 01 Apr 2000 00:00:00 -0000 [thread overview]
Message-ID: <200001071944.LAA09118@elmo.cygnus.com> (raw)
Message-ID: <20000401000000.L5kkq1gtuNirF_SEbcctMCyOPUg_kyKZ8NT0eo1bBGg@z> (raw)
Hi Guys,
I have applied the following supplimental patch to my previous patch
updating the linker documentation. This patch adds a note that
other (non-GNU) compiler drivers may not use -Wl, as the linker
command line option prefix.
It also fixes a error in the documentation of the -n command line
switch. This option does not mark the text section as read-only.
(It is marked as such by default, and the -N option can be used to
make it read-write, but -n will not set it back to being
read-only). What it does do, however, is to turn off page
alignment of the sections, so I have added this to the
documentation.
Cheers
Nick
2000-01-07 Nick Clifton <nickc@cygnus.com>
* ld.texinfo (Options): Remind users to preceed linker command
line switches with -Wl, (or whatever is appropriate) if it is
being invoked by a comnpiler driver program.
Fix description of the behaviour of the -n command line switch.
Index: ld.texinfo
===================================================================
RCS file: /cvs/binutils/binutils/ld/ld.texinfo,v
retrieving revision 1.9
diff -p -r1.9 ld.texinfo
*** ld.texinfo 2000/01/07 19:06:46 1.9
--- ld.texinfo 2000/01/07 19:34:02
*************** of multiple-letter options are accepted.
*** 230,236 ****
Note - if the linker is being invoked indirectly, via a compiler driver
(eg @samp{gcc}) then all the linker command line options should be
! prefixed by @samp{-Wl,} like this:
@smallexample
gcc -Wl,--startgroup foo.o bar.o -Wl,--endgroup
--- 230,237 ----
Note - if the linker is being invoked indirectly, via a compiler driver
(eg @samp{gcc}) then all the linker command line options should be
! prefixed by @samp{-Wl,} (or whatever is appropriate for the particular
! compiler driver) like this:
@smallexample
gcc -Wl,--startgroup foo.o bar.o -Wl,--endgroup
*************** which caused the archive member to be br
*** 558,565 ****
@kindex --nmagic
@item -n
@itemx --nmagic
! Set the text segment to be read only, and mark the output as
! @code{NMAGIC} if possible.
@kindex -N
@kindex --omagic
--- 559,566 ----
@kindex --nmagic
@item -n
@itemx --nmagic
! Turn off page alignment of sections, and mark the output as
! @code{NMAGIC} if possible.
@kindex -N
@kindex --omagic
next reply other threads:[~2000-01-07 11:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-01-07 11:44 Nick Clifton [this message]
2000-04-01 0:00 ` Nick Clifton
-- strict thread matches above, loose matches on Subject: below --
2000-01-07 11:31 Nick Clifton
2000-01-07 11:07 Nick Clifton
2000-01-07 11:26 ` Ian Lance Taylor
2000-04-01 0:00 ` Nick Clifton
1999-07-01 0:00 Nick Clifton
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200001071944.LAA09118@elmo.cygnus.com \
--to=nickc@cygnus.com \
--cc=binutils@sourceware.cygnus.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).