This is the mail archive of the
cygwin-apps
mailing list for the Cygwin project.
R: Now uploading gcc4-4.3.2-2/ PING hdf5, libicu38, file maintainers.
- From: Marco Atzeri <marco_atzeri at yahoo dot it>
- To: cygwin-apps <cygwin-apps at cygwin dot com>, Dave Korn <dave dot korn dot cygwin at googlemail dot com>
- Date: Thu, 12 Mar 2009 07:45:04 +0000 (GMT)
- Subject: R: Now uploading gcc4-4.3.2-2/ PING hdf5, libicu38, file maintainers.
--- Gio 12/3/09, Dave Korn ha scritto:
> Da: Dave Korn
> Oggetto: Now uploading gcc4-4.3.2-2/ PING hdf5, libicu38, file maintainers.
> A: "cygwin-apps"
> Data: Giovedì 12 marzo 2009, 05:25
>
> ? ? Hi all,
>
> ? 4.3.2-2 is ready to go, so I'm starting to upload it
> to sourceware.org now.
>
> ? It's still experimental, so it doesn't make gcc-4
> the default just now.
> Unless anything nasty crops up I imagine the next release
> will be the first
> that can be considered fully production-ready and probably
> an appropriate time
> to switch the default away from -3.
>
> ? One thing this does is obsolete the current
> unversioned cyggcc_s.dll.? At
> the moment there are only a few packages, according to
> setup{,-2}.ini, that
> require it:
>
> >From 1.5 distro:
>
> hdf5
> libhdf5_0
>
> >From 1.7 distro:
>
> file
> hdf5
> libhdf5_0
> libicu38
>
> ? There's no need for the maintainers to rush to
> respin these packages, but
> sooner rather than later is in general better.
>
> ? As other package maintainers start building their
> DLLs to link against the
> newer shared libgcc, there is a danger that an application
> that links against
> multiple DLLs may end up linking against both versions
> simultaneously; that
> would be bad.
>
> ? (libhdf, for example, requires gcc4-runtime and
> zlib; if zlib DLL gets
> rebuilt against the new libgcc, and libhdf DLL doesn't,
> applications using
> libhdf may get both runtimes at once.)
>
> ? ? cheers,
> ? ? ? DaveK
>
Thanks Dave,
my original intention was to respin only the cygwin-1.7
packages but I will rebuild hdf5 also for cygwin-1.5
and likely also the others just to be sure.
I think octave could have the same problem
$cygcheck /usr/bin/octave-3.0.3.exe
C:\cygwin/bin\octave-3.0.3.exe
C:\cygwin/bin\cygoctinterp.dll
C:\cygwin/bin\cygcruft.dll
C:\cygwin/bin\cygblas.dll
C:\cygwin/bin\cygwin1.dll
C:\WINDOWS\system32\ADVAPI32.DLL
C:\WINDOWS\system32\ntdll.dll
C:\WINDOWS\system32\KERNEL32.dll
C:\WINDOWS\system32\RPCRT4.dll
C:\cygwin/bin\cyglapack.dll
C:\cygwin/bin\cyggcc_s.dll
C:\cygwin/bin\cygoctave.dll
C:\cygwin/bin\cygfftw3-3.dll
C:\cygwin/bin\cygreadline6.dll
C:\cygwin/bin\cygncurses-8.dll
C:\WINDOWS\system32\USER32.dll
C:\WINDOWS\system32\GDI32.dll
C:\cygwin/bin\cyghdf5-0.dll
C:\cygwin/bin\cygz.dll
Regards
Marco