GCC 3.x is stricter than GCC 2.95.3 that's what all the "scary
warnings" are you read about.
If the developers for the project your compiling adhered to
standards a little closer they probably would not run into problems. A lot
of code out there is a little sloppy. Older versions of GCC did not
complain as much, so the code was allowed to compile.
If you want to use a different compiler on your system you should
look into building the compiler yourself. It's pretty easy. Untar the
sources to a directory, then create a peer directory called build. Go into
build and invoke the configure from the sources. You will probably want to
specify a --prefix=/usr/local/gcc-2.95.3, so that all the files go into
their own directory. This makes it easier to maintain a bunch of different
compilers on the machine. If you want shared libs you have specify a
--shared-enabled or an option very close to this. I typically build shared
libs and specify --enable-threads=posix.
"../gcc-2.95.3_source/configure --prefix=/usr/local/gcc-2.95.3
--enable-shared --enable-threads=posix" These options are what I generally
use.
Then do a "make bootstrap" and a little while later your compiler will be
built.
Do a "make install". Now you should have everything installed to
/usr/local/gcc-2.95.3. You will then need to play around with your library
path if you want to build projects with the new compiler and use shared
libs. The libs you'll need are in /usr/local/gcc-2.95.3/lib this is not
part of the standard shared lib path. There are a few ways to fix this, it
all depends on how you want to configure your system.
If you run into problems send me an email and I'll help you. I do this kind
of thing a lot.
-----Original Message-----
From: Daniel Sheltraw [mailto:[EMAIL PROTECTED]
Sent: Thursday, April 03, 2003 12:29 PM
To: [EMAIL PROTECTED]
Subject: Re: GCC and Redhat 8.0
Hello Again
> > > > So was this the kcc or kgcc compiler, or was that something
> else
> > > > altogether ?
> > >
> > > Yes, kgcc.
> >
> > I doubt it. I don't even have kgcc installed, and no problem
> building
> > anything. I think kgcc was just a 7.x creature, back when early
> 2.96
> > compilers had trouble with kernel building. Later 2.96 build
> kernels
> > fine (as do 3.x):
>
> Yes, the point I was trying to make was that kgcc (or even old gcc
> versions) haven't been included recently because the default compiler
> *is*
> the compiler used for the kernel. The reference to kgcc was just to
> demonstrate that RH would certainly have provided a kernel-capable
> compiler if their current gcc didn't do the job (at least as far as
> their
> own QA goes).
The reason for my initial question about the GCC 3.2 compiler and
a compiler fit for kernel work is that a remembered the problem
with GCC 2.96. I am patching a 2.4.20 kernel with the RTAI
real-time executive patch. The latest RTAI patch says in a README
file that the GCC 3.2 compiler gives lots of scarey warnings
when used to do the compile and I would rather avoid this problem
despite the fact that the build is reported to work. So, recalling
that in the Redhat 7.2 there was another compiler besides the
2.96, I was wondering if RedHat 8.0 contains a 2.95.3 compiler
somewhere which can be installed. My understanding is that 2.95
is still the "official" compiler for kernel work.
Thanks again
Daniel
>
.com?subject=unsubscribe
> https://listman.redhat.com/mailman/listinfo/redhat-list
>
--
redhat-list mailing list
unsubscribe mailto:[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
--
redhat-list mailing list
unsubscribe mailto:[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
