From: Tom Tromey <tromey@redhat.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: gdb-patches@sourceware.org, Sergio Durigan <sdurigan@redhat.com>
Subject: Re: [patch 2/2] Do not build libgdb.a by default
Date: Wed, 21 Dec 2011 19:18:00 -0000 [thread overview]
Message-ID: <m37h1pdee4.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20111221114720.GC25652@host2.jankratochvil.net> (Jan Kratochvil's message of "Wed, 21 Dec 2011 12:47:20 +0100")
>>>>> "Jan" == Jan Kratochvil <jan.kratochvil@redhat.com> writes:
Jan> with the default build of only "gdb" after [patch 1/2] it no longer
Jan> makes much sense to build *.o -> libgdb.a and then libgdb.a -> gdb.
Jan> Use *.o files directly for gdb. libgdb.a build is still supported
Jan> for its rare users, it is just not built by the default rule.
Thanks. This seems like a sensible compromise approach to me.
I am in favor of it.
Jan> By no longer using *.a some duplicate files have started to break
Jan> ld. Patch removes these duplicities. I believe some
Jan> configurations get broken this way but their fix will be easy.
Turn over a rock...
Tom
next prev parent reply other threads:[~2011-12-21 19:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-21 11:58 Jan Kratochvil
2011-12-21 13:12 ` Joel Brobecker
2011-12-21 14:01 ` Pierre Muller
2011-12-21 14:24 ` Joel Brobecker
2011-12-21 14:27 ` Pierre Muller
2011-12-21 19:18 ` Tom Tromey [this message]
2012-01-02 2:32 ` [commit] " Jan Kratochvil
2012-01-02 13:40 ` Pedro Alves
2012-01-02 14:02 ` [patch] Put solib-target.o back to COMMON_OBS [Re: [patch 2/2] Do not build libgdb.a by default] Jan Kratochvil
2012-01-02 17:12 ` Pedro Alves
2012-01-02 17:19 ` Jan Kratochvil
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=m37h1pdee4.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=sdurigan@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