* Building with --enable-languages problematic
@ 2001-10-09 12:24 Daniel Egger
2001-10-09 12:29 ` guerby
2001-10-09 12:30 ` Daniel Jacobowitz
0 siblings, 2 replies; 9+ messages in thread
From: Daniel Egger @ 2001-10-09 12:24 UTC (permalink / raw)
To: GCC Mailinglist
Hija,
the configure script has a bug that makes it troublesome to build
a version of gcc with only selected languages.
Using ../gcc/configure --enable-languages="c c++" works fine on
the first time but the build fails terribly on consecutive tries
when the dependencies trigger a rebuild of the scripts by issueing
config.status.
The problem is that the configure call in there uses --enable-languages
without glueing the additional arguments together by ""'s.
Thus it looks like this
../gcc/configure --with-gcc-version-trigger=/devel/gcc/gcc/version.c
--enable-languages=c c++
and fails.
Can anyone with more insight handle this please?
--
Servus,
Daniel
^ permalink raw reply [flat|nested] 9+ messages in thread* Re: Building with --enable-languages problematic
2001-10-09 12:24 Building with --enable-languages problematic Daniel Egger
@ 2001-10-09 12:29 ` guerby
2001-10-09 12:30 ` Daniel Jacobowitz
1 sibling, 0 replies; 9+ messages in thread
From: guerby @ 2001-10-09 12:29 UTC (permalink / raw)
To: degger; +Cc: gcc
The documentation says --enable-languages=c,c++ (ie use comma). I
don't know is space as separator is supported, I suspect from your
email that it is not.
--
Laurent Guerby <guerby@acm.org>
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Building with --enable-languages problematic
2001-10-09 12:24 Building with --enable-languages problematic Daniel Egger
2001-10-09 12:29 ` guerby
@ 2001-10-09 12:30 ` Daniel Jacobowitz
2001-10-09 13:06 ` Daniel Egger
1 sibling, 1 reply; 9+ messages in thread
From: Daniel Jacobowitz @ 2001-10-09 12:30 UTC (permalink / raw)
To: Daniel Egger; +Cc: GCC Mailinglist
On Tue, Oct 09, 2001 at 06:59:35PM +0200, Daniel Egger wrote:
> Hija,
>
> the configure script has a bug that makes it troublesome to build
> a version of gcc with only selected languages.
>
> Using ../gcc/configure --enable-languages="c c++" works fine on
> the first time but the build fails terribly on consecutive tries
> when the dependencies trigger a rebuild of the scripts by issueing
> config.status.
>
> The problem is that the configure call in there uses --enable-languages
> without glueing the additional arguments together by ""'s.
>
> Thus it looks like this
> ../gcc/configure --with-gcc-version-trigger=/devel/gcc/gcc/version.c
> --enable-languages=c c++
>
> and fails.
>
> Can anyone with more insight handle this please?
Try --enable-languages="c,c++"; I think that's how it's documented to
work.
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Building with --enable-languages problematic
2001-10-09 12:30 ` Daniel Jacobowitz
@ 2001-10-09 13:06 ` Daniel Egger
2001-10-09 13:25 ` Gerald Pfeifer
2001-10-09 13:27 ` Phil Edwards
0 siblings, 2 replies; 9+ messages in thread
From: Daniel Egger @ 2001-10-09 13:06 UTC (permalink / raw)
To: Daniel Jacobowitz; +Cc: GCC Mailinglist
Am Die, 2001-10-09 um 21.30 schrieb 1002655807:
> Try --enable-languages="c,c++";
Will do, thanks. Though I remember that the config.status failed
sometimes even without my intervention with exactly the same problem, so
maybe a fix would be wise nevertheless.
> I think that's how it's documented to work.
DOH, indeed. Though mentioning that in install.texi is a bit late
for someone bootstrapping the first compiler...
--
Servus,
Daniel
^ permalink raw reply [flat|nested] 9+ messages in thread* Re: Building with --enable-languages problematic
2001-10-09 13:06 ` Daniel Egger
@ 2001-10-09 13:25 ` Gerald Pfeifer
2001-10-11 7:38 ` Daniel Egger
2001-10-09 13:27 ` Phil Edwards
1 sibling, 1 reply; 9+ messages in thread
From: Gerald Pfeifer @ 2001-10-09 13:25 UTC (permalink / raw)
To: Daniel Egger; +Cc: Daniel Jacobowitz, GCC Mailinglist
On 9 Oct 2001, Daniel Egger wrote:
> DOH, indeed. Though mentioning that in install.texi is a bit late
> for someone bootstrapping the first compiler...
I don't understand. Our web page documentation and the HTML and
ASCII docs shipped with releases all are generated from install.texi,
so you can easily access the install docs immediately.
Or did I misunderstand your problem?
Gerald
--
Gerald "Jerry" pfeifer@dbai.tuwien.ac.at http://www.dbai.tuwien.ac.at/~pfeifer/
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Building with --enable-languages problematic
2001-10-09 13:25 ` Gerald Pfeifer
@ 2001-10-11 7:38 ` Daniel Egger
2001-10-12 13:56 ` Gerald Pfeifer
0 siblings, 1 reply; 9+ messages in thread
From: Daniel Egger @ 2001-10-11 7:38 UTC (permalink / raw)
To: Gerald Pfeifer; +Cc: GCC Mailinglist
Am Die, 2001-10-09 um 22.23 schrieb 1002659025:
> I don't understand. Our web page documentation and the HTML and
> ASCII docs shipped with releases all are generated from install.texi,
> so you can easily access the install docs immediately.
FWIW I prefer offline documentation over online documentation because
I have to pay access to the WWW per minute.
> Or did I misunderstand your problem?
IMHO important information to compile a software should always be
put into some sort of a textfile in the toplevel directory to guide
the user through the building process. Having the information in the
compiled docs is nice though it won't help if you fail to build at
all.
--
Servus,
Daniel
^ permalink raw reply [flat|nested] 9+ messages in thread* Re: Building with --enable-languages problematic
2001-10-11 7:38 ` Daniel Egger
@ 2001-10-12 13:56 ` Gerald Pfeifer
0 siblings, 0 replies; 9+ messages in thread
From: Gerald Pfeifer @ 2001-10-12 13:56 UTC (permalink / raw)
To: Daniel Egger; +Cc: GCC Mailinglist
On 11 Oct 2001, Daniel Egger wrote:
>> I don't understand. Our web page documentation and the HTML and
>> ASCII docs shipped with releases all are generated from install.texi,
>> so you can easily access the install docs immediately.
> IMHO important information to compile a software should always be
> put into some sort of a textfile in the toplevel directory to guide
> the user through the building process. Having the information in the
> compiled docs is nice though it won't help if you fail to build at
> all.
Well, but our docs in text form are shipped as part of releases!
As I wrote: "HTML and ASCII docs shipped with releases". How these
docs are generated (namely, from install.texi) is just a technical
detail not relevant to the end-user.
Just have a look at the README file and the INSTALL directory after
unpacking gcc-3.0.1.tar.gz!
Gerald
--
Gerald "Jerry" pfeifer@dbai.tuwien.ac.at http://www.dbai.tuwien.ac.at/~pfeifer/
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Building with --enable-languages problematic
2001-10-09 13:06 ` Daniel Egger
2001-10-09 13:25 ` Gerald Pfeifer
@ 2001-10-09 13:27 ` Phil Edwards
2001-10-13 10:36 ` Daniel Egger
1 sibling, 1 reply; 9+ messages in thread
From: Phil Edwards @ 2001-10-09 13:27 UTC (permalink / raw)
To: Daniel Egger; +Cc: Daniel Jacobowitz, GCC Mailinglist, gcc-patches
On Tue, Oct 09, 2001 at 08:06:38PM +0200, Daniel Egger wrote:
> Am Die, 2001-10-09 um 21.30 schrieb 1002655807:
>
> > Try --enable-languages="c,c++";
>
> Will do, thanks. Though I remember that the config.status failed
> sometimes even without my intervention with exactly the same problem, so
> maybe a fix would be wise nevertheless.
Something like the completely untested patch, appended?
> > I think that's how it's documented to work.
>
> DOH, indeed. Though mentioning that in install.texi is a bit late
> for someone bootstrapping the first compiler...
*cough* online web docs *cough* :-)
Index: configure.in
===================================================================
RCS file: /home/pme/Repositories/GCC/gcc/configure.in,v
retrieving revision 1.110
diff -u -3 -p -r1.110 configure.in
--- configure.in 27 Sep 2001 18:01:15 -0000 1.110
+++ configure.in 9 Oct 2001 20:25:12 -0000
@@ -1037,6 +1037,15 @@ else
if test x"${enable_languages}" = x; then
echo configure.in: --enable-languages needs at least one argument 1>&2
exit 1
+ else
+ case "${enable_languages}" in
+ # embedded tab -- do not untabify
+ "*[ ]*") echo configure.in: --enable-languages arguments are not whitespace-separated 1>&2
+ exit 1
+ ;;
+ *)
+ ;;
+ esac
fi
fi
^ permalink raw reply [flat|nested] 9+ messages in thread
end of thread, other threads:[~2001-10-13 10:36 UTC | newest]
Thread overview: 9+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2001-10-09 12:24 Building with --enable-languages problematic Daniel Egger
2001-10-09 12:29 ` guerby
2001-10-09 12:30 ` Daniel Jacobowitz
2001-10-09 13:06 ` Daniel Egger
2001-10-09 13:25 ` Gerald Pfeifer
2001-10-11 7:38 ` Daniel Egger
2001-10-12 13:56 ` Gerald Pfeifer
2001-10-09 13:27 ` Phil Edwards
2001-10-13 10:36 ` Daniel Egger
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).