* Upgrade from 3.2.1 to 3.2.2 recommended (Linux i386) ?
@ 2003-03-19 19:50 Malte Gell
2003-03-19 21:01 ` LLeweLLyn Reese
0 siblings, 1 reply; 3+ messages in thread
From: Malte Gell @ 2003-03-19 19:50 UTC (permalink / raw)
To: gcc-help
Hello,
I'm using GCC 3.2.1 on my system and saw that some bugs like No. 8708
(__USE_MALLOC doesn't work) are considered to be serious, so is it much
recommended to upgrade to 3.2.2 (on Linux i386) ?
If I do and also upgrade binutils (from 2.13.90.0.4 to 2.13.90.0.18)
will this break C/C++ apps/libraries compiled with GCC 3.2.1 relying on
libstdc++.so.5 from GCC 3.2.1 ?
Thanx
Malte
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Upgrade from 3.2.1 to 3.2.2 recommended (Linux i386) ?
2003-03-19 19:50 Upgrade from 3.2.1 to 3.2.2 recommended (Linux i386) ? Malte Gell
@ 2003-03-19 21:01 ` LLeweLLyn Reese
2003-03-20 8:58 ` Malte Gell
0 siblings, 1 reply; 3+ messages in thread
From: LLeweLLyn Reese @ 2003-03-19 21:01 UTC (permalink / raw)
To: Malte Gell; +Cc: gcc-help
Malte Gell <malte_gell@web.de> writes:
> Hello,
> I'm using GCC 3.2.1 on my system and saw that some bugs like No. 8708
> (__USE_MALLOC doesn't work) are considered to be serious, so is it much
> recommended to upgrade to 3.2.2 (on Linux i386) ?
>
> If I do and also upgrade binutils (from 2.13.90.0.4 to 2.13.90.0.18)
> will this break C/C++ apps/libraries compiled with GCC 3.2.1 relying on
> libstdc++.so.5 from GCC 3.2.1 ?
3.2.1 and 3.2.2 are intended to be binary compatible.
My advice is that you *not* install 3.2.2 on top of 3.2.1, but
instead use a different --prefix; I use
--prefix=/usr/local/gcc-<version> . In this way you retain both
versions.
(Note: the --prefix comment assumes you are building and installing
from source. If you are installing binaries using a package
manager, I don't know.)
I
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Upgrade from 3.2.1 to 3.2.2 recommended (Linux i386) ?
2003-03-19 21:01 ` LLeweLLyn Reese
@ 2003-03-20 8:58 ` Malte Gell
0 siblings, 0 replies; 3+ messages in thread
From: Malte Gell @ 2003-03-20 8:58 UTC (permalink / raw)
To: gcc-help
> > I'm using GCC 3.2.1 on my system and saw that some bugs like No.
> > 8708 (__USE_MALLOC doesn't work) are considered to be serious, so
> > is it much recommended to upgrade to 3.2.2 (on Linux i386) ?
> >
> > If I do and also upgrade binutils (from 2.13.90.0.4 to
> > 2.13.90.0.18) will this break C/C++ apps/libraries compiled with
> > GCC 3.2.1 relying on libstdc++.so.5 from GCC 3.2.1 ?
>
> 3.2.1 and 3.2.2 are intended to be binary compatible.
>
> My advice is that you *not* install 3.2.2 on top of 3.2.1, but
> instead use a different --prefix; I use
> --prefix=/usr/local/gcc-<version> . In this way you retain both
> versions.
Okay, this sounds good, so I'll give it a try. I always bild from
sources with the help of --prefix=/opt/GCC-3... so I can keep both
versions.
Malte
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2003-03-20 0:41 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2003-03-19 19:50 Upgrade from 3.2.1 to 3.2.2 recommended (Linux i386) ? Malte Gell
2003-03-19 21:01 ` LLeweLLyn Reese
2003-03-20 8:58 ` Malte Gell
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).