The missing commands are binutils commands, not gcc commands, but I suppose gcc-mingw32 could provide them (rather than introduction a binutils compatibility package).
My real question is, does the lack of these commands cause issues? The idea behind gcc-mingw32 is just to provide compatibility symlinks to allow autoconf etc. to find the compiler (and related tools) even when using the old i586-mingw32msvc triplet. I tested a variety of programs using that triplet with the new gcc-mingw32 package and they built successfully; the binutils tools actually end up being found with the i686-w64-mingw32 triplet:
Hi Roberto,
The missing commands are binutils commands, not gcc commands, but I suppose gcc-mingw32 could provide them (rather than introduction a binutils compatibility package).
My real question is, does the lack of these commands cause issues? The idea behind gcc-mingw32 is just to provide compatibility symlinks to allow autoconf etc. to find the compiler (and related tools) even when using the old i586-mingw32msvc triplet. I tested a variety of programs using that triplet with the new gcc-mingw32 package and they built successfully; the binutils tools actually end up being found with the i686-w64-mingw32 triplet:
% i586-mingw32msv c-gcc -print-prog-name=ld i686-w64- mingw32- ld
/usr/bin/
Regards,
Stephen