From: Tom Tromey <tromey@redhat.com>
To: Pedro Alves <pedro@codesourcery.com>
Cc: gdb-patches@sourceware.org, Eli Zaretskii <eliz@gnu.org>
Subject: Re: go32-nat, always a thread
Date: Sat, 09 Aug 2008 18:06:00 -0000 [thread overview]
Message-ID: <m3iquaawwy.fsf@fleche.redhat.com> (raw)
In-Reply-To: <200808091853.44771.pedro@codesourcery.com> (Pedro Alves's message of "Sat\, 9 Aug 2008 18\:53\:44 +0100")
>>>>> "Pedro" == Pedro Alves <pedro@codesourcery.com> writes:
Pedro> The build complains about not finding stdint.h. DJGPP 2.03 doesn't
Pedro> come bundled with stdint.h, but we should be picking up
Pedro> stdint.h from gdb/gnulib. There seems to be a build order
Pedro> dependency going wrong. We configure gdb/gnulib before starting
Pedro> to build gdb/, but we build gdb/ before gdb/gnulib.
Please try this patch.
Tom
ChangeLog:
2008-08-09 Tom Tromey <tromey@redhat.com>
* Makefile.in (generated_files): Add GNULIB_H.
Index: Makefile.in
===================================================================
RCS file: /cvs/src/src/gdb/Makefile.in,v
retrieving revision 1.1045
diff -u -r1.1045 Makefile.in
--- Makefile.in 8 Aug 2008 17:38:35 -0000 1.1045
+++ Makefile.in 9 Aug 2008 18:00:45 -0000
@@ -831,7 +831,7 @@
# All generated files which can be included by another file.
-generated_files = config.h observer.h observer.inc ada-lex.c
+generated_files = config.h observer.h observer.inc ada-lex.c $(GNULIB_H)
.c.o:
$(COMPILE) $<
next prev parent reply other threads:[~2008-08-09 18:06 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-08 3:39 Pedro Alves
2008-08-08 3:41 ` Pedro Alves
2008-08-08 8:01 ` Eli Zaretskii
2008-08-08 12:43 ` Daniel Jacobowitz
2008-08-08 12:47 ` Eli Zaretskii
2008-08-08 12:55 ` Daniel Jacobowitz
2008-08-09 17:54 ` Pedro Alves
2008-08-09 18:06 ` Tom Tromey [this message]
2008-08-09 18:15 ` Pedro Alves
2008-08-09 18:22 ` Daniel Jacobowitz
2008-08-09 18:55 ` Eli Zaretskii
2008-08-09 19:18 ` Mark Kettenis
2008-08-09 19:31 ` Daniel Jacobowitz
2008-08-09 21:32 ` Eli Zaretskii
2008-08-09 21:33 ` Pedro Alves
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=m3iquaawwy.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=pedro@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