public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: spam@wrightnet.dhs.org
To: gcc-gnats@gcc.gnu.org
Subject: other/3055: Configure error-GCC-3 (CVS source for 6/5/2001) on HPUX 11.0: ltconfig and maximum length of command line operations in zlib
Date: Tue, 05 Jun 2001 10:06:00 -0000 [thread overview]
Message-ID: <20010605170333.7918.qmail@sourceware.cygnus.com> (raw)
>Number: 3055
>Category: other
>Synopsis: Configure error-GCC-3 (CVS source for 6/5/2001) on HPUX 11.0: ltconfig and maximum length of command line operations in zlib
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: unassigned
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Tue Jun 05 10:06:04 PDT 2001
>Closed-Date:
>Last-Modified:
>Originator: zlib
>Release: GCC-3.0 (CVS Source 6/5/2001)
>Organization:
>Environment:
HP UX 11.0
GNU bash, version 2.04.0(1)-release (hppa2.0n-hp-hpux11.00)
>Description:
When I run configure, and when configure recurses into the zlib directory, I get the following error (and autoconf stops completely):
finding the maximum length of command line arguments... ./../ltconfig[790]: There is not enough memory available now.
configure: error: libtool configure failed
Configure in /tmp/gcc/zlib failed, exiting.
This halts my build of gcc entirely. This wasn't a problem in 2.95.x, but it seems to be a problem in all the latest snapshots on GCC 3.x. I tried to compile with several different shells, with the same result. I also tried to bypass zlib with the --with-system-zlib, but it still ran configure from the zlib directory
>How-To-Repeat:
Run it as specified in environment.
>Fix:
I removed the zlib directory from the tree, and used
--with-system-zlib, and that seemed to get around the problem. However, I'm not sure what this will break later.
>Release-Note:
>Audit-Trail:
>Unformatted:
next reply other threads:[~2001-06-05 10:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-05 10:06 spam [this message]
2002-01-04 22:10 rodrigc
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=20010605170333.7918.qmail@sourceware.cygnus.com \
--to=spam@wrightnet.dhs.org \
--cc=gcc-gnats@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).