From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Ulrich Weigand <uweigand@de.ibm.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [patch] testsuite: gdb compile failed, gcc: -soname: linker input file unused because linking not done
Date: Tue, 12 Oct 2010 18:13:00 -0000 [thread overview]
Message-ID: <20101012181322.GA8793@host1.dyn.jankratochvil.net> (raw)
In-Reply-To: <201010121756.o9CHugRb031064@d12av02.megacenter.de.ibm.com>
On Tue, 12 Oct 2010 19:56:42 +0200, Ulrich Weigand wrote:
> Jan Kratochvil wrote:
> > gdb/testsuite/
> > 2010-10-11 Jan Kratochvil <jan.kratochvil@redhat.com>
> >
> > * gdb.base/break-interp.exp: Use ldlags for linking flags.
> > * gdb.base/prelink.exp: Likewise.
> > * gdb.base/solib-nodir.exp: Likewise.
> > * lib/gdb.exp (gdb_compile) <*-*-openbsd*>
> > (gdb_compile) <shlib_load>: Use ldlags for linking flags.
> > * lib/prelink-support.exp (build_executable_own_libs): Likewise.
>
> This looks good to me.
Checked-in:
http://sourceware.org/ml/gdb-cvs/2010-10/msg00076.html
Thanks,
Jan
prev parent reply other threads:[~2010-10-12 18:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-11 21:33 Jan Kratochvil
2010-10-12 17:56 ` Ulrich Weigand
2010-10-12 18:13 ` Jan Kratochvil [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=20101012181322.GA8793@host1.dyn.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=uweigand@de.ibm.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