From: Joel Brobecker <brobecker@adacore.com>
To: Michael Snyder <msnyder@specifix.com>
Cc: gdb@sourceware.org, Nicolas Bonifas <nicolas.bonifas@free.fr>
Subject: Re: Should we install gcore.sh (and a gcore.1 man page)?
Date: Thu, 25 Oct 2007 00:41:00 -0000 [thread overview]
Message-ID: <20071025004101.GQ11797@adacore.com> (raw)
In-Reply-To: <1193271391.16917.42.camel@localhost.localdomain>
> That sounds good. Then we would not have to change much
> except for like Makefile.in and configure.in. Script something
> like 'cat <host makefile fragment> | grep "gcore\.o"'
I think you can simplify this even further by only changing Makefile.in.
Instead of grep'ing the makefile fragment, which can only be done in
the configure script (and is also a little error prone), I think you
can just grep the value of ${DEPFILES} for gcore.o.
--
Joel
next prev parent reply other threads:[~2007-10-25 0:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-24 22:01 Michael Snyder
2007-10-24 22:10 ` Joel Brobecker
2007-10-24 22:14 ` Michael Snyder
2007-10-24 22:24 ` Joel Brobecker
2007-10-25 0:21 ` Michael Snyder
2007-10-25 0:41 ` Joel Brobecker [this message]
2007-11-05 9:30 ` Nicolas Bonifas
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=20071025004101.GQ11797@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb@sourceware.org \
--cc=msnyder@specifix.com \
--cc=nicolas.bonifas@free.fr \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).