delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp-workers/1997/08/14/19:16:32

From: Andrew Crabtree <andrewc AT typhoon DOT rose DOT hp DOT com>
Message-Id: <199708142311.AA188050311@typhoon.rose.hp.com>
Subject: gxx ?s / 2.7.2.3 ?s
To: djgpp-workers AT delorie DOT com
Date: Thu, 14 Aug 1997 16:11:50 PDT

try again

> 
>    ----- The following addresses had permanent fatal errors -----
> <djgpp-workers AT delorie DOT com>
> 
>    ----- Transcript of session follows -----
> ... while talking to delorie.com.:
> >>> MAIL From:<andrewc AT typhoon DOT rose DOT hp DOT com> SIZE=1726
> <<< 551 <andrewc AT typhoon DOT rose DOT hp DOT com>... Host typhoon.rose.hp.com doesn't exist in DNS
> 554 <djgpp-workers AT delorie DOT com>... Service unavailable
> 
> Hello - 
> 
> I'm not subscribed so CC responses please.  Could someone explain 
> how the gxx that comes in the C++ compiler works?  My assumption 
> is that it is just a wrapper program that calls gcc.  Is that 
> correct?  The reason I ask is that I have received bug reports regarding
> gxx from the latest pcg snapshots.  If I add a [gxx] section to the 
> djgpp.env file that is the same as the one for [gcc] everything works 
> OK.  My simple test case for the theory was 'gxx -v -c hello.c' (this
> is with the [gxx] change to djgpp.env)
> 
> with original gxx 
> 
> <snip cpp stuff>
> cc1 ....
> as -o hello.o c:\TEMP/ccaaaaaa.s
> gcc.exe: -lgpp: linker input file unused since linking not done
> gcc.exe: -lstdcx: linker input file unused since linking not done
> gcc.exe: -lm: linker input file unused since linking not done
> 
> 
> Note that cc1 was invoked to compile the .c file.
> 
> 
> With 0725 pcg snapshot gxx
> 
> <snip cpp stuff>
> cc1plus ...
> as -o hello.o C:\TEMP/ccaaaaaa.s
> 
> 
> Thats it.  No unused linker file messages or anything.  Was gxx modified for
> the DJGPP release or something?  My assumption would be no since 
> prior to release of pgcc didn't appear to have this problem (or nobody used 
> c++).  I'm not sure if telling people
> to modify their djgpp.env is the correct thing and would appreciate any
> comments.
> 
> Also, in case anyone is interested there will be a 2.7.2.3 official fsf
> release very soon.  
> Although primarily for linux/glibc fixes they also were accepting
> general bug fixes.  Since there has been a lot of questions on djgpp
> list about debugging .cpp files or using -gstabs it may be worthwile
> to submit that to HJ Lu and roll another 'official' DJGPP gcc release.
> 
> Thanks 
> 
> Andrew

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019