Date: Wed, 4 Aug 1999 22:21:27 +0200
To: pgcc AT delorie DOT com
Subject: Re: Compling Kernals with PGCC
Message-ID: <19990804222126.I19168@cerebro.laendle>
Mail-Followup-To: pgcc AT delorie DOT com
References: <19990802033939 DOT C5005 AT cerebro DOT laendle> <Pine DOT LNX DOT 4 DOT 10 DOT 9908020906430 DOT 421-100000 AT saito>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
In-Reply-To: <Pine.LNX.4.10.9908020906430.421-100000@saito>; from Junichi Saito on Mon, Aug 02, 1999 at 10:21:51AM +0200
X-Operating-System: Linux version 2.2.10 (root AT cerebro) (gcc driver version egcs-2.91.66 19990314 (egcs-1.1.2 release) executing gcc version 2.7.2.3) 
From: Marc Lehmann <pcg AT goof DOT com>
Reply-To: pgcc AT delorie DOT com
X-Mailing-List: pgcc AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

On Mon, Aug 02, 1999 at 10:21:51AM +0200, Junichi Saito <j DOT saito AT wanadoo DOT fr> 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.

These versions are not binary compatible. In general you should use
gcc-2.95 with pgcc-2.95 etc.

> 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 ?

I believe using -V does not do what you intend to do. It's best to use the
frontend the respective compiler installes (e.g. by renaming g++ to pg++)

> How can I manage to get c++ sources linked always against
> libstdc++.so.2.9, when I invoke g++ with "-Vpgcc-2.91.60" ?

with /path/to/libstdc/libstdc++.so.2.9, however this is not what you might
want to do. Rather you should use the correct frontend.

> 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!'.

Yes. I can only do patches from cvs, Bernhard usually fixes all these
problems for me (but he's away).

Anyway, gcc-2.95.1 will be out in less then two weeks, and I think we cna
get a nice version then.

-- 
      -----==-                                             |
      ----==-- _                                           |
      ---==---(_)__  __ ____  __       Marc Lehmann      +--
      --==---/ / _ \/ // /\ \/ /       pcg AT goof DOT com      |e|
      -=====/_/_//_/\_,_/ /_/\_\       XX11-RIPE         --+
    The choice of a GNU generation                       |
                                                         |