Mail Archives: pgcc/1999/08/04/02:13:50.1
On Mon, 2 Aug 1999, Marc Lehmann wrote:
>On Sun, Aug 01, 1999 at 05:08:54PM +0200, Junichi Saito <j DOT saito AT wanadoo DOT fr> wrote:
>> >versions, not specific to pgcc, which might have additional problems.
>>
>> I tried compiling KDE (kdelibs), using gcc-2.95 but the build failed with
>> :
>
>This is most probably a bug in kde. Have you reocmpiled all your libraries
>(qt)? gcc-2.95 adheres strictly to the c++ standard.
Yes, before compiling kdelibs, I first recompiled qt (1.44) with gcc 2.95.
I have been trying to have gcc 2.95 (default) and pgcc 1.1.1 installed in
parallel, but have a problem.
I first installed pgcc 1.1.1 with among other options '--prefix=/usr' and
'--enable-version-specific-runtime-libs' and next installed gcc 2.95 over
it (with "--prefix=/usr --enable-shared --enable-haifa --enable-threads").
I compiled the following apps to test the installation : groff-1.11,
xosview and kdesupport (collection of support libraries).
When I compiled groff-1.11 and xosview with "-Vpgcc-2.91.60", the
generated binaries are linked against libstdc++.so.2.9. If I did the same,
however, with kdesupport, the generated libraries are linked against the
new libstdc++.
Dose this have something to do with the use of libtool ? Or the mechanism
is different when it comes to compiling libraries ?
How can I manage to get c++ sources linked always against
libstdc++.so.2.9, when I invoke g++ with "-Vpgcc-2.91.60" ?
As to the pgcc 2.95 patch, it seems that I didn't apply it properly,
judging from a message posted here : patch said 'Reversed (or previously
applied). patch detected!'.
- Raw text -