Date: Thu, 30 May 2002 11:09:49 +0300 (WET) From: Andris Pavenis X-Sender: pavenis AT ieva06 To: Eli Zaretskii Cc: djgpp-workers AT delorie DOT com Subject: Re: [Fix for v2.03 refresh] Re: Undefined reference to _finite In-Reply-To: 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 Thu, 30 May 2002, Eli Zaretskii wrote: > > On Thu, 30 May 2002, Andris Pavenis wrote: > > > libm.a should be linked AFTER libstdcxx.a. > > > > Is it OK to check in included patch for DJGPP v2.03 refresh. > > I don't see any reason why not. Commited. Perhaps I should send a patch also to people who get linking problems (normally we don't recommend to modify djgpp.env ...) as a refresh will not be out very soon > The question that bothers me is whether this order can cause trouble > outside RHIDE as well. For example, does gpp.exe invoke the linker with > those libraries in the correct order? What about gxx.exe? > After looking at sources (src/utils/gxx.c) all seems to be Ok. Anyway I think that linking libgpp.a should be dropped as it is no more supported with gcc-3.X. If we drop it, then I think it is simplier to use gpp.exe instead (ln -s gpp.exe gxx.exe) We have one additional problem with RHIDE and gcc-3.1. For gcc-3.1 linking Fortran programs requires also libfrtbegin.a not only libg2c.a and libm.a. libfretbegin.a were not present in earlier versions, so I cannot simply put it in. So perhaps it should be solved inside RHIDE, not here Andris PS. Perhaps I could help Charles a bit and check in patch for sys/djtypes.h too