From: Andrew Crabtree <andrewc AT typhoon DOT rose DOT hp DOT com>
Message-Id: <199705241659.AA075583151@typhoon.rose.hp.com>
Subject: Re: Problems with pgcc
To: bukinm AT inp DOT nsk DOT su
Date: Sat, 24 May 1997 9:59:11 PDT
Cc: djgpp AT delorie DOT com
In-Reply-To: <338431e9.9258972@news-win.inp.nsk.su>; from "Michael Bukin" at May 22, 97 12:34 (noon)
Precedence: bulk

> 
> 1. When compiling tested C++ program with virtual functions
> linker says:
> 
> d:/comp/djgpp/tmp/ccaaaaaa1.o(.text+0x136):cctest0.cc: undefined
> reference to `__rtti_si'
> d:/comp/djgpp/tmp/ccaaaaaa1.o(.text+0x162):cctest0.cc: undefined
> reference to `__rtti_user'

Not surprising.  As I said, the C++ parser is basically untested.
I believe I may have seen a reference to RTTI in G++ in the 
PGCC FAQ.  Something like a new feature?!?  Could be you
need new libs.  Sorry I can't be of any more help.

> 2. Also, it looks like pgcc does not recognize GCC_EXEC_PREFIX.
> gcc should first try to execute stage by appending name to the
> value of GCC_EXEC_PREFIX and then in standard places.
> For more info, read this: info gcc invo envi

Hmmm - It could be that pgcc does not recognize the set DJGPP=
stuff.  If you could, would you set GCC_EXEC_PREFIX in the 
environment and see if it works there.  I'll try to diff the 
cooked dj source distribution with the original FSF and see if 
there were any changes to support this. 

> The idea of using GCC_EXEC_PREFIX was to have two (or more)
> compilers at the same time, and to call them with different names.

I always thought EXEC_PREFIX was used if you didn't configure with
--prefix and then moved gcc.  I think you may be able to accomplish the
same thing that you want with the -V option.  I think it works by
having one copy of gcc, and then depending on the -V option it calls different
versions of CPP, CC1, ...  Note that I haven't tested -V on pgcc so 
I may be spewing crap right not.

Andrew