Date:	Sun, 24 Jun 2001 11:01:52 +0300 (IDT)
From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender:	eliz AT is
To:	jonathan bailey <jbailey8 AT triad DOT rr DOT com>
cc:	djgpp AT delorie DOT com
Subject:	Re: Compile gcc 3.0
In-Reply-To:	<RMbZ6.73260$ru2.21459476@typhoon.southeast.rr.com>
Message-ID:	<Pine.SUN.3.91.1010624110132.13700O-100000@is>
MIME-Version:	1.0
Reply-To:	djgpp AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	djgpp AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

On Sun, 24 Jun 2001, jonathan bailey wrote:

> 1. At some point during configure, I see a line that says
>     'Determining maximum length of command line input'
>     or something close to this statement, after a minute or so,
>     the computer either locks up completly

This is a known problem with the recent versions of libtool (a shell
script that is run as part of the GCC build procedure to adapt the
produced programs and libraries to the host and target environment).
The problem with testing the maximum length of command line is that,
when DJGPP programs are run via Bash, there's no such limit, except
for the amount of free disk space and virtual memory.  (That's because
Bash automatically switches to using response files when the command
line becomes too large for the 16KB transfer buffer.)  So the script
keeps enlarging the command line length until it overflows some
internal buffer in one of the library functions that processes the
argv[] array.

This will be fixed in the next DJGPP release, but until then, I
suggest to put the following line into your config.site file:

export lt_cv_sys_max_cmd_len=12288

(This tells libtool that the limit on the command-line length is about
12KB, which should be right for every sane DJGPP installation.)

> 2. Once I get past the first problem, I run into another problem
>     which is more serious, The configure part has finished by now,
>    so all of the makefiles have been created, I then go to the root
>    of the sources and type 'make bootstrap', this runs for a while
>    and then eventually stops with the error 'xgcc ./specs permission
>    denied (EACCES)'.

Why do you need to bootstrap?  Why can't you just say "make"?  You
already have a working version of GCC, so "make bootstrap" should not
be required.

I agree that "make bootstrap" should work, but it involves additional
complications, so if you just want to build GCC with minimal fuss, you
may wish to avoid bootstraping.

Also note that GCC 3.0 needs a modified linker script to avoid some
subtle problems.  You can get the modified script from the DJGPP CVS
(see http://www.delorie.com/djgpp/cvs.html).

- Raw text -