Ruben Van Boxem wrote: > 2010/9/22 Ruben Van Boxem <[email protected]> > >> 2010/9/22 Earnie <[email protected]> >> >> >>> >>> Check the libstdc++.la file. If it looks valid make sure it >>> doesn't have CRLF line endings. >>> >>> Earnie >>> >> >> I have attached the libstdc++.la file. It has unix newlines, and >> everything (except the dependency_libs entry) seems ok. clearing >> that entry (..=' ') does nothing. The libdir entry is exactly the >> same as in sezero's build... >> >> One difference is the library_names entry, which is empty in >> sezero's builds. How come mine is filled in. I suppose libtool >> tried to be clever and create the absolute library location from >> libdir + "/" + library_names? >> >> Ruben >> > > And now with attachment... > > I also noticed TDM manages to release without the .la files. Would > this not create problems with libtool build systems?
I've disliked libtool to the point that at one time I had a modified libtool script that I overwrote the generated ones with; don't ask for it, I don't have it any longer. I suggest you ask the libtool list. Earnie ------------------------------------------------------------------------------ Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev _______________________________________________ Mingw-w64-public mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
