mingw-cross-env-list
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Mingw-cross-env-list] gcc 4.6.0


From: Volker Grabsch
Subject: Re: [Mingw-cross-env-list] gcc 4.6.0
Date: Sun, 27 Mar 2011 18:15:21 +0200
User-agent: Mutt/1.5.18 (2008-05-17)

Mark Brand schrieb:
> Would you like to share this letter-writing campaign and contact group  
> 1) (guile, physfs) and 3) (exiv2, xine-lib). I'll contact 2) fltk,  
> libdnet, winpcap, xvidcore.

Okay, here is what I've done so far:

guile

    I verified that their latest release (2.0.0) and latest Git version
    (4db853d7) don't fail with GCC-4.6 anymore, so there's no need to
    bother them.

    Moreover, I'm in contact with Guile to make the 2.0.0 version
    portable to win32 again. Until that happens, we'll have to stick
    with the outdated 1.8.7 version, using that compiler flag.

    Our test program wan't affected, so I removed the compiler flag there.

jpeg

    I fixed our test program. The compiler flag isn't needed anymore.

sdl

    I fixed our test program. The compiler flag isn't needed anymore.

sdl_mixer

    I fixed our test program. The compiler flag isn't needed anymore.

physfs

    I fixed the package (just two places in their sources) and
    proposed that patch to upstream. The compiler flag isn't
    needed anymore.

exiv2

    After some investigation I noticed that the "-no-undefined"
    is only meant to be used by libtool and not by GCC. Removing
    that option is the wrong way as it would make Exiv2 unable
    to build DLL files via MinGW anymore.

    The IMHO correct solution is to make sure that "-no-undefined"
    is not passed to GCC by the configure checks, by adding it
    to LDFLAGS as lately as possible:

    http://dev.exiv2.org/issues/767

xine-lib

    This was essentially the same issue as with exiv2:

    https://bugs.xine-project.org/show_bug.cgi?id=411



Greets,
Volker

-- 
Volker Grabsch
---<<(())>>---



reply via email to

[Prev in Thread] Current Thread [Next in Thread]