From: DJ Delorie <dj@redhat.com>
To: drow@mvista.com
Cc: neroden@twcny.rr.com, binutils@sources.redhat.com,
gdb-patches@sources.redhat.com, gcc-patches@sources.redhat.com
Subject: Re: re-re-re-re-configuring
Date: Sun, 08 Dec 2002 20:38:00 -0000 [thread overview]
Message-ID: <200212090330.gB93Um631814@greed.delorie.com> (raw)
In-Reply-To: <20021209032404.GA31552@nevyn.them.org> (message from Daniel Jacobowitz on Sun, 8 Dec 2002 22:24:04 -0500)
> So, um, silly question. Why does changing libiberty require that
> bfd/Makefile be regenerated?
Because bfd/Makefile does this:
x=`sed -n -e 's/^[ ]*PICFLAG[ ]*=[ ]*//p' < ../libiberty/Makefile | tail -1`
prev parent reply other threads:[~2002-12-09 3:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20021206102555.GA15028@redhat.com>
[not found] ` <200212061850.gB6Io3m26371@greed.delorie.com>
2002-12-08 14:40 ` re-re-re-re-configuring Nathanael Nerode
2002-12-08 16:12 ` re-re-re-re-configuring DJ Delorie
2002-12-08 19:28 ` re-re-re-re-configuring Daniel Jacobowitz
2002-12-08 20:38 ` DJ Delorie [this message]
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=200212090330.gB93Um631814@greed.delorie.com \
--to=dj@redhat.com \
--cc=binutils@sources.redhat.com \
--cc=drow@mvista.com \
--cc=gcc-patches@sources.redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=neroden@twcny.rr.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