Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Steve Ellcey <sellcey@cavium.com>
Cc: gdb@sourceware.org
Subject: Re: prelink -u on aarch64 question
Date: Wed, 26 Jul 2017 19:44:00 -0000	[thread overview]
Message-ID: <20170726194415.GA12866@host1.jankratochvil.net> (raw)
In-Reply-To: <201707261737.v6QHbkDv026294@sellcey-dt.caveonetworks.com>

On Wed, 26 Jul 2017 19:37:46 +0200, Steve Ellcey wrote:
> I was wondering if anyone could tell me anything about prelink on
> aarch64?

prelink probably is not supported on aarch64 at all, I have not checked.

But even on x86* prelink has been discontinued - on its "core" distro:
	Don't enable prelink by default in Fedora
	https://pagure.io/fesco/issue/1183

I think at least the prelink testfile gdb.base/break-interp.exp could be even
disabled by default nowadays (saying that as author of the testfile) as even
when it PASSes it is very slow given the huge number of combinations it does
test.


Jan


  reply	other threads:[~2017-07-26 19:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-26 17:37 Steve Ellcey
2017-07-26 19:44 ` Jan Kratochvil [this message]
2017-07-26 20:05   ` Steve Ellcey

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=20170726194415.GA12866@host1.jankratochvil.net \
    --to=jan.kratochvil@redhat.com \
    --cc=gdb@sourceware.org \
    --cc=sellcey@cavium.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