Date: Wed, 13 Jun 2001 15:39:18 +0300 (IDT) From: Eli Zaretskii X-Sender: eliz AT is To: pavenis AT lanet DOT lv cc: djgpp-workers AT delorie DOT com Subject: Re: GCC-3.0 related problem with src/libc/stubs/stubXXXX.S In-Reply-To: <3B27870A.168.843261@localhost> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Reply-To: djgpp-workers AT delorie DOT com Errors-To: nobody AT delorie DOT com X-Mailing-List: djgpp-workers AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk On Wed, 13 Jun 2001 pavenis AT lanet DOT lv wrote: > > Does that mean that -remap and -imacros don't work with "gcc -traditional"? > > > > If that is indeed so, I guess we have no other choice but to modify the > > stubs as you suggested originally. Tweaking specs for this is too gross, > > IMHO, and might also cause compatibility problems in the long run. > > I don't expect special problems from such modification of specs (I > simply copied condition from rule how to choose which of cpp0 > or tradcpp0 to use). > > gcc -traditional will fail unconditionally unless I exclude both > -remap and -imacros when tradcpp0 is being used. We'll unable to > compile too much things with gcc -traditional even when we'll > remove these options with tradcpp0. If the problem with -traditional is not limited to building the library, then changing specs _is_ the solution, because we will have to make that change anyway, to let users use -traditional. However, I wonder: since what version of GCC did -traditional stop working with -imacros? Is this something new in GCC 3.0? Also, this seems to suggest that "gcc -traditional" will not pick up the __DJGPP__ and __DJGPP_MINOR__ symbols, and also will not be able to automatically find some of the C++ headers which need -remap, and that this side effect cannot be cured by changes in specs. Is that true?