Re: colorgcc: colorgcc screws up configure (was: Re: I think I'm going mad ...)
severity 75789 important
thanks.
On Sun, 29 Oct 2000, Raphael Bossek wrote:
> hi Cristian,
>
> > Now I found it!!! The problem seems to be COLORGCC.
> >
> > It looks like configure (which uses gcc to do it's tests) can't cope
> > with colorgcc (which is a gcc wrapper) or colorgcc is screwing up.
> hm, I'm using colorgcc successful with my automake/autoconf environemtns.
> Take a look on my configure.in...
>
> AC_ARG_WITH(colorgcc,
> [ --with-colorgcc= use ColorGCC script for colorising GCC compiler output (default yes)],
> colorgcc=`echo $withval|tr [A-Z] [a-z]`, colorgcc="yes")
> if test "$colorgcc" = "yes" -o "$colorgcc" = "on"; then
> AC_PATH_PROG(COLORGCC,colorgcc)
> if test "$COLORGCC"; then
> CC="$COLORGCC"
> CXX="$COLORGCC"
> else
> echo "***"
> echo "*** Missing ColorGCC script for GCC output colorisation!"
> echo "*** To enable ColorGCC colorisation install the colorgcc"
> echo "*** package provided by your distribution or install the"
> echo "*** latest application from http://home.i1.net/~jamoyers/software/";
> echo "***"
> exit 1
> fi
> fi
>
> Please send me your configure.in or better the project, so I can reproduce
> it here!
Um, this is completely wrong. colorgcc should <b><i><blink>NOT</blink></i></b>
output colorization codes when it's stdout/stderr is NOT a terminal. This
way, wrappers that parse it's output can function sanely.
----BEGIN GEEK CODE BLOCK----
Version: 3.12
GCS d- s: a-- c+++ UL++++ P+ L++++ !E W+ M o+ K- W--- !O M- !V PS--
PE++ Y+ PGP++ t* 5++ X+ tv b+ D++ G e h*! !r z?
-----END GEEK CODE BLOCK-----
----BEGIN PGP INFO----
Adam Heath <doogie@debian.org> Finger Print | KeyID
67 01 42 93 CA 37 FB 1E 63 C9 80 1D 08 CF 84 0A | DE656B05 PGP
AD46 C888 F587 F8A3 A6DA 3261 8A2C 7DC2 8BD4 A489 | 8BD4A489 GPG
-----END PGP INFO-----
Reply to: