MinGW - Minimalist GNU for Windows

Hello!

>>I tried this a while ago and building a static library using autoconf
>>and libtool was stilll possible. I did not see any functional difference
>>between the this and the older version.
> 
> OK.

This was only partly correct. I found out that the 1.5.22 mingPORT seems
to install libtool.m4 below my mingw directory instead below by msys
directory where all other macro-collections are places. Thus it did not
overwrite my old libtool.m4 which in turn resulted in my autoconf
scripts still working with old macro-package.

I fixed that by simply moving them to the right place. But nevertheless
this seems to be a problem in the mingPORT-package.


>>Building shared libraries still did not work. libtool claimed that there
>>were unresolved symbols. Searching google shows that this may have to do
>>with some special math library condition in MingW (Sounded like math
>>library is faked, but I'm not an expert on this topic).

> 
> We have fixed a related bug a while ago.  To fix any remaining instances
> of the issue (or a pretty similar one, as it most likely is), I need
> very detailed information.

After fixing installation, rebuild the configure stuff (including
ltmain.sh and libtool scripts), fixing libm usage, adding -no-undefined
 and fixing my IMPORT/EXPORT macros I was finally able to build a
working DLL!

So: I was able to build a DLL using libtool 1.5.22 called from a
"normal" Unix-based autoconf package :-) This saved me about 300MB disk
space :-)

> 1) Did you add -no-undefined to the link line?  If no, please do so.

It this a "Windows-only" or should this be added for building
libtool-based shared-libraries on all systems?

-- 
Gruß...
       Tim.

I have uploaded an update  of binutils (2.16.91-20060119-1)
to MinGW's Sourceforge File Release page. You can download it
from:

https://sourceforge.net/project/showfiles.php?group_id=2435

The 2.16.91-20060119-1 snapshot incorporates modifications to official
binutils CVS since last update.

Of particular interest is that 'objcopy --add-gnu-debuglink' now works
as advertised on Windows (PE-COFF) targets.  This feature is used to
to move debug information from an executable into a separate .dbg file. 
Please refer to the objcopy section of the binutils info file for more details.

It also includes a patch by Filip Navara to support forward exports
in .def files passed to ld.exe.

Please refer ChangeLog entries in src for specific changes

For more info on binutils, follow this:
http://sources.redhat.com/binutils/

Danny

2006-01-24

Read and respond to this message at: 
https://sourceforge.net/forum/message.php?msg_id=3539313
By: radsurfer

Hello!
When I first downloaded mingw, I was under the impression it was called
     mingw_date_version#.zip|exe,
or something logical like that....

When I goto sourceforge to download the latest
complete package, as a whole, I find apparently
there is no such package now?
That when unzipped or executed installs the complete
mingw directory tree, with all necessary items
all nicely provided and put where they belong.

Is this form of mingw still available or what
now?  Did I miss something somewhere?

the gcc in the mingw I have reports:
g:\mingw>gcc --version
GCC.EXE (GCC) 3.4.2 (mingw-special)
Copyright (C) 2004 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

The dates in most of the things in \bin\ is
1-20-05, and the libs are dated 1-20-05,
and I installed it 05-04-05 judging from the date
of the mingw directory itself.

I was trying to determine if a single mingw-installer could be downloaded to
conveniently upgrade me to the latest version.
I understand that various components can be updated seperately; but I like having
on hand the
very latest complete installer if still available.

Thanks for any comments!

RadSurfer@...



______________________________________________________________________
You are receiving this email because you elected to monitor this forum.
To stop monitoring this forum, login to SourceForge.net and visit: 
https://sourceforge.net/forum/unmonitor.php?forum_id=7134