delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp-workers/1998/04/14/08:36:14

Date: Tue, 14 Apr 1998 15:35:57 +0200 (WET)
From: "Andris Pavenis (LU Astro.)" <pavenis AT lanet DOT lv>
To: Robert Hoehne <robert DOT hoehne AT gmx DOT net>
cc: djgpp-workers AT delorie DOT com
Subject: Re: [Fwd: Re: What did I miss ?]
In-Reply-To: <352E33B9.8A1666AB@gmx.net>
Message-ID: <Pine.A32.3.91.980414152847.68224A-100000@ieva05.lanet.lv>
MIME-Version: 1.0


On Fri, 10 Apr 1998, Robert Hoehne wrote:

> Because I saw this mail only via DJ's mail archive, I cannot
> answer directly, but here my comments.
> 
> The problem with the -dumpbase option is not fixed in
> gcc 2.8.0 (and probably also not in gcc 2.8.1) _BUT_ the
> good news: this does not matter, since gcc for DJGPP
> does not longer use the -dumpbase argument to place the
> filename in the assembler sources (it uses now the main
> input filename) and so it works now correct and there
> is no need to fix the -dumpbase thing.
> 
> To check it, simply compile
> 
> gcc -S foo.cpp
> 
> and you will see the (correct) result.
> 

Thanks. I tested this in Linux with gcc 2.8.1 and all went Ok (I haven't
booted Win95 today yet). Then perhaps it's really not worth to touch it 
even if it is not very difficult. Then we should consider -dumpbase as a 
relic from previous versions of gcc.

Robert, have You tried a version of port of gcc I uploaded to delorie.com
(it is in /v2gnu/alphas). Unfortunatelly looks that last version of 
patches I sent to You were better (my own opinion). 

Andris

- Raw text -


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