From:	Andris Pavenis <pavenis AT latnet DOT lv>
To:	djgpp-workers AT delorie DOT com, "Andrew Cottrell" <acottrel AT ihug DOT com DOT au>,
	"Tim Van Holder" <tim DOT van DOT holder AT pandora DOT be>
Subject:	Re: GCC configure buglet
Date:	Fri, 23 May 2003 12:26:14 +0300
User-Agent:	KMail/1.5.2
References:	<004e01c3208a$b4c4adf0$2302a8c0 AT dualzastai> <200305221810 DOT h4MIA4aC018594 AT envy DOT delorie DOT com> <004e01c320fe$0aecf7f0$0100a8c0 AT acp42g>
In-Reply-To:	<004e01c320fe$0aecf7f0$0100a8c0@acp42g>
MIME-Version:	1.0
Message-Id:	<200305231226.15124.pavenis@latnet.lv>
Reply-To:	djgpp-workers AT delorie DOT com

On Friday 23 May 2003 10:36, Andrew Cottrell wrote:
> > > One caveat - this test (both original & patched) may break if
> > > autoconf 2.13 is used to generate configure,
> >
> > Assume 2.13, since that's the version being used at the moment.
> >
> > > AC_PREREQ(2.13)
>
> GCC 3.3 works fine with the 2.57. I have done allot of builds this week,
> proably in the order of 15-20 or more without any GCC build issues that I
> know of.
>
> If the configure did fail then would I be able to do a build?

The problems is with generating source archive (gcc33s.zip) from original
sources (eg. gcc-3.3.tar.bz2). In this case aclocal, automake, autoconf should
be run in directories where it normall should not be done when building from
gcc33z.sip. And in this case autoconf-2.13 and automake-1.[45] is needed.
I have modified related script to avoid building DJGPP sources archive when
something fails.

Andris

- Raw text -