From: Kevin Buettner <kevinb@redhat.com>
To: gdb-patches@sources.redhat.com, Alexandre Oliva <aoliva@redhat.com>
Subject: Re: cope with varying prelink base addresses
Date: Tue, 28 Feb 2006 01:50:00 -0000 [thread overview]
Message-ID: <20060227163051.47456664@ironwood.lan> (raw)
In-Reply-To: <ork6bljrjt.fsf@free.oliva.athome.lsd.ic.unicamp.br>
On Fri, 24 Feb 2006 01:42:46 -0300
Alexandre Oliva <aoliva@redhat.com> wrote:
> On Feb 23, 2006, Daniel Jacobowitz <drow@false.org> wrote:
>
> > On Thu, Feb 23, 2006 at 05:18:11PM -0300, Alexandre Oliva wrote:
> >> On Feb 20, 2006, Daniel Jacobowitz <drow@false.org> wrote:
> >>
> >> > The testcase behaves on Solaris, where there's no prelink binary. I'm
> >> > a little worried about it being noisy where -shared doesn't work,
> >> > and with various non-GCC tools. Maybe move the gcc_compiled check
> >> > further up?
> >>
> >> Isn't gcc_compiled only set when you actually try to compile
> >> something? That was my impression when I tried the test earlier,
> >> before I submitted the first version of this patch.
>
> > Once upon a time get_compiler_info needed $binfile. Now the argument
> > is ignored, so you can move get_compiler_info up before the
> > compilation.
>
> Aha! Ok, this should work, then (tested on GNU/Linux/x86_64)
>
> Ok to install?
Yes, please commit this patch.
Kevin
prev parent reply other threads:[~2006-02-27 23:31 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-08 5:35 Alexandre Oliva
2006-02-08 6:25 ` Eli Zaretskii
2006-02-10 0:15 ` Alexandre Oliva
2006-02-08 21:40 ` Mark Kettenis
2006-02-10 0:09 ` Alexandre Oliva
2006-02-10 1:42 ` Daniel Jacobowitz
2006-02-13 19:03 ` Alexandre Oliva
2006-02-14 0:56 ` Kevin Buettner
2006-02-14 2:08 ` Daniel Jacobowitz
2006-02-14 18:40 ` Alexandre Oliva
2006-02-14 18:53 ` Mark Kettenis
2006-02-20 18:16 ` Alexandre Oliva
2006-02-20 21:49 ` Mark Kettenis
2006-02-20 17:37 ` Daniel Jacobowitz
2006-02-20 17:43 ` Daniel Jacobowitz
2006-02-23 20:22 ` Alexandre Oliva
2006-02-23 20:53 ` Daniel Jacobowitz
2006-02-24 7:42 ` Alexandre Oliva
2006-02-28 1:50 ` Kevin Buettner [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:
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=20060227163051.47456664@ironwood.lan \
--to=kevinb@redhat.com \
--cc=aoliva@redhat.com \
--cc=gdb-patches@sources.redhat.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