From: "Pierre Muller" <pierre.muller@ics-cnrs.unistra.fr>
To: "'Joel Brobecker'" <brobecker@adacore.com>,
"'gdb-patches'" <gdb-patches@sourceware.org>
Subject: RE: [patch 2/2] Do not build libgdb.a by default
Date: Wed, 21 Dec 2011 14:01:00 -0000 [thread overview]
Message-ID: <004001ccbfe6$f747e890$e5d7b9b0$@muller@ics-cnrs.unistra.fr> (raw)
In-Reply-To: <20111221125919.GJ23376@adacore.com>
> -----Message d'origine-----
> De : gdb-patches-owner@sourceware.org [mailto:gdb-patches-
> owner@sourceware.org] De la part de Joel Brobecker
> Envoyé : mercredi 21 décembre 2011 13:59
> À : Jan Kratochvil
> Cc : gdb-patches@sourceware.org; Sergio Durigan
> Objet : Re: [patch 2/2] Do not build libgdb.a by default
>
> > with the default build of only "gdb" after [patch 1/2] it no longer
> > makes much sense to build *.o -> libgdb.a and then libgdb.a -> gdb.
> > Use *.o files directly for gdb. libgdb.a build is still supported for
> > its rare users, it is just not built by the default rule.
>
> Just wondering, who are the rare users? insight?
We (Free Pascal core team) are still using libgdb.a library
to statically link GDB into our "home made" IDE with
GDB debugger integrated...
I don't mind much needed to explicitly ask for libgdb.a library,
but please leave the rule present!
Pierre Muller
GDB pascal language maintainer
and Free Pascal compiler core developer
next prev parent reply other threads:[~2011-12-21 13:47 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 [this message]
2011-12-21 14:24 ` Joel Brobecker
2011-12-21 14:27 ` Pierre Muller
2011-12-21 19:18 ` Tom Tromey
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='004001ccbfe6$f747e890$e5d7b9b0$@muller@ics-cnrs.unistra.fr' \
--to=pierre.muller@ics-cnrs.unistra.fr \
--cc=brobecker@adacore.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