From: Joel Brobecker <brobecker@adacore.com>
To: gdb@sourceware.org
Subject: gnulib dependency in gdbserver
Date: Wed, 25 Jun 2008 19:16:00 -0000 [thread overview]
Message-ID: <20080625191621.GI3700@adacore.com> (raw)
I just realized that gdbserver now depends on ../gnulib. The problem
is ../gnulib has been configured by and for gdb, not gdbserver. So
if one wants to just build gdbserver, or if the host/target configuration
for gdb and gdbserver are different, then things may not work.
In my particular case, I'm working on a GDB hosted on Solaris cross
ppc-lynxos, and then cross-build gdbserver to run on ppc-lynxos.
I get an error because the stdint.h file doesn't work (SIZE_MAX
is missing).
I don't see any other way but making an additional copy of gnulib
inside gdbserver. I really hate the idea; even though it seems that
this is the way that the project was designed to be used, it means
that we have to be careful to update two copies if a file is
duplicated twice...
Any suggestion?
Thanks,
--
Joel
next reply other threads:[~2008-06-25 19:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-25 19:16 Joel Brobecker [this message]
2008-06-25 19:23 ` Daniel Jacobowitz
2008-06-25 21:14 ` Joel Brobecker
2008-06-25 21:58 ` Daniel Jacobowitz
2008-06-25 22:15 ` Joel Brobecker
2008-06-25 23:09 ` Joel Brobecker
2008-06-26 2:09 ` Daniel Jacobowitz
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=20080625191621.GI3700@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb@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