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: Mark Brand
Subject: Re: [Mingw-cross-env-list] gcc 4.6.0
Date: Sat, 26 Mar 2011 23:09:39 +0100
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.14) Gecko/20110221 SUSE/3.1.8 Thunderbird/3.1.8

Hi Volker,

1. Addition of -Wno-unused-but-set-variable
>  This was needed for compiling our test programs for guile, jpeg, sdl,
>  sdl_mixer.
>  Otherwise needed for:
>  guile
>  physfs
>
>  2. Removal of apparently obsolete gcc flag -mno-cygwin
>  Used sed to strip from configure script.
>  Needed for:
>  fltk
>  libdnet
>  winpcap
>  xvidcore
>
>  3. Removal of apparently obsolete gcc flag -no-undefined
>  Used sed to strip from configure script.
>  Needed for:
>  exiv2
>  xine-lib
>
>  I'm not sure it's worth the trouble to contact the upstream projects
>  about 1,2 and 3. What do you think?
I'm sure that for 2) it's really worth the trouble, so the projects
should be contacted.

For 3) I'm not sure how this "-no-undefined" option went into the
build system. Maybe those projects just need to upgrade their
autoconf or automake?

For 1), I guess it is not worth the trouble, as the extra option
for the test programs doesn't really hurt anyone.

Since 1) affects guile and physfs themselves (not just the test programs), it probably merits the same classification as 2) for upstream notification. Rather than introducing -Wno-unused-but-set-variable though, they should probably clean up the offending code.

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.

regards,

Mark



reply via email to

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