public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: "Ronald F. Guilmette" <rfg@monkeys.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org
Subject: Re: c/2678: gcc/g++ should stick compilation options into the .o file
Date: Mon, 30 Apr 2001 10:26:00 -0000	[thread overview]
Message-ID: <20010430172601.31387.qmail@sourceware.cygnus.com> (raw)

The following reply was made to PR c/2678; it has been noted by GNATS.

From: "Ronald F. Guilmette" <rfg@monkeys.com>
To: "Joseph S. Myers" <jsm28@cam.ac.uk>
Cc: gcc-gnats@gcc.gnu.org, pedwards@disaster.jaj.com
Subject: Re: c/2678: gcc/g++ should stick compilation options into the .o file 
Date: Mon, 30 Apr 2001 10:21:12 -0700

 In message <Pine.LNX.4.32.0104301813300.17624-100000@kern.srcf.societies.cam.ac
 .uk>, you wrote:
 
 >On 30 Apr 2001, Ronald F. Guilmette wrote:
 >
 >>  As I noted, they can always run `strip' after the compile, if the extra
 >>  info really bothers them.
 >
 >But does "strip" (without other options) remove these sections?  It
 >doesn't (binutils 2.11.90.0.6) remove .comment and .note; for that reason,
 >Debian has modified "install -s" to pass --remove-section=.comment
 >--remove-section=.note to strip.
 
 a)  It's no big deal to also supply --remove-section=.comment on the
     strip command line.
 
 b)  In practice, nobody will give a damn about the presence or absense of
     this extra information anyway.
 


             reply	other threads:[~2001-04-30 10:26 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-30 10:26 Ronald F. Guilmette [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-11-05  9:16 Wolfgang Bangerth
2002-11-05  9:08 bangerth
2002-11-05  9:06 Phil Edwards
2002-11-05  7:46 Wolfgang Bangerth
2001-05-07 16:56 Phil Edwards
2001-04-30 17:36 Ronald F. Guilmette
2001-04-30 17:16 Phil Edwards
2001-04-30  9:46 Ronald F. Guilmette
2001-04-30  2:36 Phil Edwards
2001-04-30  2:16 Ronald F. Guilmette
2001-04-29 20:06 Phil Edwards
2001-04-29 11:56 Ronald F. Guilmette
2001-04-29  5:46 Phil Edwards
2001-04-29  5:16 Phil Edwards
2001-04-29  4:16 Phil Edwards
2001-04-28 13:46 rfg

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=20010430172601.31387.qmail@sourceware.cygnus.com \
    --to=rfg@monkeys.com \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@gcc.gnu.org \
    /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).