April 2011 - openSUSE MinGW - openSUSE Mailing Lists

mingw32-cross-gcc and -Wunused-function
by Roger Oberholtzer 06 Apr '11

06 Apr '11

I have a question about a warning I get with the mingw32 gcc cross compiler that I do not get with the linux version of the compiler, when compiling the same source. I have an include file that defines a few static inline functions. Obviously every file that includes this file will not use the defined function. The mingw32 compiler complains as follows: mcaio.h:322:28: warning: 'LswapInt' defined but not used [-Wunused-function] The code in the include file is: static inline unsigned int LswapInt(unsigned int val) { unsigned char *data = (unsigned char *) &val; return ((data[0] << 24) | (data[1] << 16) | (data[2] << 8) | (data[3])); } According to the gcc docs: -Wunused-function Warn whenever a static function is declared but not defined or a non-inline static function is unused. I do not think it should be complaining about this. It has been this way for the past few releases of the mingw32 compiler. As some of these inline functions are declared in files that get included a lot, I get quite a few spurious warnings. I am currently running the compiler in mingw32-cross-gcc-4.6.0-8.1.i586 Have I specified something wrong here? Yours sincerely, Roger Oberholtzer OPQ Systems / Ramböll RST Office: Int +46 10-615 60 20 Mobile: Int +46 70-815 1696 roger.oberholtzer(a)ramboll.se ________________________________________ Ramböll Sverige AB Krukmakargatan 21 P.O. Box 17009 SE-104 62 Stockholm, Sweden www.rambollrst.se -- To unsubscribe, e-mail: opensuse-mingw+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-mingw+help(a)opensuse.org

2 2

is _mingw32_makeinstall macro useful?
by Maarten Bosmans 06 Apr '11

06 Apr '11

The ${_mingw32_makeinstall} macro from mingw32-filesystem seems broken. The reason is that ${buildroot} is empty. IIRC it used to be the same as $RPM_BUILD_ROOT. Has anything changed? Anyway, the canonical way to make install seems to be make DESTDIR=$RPM_BUILD_ROOT install but a simple ${_mingw32_makeinstall} seems more clean to me. But the advantage of the DESTDIR approach is that even when a Makefile.am file defines a custom dir not listed in mingw32-filesystem (pulseaudio defines such an extra dir), the files get installed in the expected location. Maarten -- To unsubscribe, e-mail: opensuse-mingw+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-mingw+help(a)opensuse.org

2 1

new package for lcms2?
by Maarten Bosmans 04 Apr '11

04 Apr '11

Hi, I have used the latest version of LittleCMS (v2.1) in my home project. https://build.opensuse.org/package/rdiff?opackage=mingw32-lcms&oproject=win… It builds and works fine. Should I make a submit request of that diff (please don't pull now, as it needs some tweaking), or should I make a new package mingw32-lcms2, as the tarball and binaries now all have a 2 suffix? Maarten -- To unsubscribe, e-mail: opensuse-mingw+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-mingw+help(a)opensuse.org

2 1