Aug. 12, 2013
11:10 a.m.
On Mon, Aug 5, 2013, at 1:07, Ryan wrote:
Here are my experiences in accidently getting a .so/.dll file for the wrong chip/CPU type:
Windows:
%1 is not a valid Win32 application
There's got to be some way to fill in %1 with the name of the dll. But a look through the list of all windows error messages on my system shows a bunch with %values that the caller could not possibly know.