X-Authentication-Warning: ieva01.lanet.lv: pavenis owned process doing -bs Date: Mon, 29 Mar 1999 09:54:47 +0300 (WET) From: Andris Pavenis To: Eli Zaretskii cc: djgpp AT delorie DOT com Subject: Re: DJGPP support in standard EGCS 1.1.2 In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Reply-To: djgpp AT delorie DOT com X-Mailing-List: djgpp AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk On Sun, 28 Mar 1999, Eli Zaretskii wrote: > > On Mon, 22 Mar 1999, Andris Pavenis wrote: > > > - gcc/cp/g++spec.c to use libstdcxx.a instead of libstdc++.a would be nice > > as then we can use the same library file name as for native compiling > > with DJGPP. > > Why do file names like g++spec.c exist in the distribution? They > alone would prevent EGCS from building without LFN support. > > Can't you ask the maintainers to rename the files? I had no problems > like that with any GNU maintainer, including RMS. > There are many LFN related problems with original egcs sources (including header STL and libg++ header files. Therefore I don't think we'll be able to rename them all in original egcs sources. Therefore I suggest to sty with current approach: running some shell script that modifies egcs sources (together with related packages) for DJGPP. Source archive for DJGPP should already contain changes done by this script. Even more, current sources of egcs-1.1.2 for DJGPP HAVE LFN related problems and will not build without LFN support. I hope I'll be able to resolve them in future (but I'm not sure of it). Help is welcome of course. Binaries are fully usable without LFN support so problems with sources influences only poeple who are going to build egcs from sources (I think rather small part of users). They currently will need LFN support. Original question were about building cross-compiler. I previously used slightly modified original sources for that purpose but not ones for DJGPP. Therefore I mentioned some changes I suggest for that purpose. Andris