public inbox for
 help / color / mirror / Atom feed
From: Mark Wielaard <>
Subject: Re: [PATCH] tests: robustify against unstripped libc_nonshared.a
Date: Wed, 09 Aug 2017 18:47:00 -0000	[thread overview]
Message-ID: <20170809184742.GB2645@stream> (raw)
In-Reply-To: <>

On Tue, Aug 08, 2017 at 07:06:16PM +0300, Dmitry V. Levin wrote:
> When glibc's libc_nonshared.a contains objects with debug info,
> this debug info is leaked into every output file produced by gcc.
> Change to use "gcc -s" instead of plain "gcc"
> for producing objects without debug info.

Thanks, I didn't know about gcc -s, but it is ideal for this testcase.
Committed to master with a ChangeLog entry.



      reply	other threads:[~2017-08-09 18:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-08 16:06 Dmitry V. Levin
2017-08-09 18:47 ` Mark Wielaard [this message]

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20170809184742.GB2645@stream \ \ \

* 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).