From: Tom Tromey <tromey@redhat.com>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: drow@false.org, gdb@sourceware.org
Subject: Re: Automatic dependency tracking
Date: Sat, 28 Jun 2008 19:31:00 -0000 [thread overview]
Message-ID: <m3k5g9l5ll.fsf@fleche.redhat.com> (raw)
In-Reply-To: <200806281920.m5SJKAQI008684@brahms.sibelius.xs4all.nl> (Mark Kettenis's message of "Sat\, 28 Jun 2008 21\:20\:10 +0200 \(CEST\)")
>>>>> "Mark" == Mark Kettenis <mark.kettenis@xs4all.nl> writes:
Mark> I'd like to avoid this if we can. On OpenBSD we include GDB in the
Mark> base system, but we don't have GNU make. This'll mean I'll have to do
Mark> extensive makefile hackary whenever I import a new version of GDB in
Mark> the OpenBSD tree. I'd rather spend that time on hacking more useful
Mark> stuff.
How does OpenBSD handle this for GCC?
Or does the OpenBSD gcc maintainer also rewrite the Makefiles?
Ugh.
FWIW, rewriting the patch I sent to avoid GNU make is likely to be
pretty fiddly & painful.
Tom
next prev parent reply other threads:[~2008-06-28 19:31 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200806152203.14626.pedro@codesourcery.com>
[not found] ` <u3anel69s.fsf@gnu.org>
[not found] ` <20080616012617.GA8944@caradoc.them.org>
[not found] ` <g35201$2uf$2@ger.gmane.org>
[not found] ` <m33an413yx.fsf@fleche.redhat.com>
2008-06-25 18:29 ` Daniel Jacobowitz
2008-06-25 19:30 ` Andreas Schwab
2008-06-25 21:35 ` Stan Shebs
2008-06-26 0:08 ` Tom Tromey
2008-06-26 1:47 ` Joel Brobecker
2008-06-26 9:48 ` Andrew STUBBS
2008-06-26 17:30 ` Tom Tromey
2008-06-27 10:23 ` Andrew STUBBS
2008-06-27 14:03 ` Daniel Jacobowitz
2008-06-27 16:09 ` Andrew STUBBS
2008-06-27 14:30 ` Tom Tromey
2008-06-28 19:20 ` Mark Kettenis
2008-06-28 19:31 ` Tom Tromey [this message]
2008-06-29 14:47 ` Daniel Jacobowitz
2008-06-29 15:36 ` Tom Tromey
2008-06-29 16:26 ` Tom Tromey
2008-06-29 14:42 ` 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=m3k5g9l5ll.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=drow@false.org \
--cc=gdb@sourceware.org \
--cc=mark.kettenis@xs4all.nl \
/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