From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: gdb-patches@sourceware.org
Subject: [commit] [patch 1/2] Fix linking on non-x86* after libgdb.a removal
Date: Mon, 09 Jan 2012 15:23:00 -0000 [thread overview]
Message-ID: <20120109152205.GA26498@host2.jankratochvil.net> (raw)
In-Reply-To: <20120104194132.GA23751@host2.jankratochvil.net>
On Wed, 04 Jan 2012 20:41:32 +0100, Jan Kratochvil wrote:
> 2012-01-04 Jan Kratochvil <jan.kratochvil@redhat.com>
>
> Partially fix duplicate .o files after omitting libbfd.a.
> * config/alpha/alpha-osf3.mh (NATDEPFILES): Remove solib.o.
> * config/i386/nbsdaout.mh (NATDEPFILES): Remove solib.o.
> * config/i386/obsdaout.mh (NATDEPFILES): Remove solib.o.
> * config/m68k/nbsdaout.mh (NATDEPFILES): Remove solib.o.
> * config/m68k/obsd.mh (NATDEPFILES): Remove solib.o.
> * config/powerpc/aix.mh (NATDEPFILES): Remove xcoffread.o.
> * config/vax/nbsdaout.mh (NATDEPFILES): Remove solib.o.
This one was easy/clear and it makes the [patch 2/2] easier to prepare.
Checked in:
http://sourceware.org/ml/gdb-cvs/2012-01/msg00090.html
Thanks+sorry,
Jan
prev parent reply other threads:[~2012-01-09 15:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-04 19:42 Jan Kratochvil
2012-01-09 15:23 ` 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=20120109152205.GA26498@host2.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=gdb-patches@sourceware.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).