From: cgd@broadcom.com
To: binutils@sources.redhat.com, aoliva@redhat.com
Subject: configure updates after libtool.m4 update, & my paranoia...
Date: Mon, 28 Apr 2003 20:41:00 -0000 [thread overview]
Message-ID: <yov5of2qtkx0.fsf@broadcom.com> (raw)
Alex,
While testing the binutils 2.14 branch, i noticed your commit
[ toplevel ]
2003-04-11 Alexandre Oliva <aoliva@redhat.com>
* libtool.m4 (lt_cv_deplibs_check_method): Use pass_all on mips*.
* */configure: Rebuilt.
However, AFAICT, */configure weren't rebuilt, at least for values of
'*' that include the binutils-related subdirs. 8-)
In particular, I don't see this rebuild in gas/configure,
bfd/configure, ld/configure, or binutils/configure... (those were the
only ones I checked. 8-)
Shouldn't those have been regen'd at the same time?
(i always sanity check my regenerated configure diffs, because, well,
i don't really trust my local copy of autoconf very much... that's
how i noticed.)
chris
next reply other threads:[~2003-04-28 20:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-28 20:41 cgd [this message]
2003-04-28 21:59 ` Alexandre Oliva
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=yov5of2qtkx0.fsf@broadcom.com \
--to=cgd@broadcom.com \
--cc=aoliva@redhat.com \
--cc=binutils@sources.redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).