From: Michael Elizabeth Chastain <mec@shout.net>
To: ac131313@cygnus.com, aoliva@redhat.com, jeffh@redhat.com
Cc: binutils@sources.redhat.com, gdb-patches@sources.redhat.com
Subject: Re: [Patch] updated ltcf-*.sh, ltconfig, ltmain.sh
Date: Mon, 05 Nov 2001 10:42:00 -0000 [thread overview]
Message-ID: <200111141733.LAA24289@duracef.shout.net> (raw)
Andrew Cagney writes:
> Changes need to be done in tandem with the official LIBTOOL
> sources or submitted to the master file maintainer and brought
> in via a merge.
Indeed. I went through this procedure. Before I submitted this change to gcc,
I submitted it to libtool and it was accepted in the mainline there.
From the libtool ChangeLog:
2001-07-09 Robert Boehne <rboehne@ricardo-us.com>
From Michael Elizabeth Chastain <chastain@cygnus.com>:
* libtool.m4 (AC_LIBTOOL_SYS_MAX_CMD_LEN): Set max_cmd_len
to a maximum of 512Kb, as it seems some HPUX 11.0 systems
have trouble with 1MB.
Alexandre Oliva asked me to mark this change as "gcc-local" in the
gcc sources; I don't remember the reasoning behind this.
You might want to run through your import procedure and check that
it yields the fixed ltconfig now. I'm getting my libtool from
"cvs -z3 -d :pserver:anoncvs@subversions.gnu.org/cvsroot/libtool co libtool"
which I believe is the official source.
Michael C
next reply other threads:[~2001-11-14 17:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-05 10:42 Michael Elizabeth Chastain [this message]
2001-11-06 8:12 ` Alexandre Oliva
-- strict thread matches above, loose matches on Subject: below --
2001-11-05 7:17 Jeff Holcomb
2001-11-05 8:58 ` Andrew Cagney
2001-11-05 11:27 ` Jeff Holcomb
2001-11-06 14:38 ` Andrew Cagney
2001-11-10 13:15 ` 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=200111141733.LAA24289@duracef.shout.net \
--to=mec@shout.net \
--cc=ac131313@cygnus.com \
--cc=aoliva@redhat.com \
--cc=binutils@sources.redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=jeffh@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