Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: gdb@sourceware.org
Subject: Re: gnulib dependency in gdbserver
Date: Wed, 25 Jun 2008 21:14:00 -0000	[thread overview]
Message-ID: <20080625211342.GF7272@adacore.com> (raw)
In-Reply-To: <20080625192247.GA29115@caradoc.them.org>

> How are you configuring?  It sounds like you're trying to share an
> object directory (same as srcdir?) for configured gdb and gdbserver;

Actually, I was configuring from separate trees.

> instead, if you build them both in separate object directories, things
> will just work out.

I think I can see why things should work for most things (things such
as the generation of the reg-*.c files for instance), but I can't
figure out things should work for gnulib.

I found the pieces that tell configure to check for memmem and use
the one in memmem if the later is not found, but I haven't found
the bits that would configure gnulib. In particular, configuring
gnulib would allow me to get stdlib.h. Should the files generated
by the gnulib configure be stored in the gdbserver directory, btw?

Just as an aside, I noticed the following two rules which look
suspicious:

signals.o: ../signals/signals.c $(server_h)
        $(CC) -c $(CPPFLAGS) $(INTERNAL_CFLAGS) $< -DGDBSERVER

memmem.o: ../gnulib/memmem.c
        $(CC) -o memmem.o -c $(CPPFLAGS) $(INTERNAL_CFLAGS) $<

Should the ../[...] be relative to $(srcdir)? Surprisingly, it
seems to work, but I don't understand why...

-- 
Joel


  reply	other threads:[~2008-06-25 21:14 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-25 19:16 Joel Brobecker
2008-06-25 19:23 ` Daniel Jacobowitz
2008-06-25 21:14   ` Joel Brobecker [this message]
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=20080625211342.GF7272@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