Re: [fltk.general] Re: FLTK msys2 initial step fails - Forums

Linking help_dialog.exe...
Compiling icon.cxx...
icon.cxx: In function 'void choice_cb(Fl_Widget*, void*)':
icon.cxx:27:38: warning: 'buffer' may be used uninitialized [-Wmaybe-uninitialized]
   27 |   Fl_RGB_Image icon(buffer, 32, 32, 3);
      |                                      ^
In file included from ../FL/Fl_Bitmap.H:22,
                 from ../FL/Fl_Window.H:25,
                 from ../FL/Fl_Double_Window.H:23,
                 from icon.cxx:18:
../FL/Fl_Image.H:333:3: note: by argument 2 of type 'const uchar*' {aka 'const unsigned char*'} to 'Fl_RGB_Image::Fl_RGB_Image(const uchar*, int, int, int, int)' declared here
333 |   Fl_RGB_Image(const uchar *bits, int W, int H, int D=3, int LD=0);
      |   ^~~~~~~~~~~~
icon.cxx:26:9: note: 'buffer' declared here
   26 |   uchar buffer[32*32*3];
      |         ^~~~~~
Linking icon.exe...
Compiling iconize.cxx...
Linking iconize.exe...
Compiling image.cxx...
Linking image.exe...
Generating inactive.cxx and header from inactive.fl...

Task manager shows fluid process running. created dump but file was too large to upload.

On Wednesday, November 24, 2021 at 1:46:44 PM UTC-8 er...@seriss.com wrote:

On 11/24/21 1:29 PM, Ian MacArthur wrote:

Hmm - what compiler actually is that? There are a few things you get that I don’t seem to see, and some things look “wrong”...

What does “g++ -v” actually report in your Msys2 shell?

    I'll await the OP's response to that question as well.

    What it "should be", assuming msys2 was installed recently (today),
    I get version 11.2.0 (Rev2):

Using built-in specs.COLLECT_GCC=C:\msys64\mingw64\bin\g++.exeCOLLECT_LTO_WRAPPER=C:/msys64/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/11.2.0/lto-wrapper.exeTarget: x86_64-w64-mingw32Configured with: ../gcc-11.2.0/configure --prefix=/mingw64 --with-local-prefix=/mingw64/local --build=x86_64-w64-mingw32 --host=x86_64-w64-mingw32 --target=x86_64-w64-mingw32 --with-native-system-header-dir=/mingw64/x86_64-w64-mingw32/include --libexecdir=/mingw64/lib --enable-bootstrap --enable-checking=release --with-arch=x86-64 --with-tune=generic --enable-languages=c,lto,c++,fortran,ada,objc,obj-c++,jit --enable-shared --enable-static --enable-libatomic --enable-threads=posix --enable-graphite --enable-fully-dynamic-string --enable-libstdcxx-filesystem-ts --enable-libstdcxx-time --disable-libstdcxx-pch --disable-libstdcxx-debug --enable-lto --enable-libgomp --disable-multilib --disable-rpath --disable-win32-registry --disable-nls --disable-werror --disable-symvers --with-libiconv --with-system-zlib --with-gmp=/mingw64 --with-mpfr=/mingw64 --with-mpc=/mingw64 --with-isl=/mingw64 --with-pkgversion='Rev2, Built by MSYS2 project' --with-bugurl=https://github.com/msys2/MINGW-packages/issues --with-gnu-as --with-gnu-ld --with-boot-ldflags='-pipe -Wl,--dynamicbase,--high-entropy-va,--nxcompat,--default-image-base-high -Wl,--disable-dynamicbase -static-libstdc++ -static-libgcc' 'LDFLAGS_FOR_TARGET=-pipe -Wl,--dynamicbase,--high-entropy-va,--nxcompat,--default-image-base-high' --enable-linker-plugin-flags='LDFLAGS=-static-libstdc++\ -static-libgcc\ -pipe\ -Wl,--dynamicbase,--high-entropy-va,--nxcompat,--default-image-base-high\ -Wl,--stack,12582912'Thread model: posixSupported LTO compression algorithms: zlib zstdgcc version 11.2.0 (Rev2, Built by MSYS2 project)

Compiling gzlib.c...
gzlib.c: In function ‘gz_open’:
gzlib.c:243:20: warning: implicit declaration of function ‘_wopen’; did you mean ‘fwopen’? [-Wimplicit-function-declaration]
243 |         fd == -2 ? _wopen(path, oflag, 0666) :
      |                    ^~~~~~
      |                    fwopen

That looks odd - I don't recall my “fresh” build from earlier today doing that.
This may well be the warning from PNG that Greg mentions, though I imagine.

    Actually, that's not one of the warnings I got.

    I opened issue #296 regarding the warnings I got this morning:
    https://github.com/fltk/fltk/issues/296