mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] Including valgrind in the configuration doesn't trigger an un-optimized build of glibc.
Date: Tue, 27 Mar 2018 09:33:56 +0200	[thread overview]
Message-ID: <20180327073356.6m6kgyb2whrael6y@pengutronix.de> (raw)
In-Reply-To: <2D79272AFFD75A4392ED2D3EF16D3B53A8999B@mdcxch20.na.ops.local>

Hi,

On Mon, Mar 26, 2018 at 07:03:21AM -0500, Crim, Jason wrote:
> I'd tried moving over the root-debug versions of the referenced files, and
> was still hitting the error.  That's when I'd found the post referencing
> the optimization levels.  I'll take a look at getting the nfs-root running
> when I've got some time.

Hmm, strage, The only problems I've seen are with stripped binaries. Which
toolchain are you using?

Michael

-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de

  reply	other threads:[~2018-03-27  7:33 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-22 17:38 Crim, Jason
2018-03-26  6:30 ` Michael Olbrich
2018-03-26 12:03   ` Crim, Jason
2018-03-27  7:33     ` Michael Olbrich [this message]
2018-03-27 11:54       ` Crim, Jason
2018-03-28 10:01 Andrej.Gantvorg
2018-03-28 15:43 ` Crim, Jason
2018-03-29  9:20   ` Michael Olbrich
2018-04-05 19:41     ` Crim, Jason
2018-04-09  8:41       ` Michael Olbrich
2018-04-09 12:13         ` Crim, Jason
2018-04-09 13:49           ` Michael Olbrich

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=20180327073356.6m6kgyb2whrael6y@pengutronix.de \
    --to=m.olbrich@pengutronix.de \
    --cc=ptxdist@pengutronix.de \
    /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