Re: msys-autoconf 2.69-2
Earnie Boyd <[email protected]>
| Newsgroups | gmane.comp.gnu.mingw.devel |
|---|---|
| Message-ID | <CA+sc5mnbcHdYgqxKJhX0tiT-wnp+qS4TrJ-Hk2F-Ad8G+aeA5A@mail.gmail.com> |
On Tue, Mar 5, 2013 at 11:43 AM, Earnie Boyd wrote: > On Tue, Mar 5, 2013 at 11:35 AM, waterlan wrote: >> >>> I certainly don't use it that way and avoid the >>> mingw32-autoconf releases. >> >> >> When you build mingw32 programs you must use mingw32-autoconf. That's >> the point. > > Why, I certainly haven't had a problem? I need to understand this > rational. I'll study the links given by Keith later today. My comment in the thread mentioned by Keith gives my original stance: > Charles Wilson wrote: >> (3) >> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= >> gettext, libtool (and libiconv) provide binary components, not just >> scripts. Specifically and most importantly, the libltdl and libintl >> DLLs. Obviously, MinGW applications will rely on mingw versions of >> these DLLs, and MSYS applications will rely on the msys versions. > > Ah, ha. This is the reason. > > The original version of msysDTK was built in the MSYS environment and > the DLL didn't exist. > > Earnie -- Earnie -- https://sites.google.com/site/earnieboyd ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_feb