On Thu, 6 Jun 2002 06:24:46 -0500
s <[EMAIL PROTECTED]> wrote:

 
> >
> > Well, I seem to have,
> > gcc-cpp v2.96-0.76mdk
> > gcc v2.96-0.76mdk
> > gcc3.0 v3.0.4-2mdk (gnu compiler)
> > gcc3.0-cpp v3.04-2mdk
> > so any of these should be OK ?
> > It doesn't seem to matter then  that so many compiler versions are
> > present at once, they don't get confused then ?
> > John
> 
> Why naw, it ain't gonna get confused.  The default appears to be
> handled by a link in /etc/alternatives.  Change the link to change the
> default compiler.  Also many configure scripts allow you to specify
> which compiler to use with the switch --cc= (I think that's it, do a
> ./configure --help to get exact syntax). 
> Shoot, just go for it and worry after you get an error (but that's
> just me:  untar, read README & INSTALL, then go for it!).  using
> --disable-gcc-checking --enable-gui --disable-runtime-cpudetection is
> my usual formula, that way I don't have to worry about it complaining
> or my risking the compiler by goofing with it. 
 

It is best to leave the default compiler set to that with which the
kernel was compiled which in 8.2 was gcc-2.9.6

the mplayer build problem has been discussed numerous times.
The aversion it has for 2.9.6 is because of RH using a pre 2.96 and
calling it 2.9.6.
This is not the case with mandrake so the --disable-gcc-checking option
can be used without problem.

Should you still prefer to do the build with gcc3.0 then;
Open a terminal that you can set aside to be used for building with
gcc3.0
su to root and enter # export CC=gcc-3.0.4
>From that point, unless you install a new kernel any program built from
That terminal will use gcc3.0


    Charles

Want to buy your Pack or Services from MandrakeSoft? 
Go to http://www.mandrakestore.com

Reply via email to