Here's your first bug report:
Remember the packaging bug in the first binutils 2.18.50 tech preview that
was pinned down in the "Necessary environment path settings" thread? This
release gets at that same issue from the other direction. Since it was
configured without a specific --build, --host or --target, it defaulted to
the autodetected "i386-pc-mingw32" platform string. However this means that
it looks for binutils in "<mingw>/i386-pc-mingw32/bin" rather than
"<mingw>/mingw32/bin". Suggested fix: add "--build=mingw32" to the configure
invocation. (As gleaned from
http://www.nabble.com/Re%3A-Standards-for-Building-MinGW-Release-Packages--(was%3A--Mingw-users--Necessary-environment-path-settings-)-p16360778.html.)
-John E.
-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace_______________________________________________
MinGW-dvlpr mailing list
MinGW-dvlpr@...
https://lists.sourceforge.net/lists/listinfo/mingw-dvlpr
