From: Paolo Bonzini <bonzini@gnu.org>
To: gcc@gcc.gnu.org, Autoconf List <autoconf@gnu.org>
Subject: Re: toplevel configure hits sed program length limit on HP-UX
Date: Mon, 31 Aug 2009 21:11:00 -0000 [thread overview]
Message-ID: <4A9C2BC1.6040203@gnu.org> (raw)
In-Reply-To: <20090831195746.GA21485@gmx.de>
> In fact, I think this API shouldn't be even more encouraged. It doesn't
> really fix things in an elegant way, and it doesn't help for other
> pending issues in the GCC tree (such as the multilib fixups that aren't
> applied in all cases; report coming up).
I agree. However, I did not have any alternative idea when I started
using extrasub, and do not have one now. :-(
> Well maybe, but I'm not sure whether we want another rush, nor why we
> need to decide this alongside with the extrasub issue. override.m4
> is also about relaxing release order requirements, no?
Yes, though I'd rather not put anything more than 15-20 lines long in
override.m4.
Paolo
next prev parent reply other threads:[~2009-08-31 20:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-31 19:57 Ralf Wildenhues
2009-08-31 20:00 ` Paolo Bonzini
2009-08-31 20:41 ` Ralf Wildenhues
2009-08-31 21:11 ` Paolo Bonzini [this message]
2009-08-31 23:05 ` Ralf Wildenhues
2009-08-31 21:07 ` Jeff Law
2009-08-31 21:31 ` Ralf Wildenhues
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=4A9C2BC1.6040203@gnu.org \
--to=bonzini@gnu.org \
--cc=autoconf@gnu.org \
--cc=gcc@gcc.gnu.org \
/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).