Re: Include dir intl when building libcommon.a for gdb

[Joel Brobecker <brobecker at adacore dot 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