From: Joel Brobecker <brobecker@adacore.com>
To: Pedro Alves <pedro@codesourcery.com>
Cc: gdb-patches@sourceware.org, Yao Qi <yao@codesourcery.com>
Subject: Re: Include dir intl when building libcommon.a for gdb
Date: Fri, 04 Mar 2011 05:46:00 -0000 [thread overview]
Message-ID: <20110304054550.GB30306@adacore.com> (raw)
In-Reply-To: <201103021243.58226.pedro@codesourcery.com>
> > In the meantime, one proposed easy way out that doesn't destroy
> > all the work that has been done so far is to add all the -I
> > directories regardless of who we build libcommon for. I think
> > it makes sense from a conceptual point of view, and it will also
> > help us avoid maintaining 2 lists. But maybe it doesn't work for
> > practical reasons.
>
> gdbserver does not depend on bfd. It's wrong to leave it in
> the include path. gdbserver is not using gnulib either (memmem.o hack
> doesn't count),
Coming back to this, this makes me ask myself: If GDBserver does
not use bfd, for instance, and we have code in common/ that needs
bfd, does it not mean that we have code in common/ that is, well,
not common between GDB and GDBserver??? IMO, we do not want that.
--
Joel
next prev parent reply other threads:[~2011-03-04 5:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-01 6:22 Yao Qi
2011-03-02 12:14 ` Joel Brobecker
2011-03-02 12:34 ` Kai Tietz
2011-03-04 5:55 ` Joel Brobecker
2011-03-02 12:44 ` Pedro Alves
2011-03-04 5:46 ` Joel Brobecker [this message]
2011-03-02 13:12 ` Mark Kettenis
2011-03-02 14:46 ` Yao Qi
2011-03-02 15:32 ` Pedro Alves
2011-03-03 3:15 ` Yao Qi
2011-03-03 5:40 ` Yao Qi
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=20110304054550.GB30306@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=pedro@codesourcery.com \
--cc=yao@codesourcery.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