Compiled executables requiring admin rights - different results between MinGW host type
Tony Kelman
kelman@berkeley.edu
Tue Mar 11 20:59:00 GMT 2014
Hi, I'm looking at a very simple 32-line c file, source is available here
https://github.com/JuliaLang/julia/blob/master/contrib/stringpatch.c
I'm seeing unpredictable results w.r.t. the compiled executable requiring
admin rights to run, depending which host compiler is used.
Under 32 bit Cygwin:
gcc -o stringpatch-cyg stringpatch.c # requires admin rights
i686-pc-mingw32-gcc -o stringpatch-pc-32 stringpatch.c # requires admin
rights
i686-w64-mingw32-gcc -o stringpatch-w64-32 stringpatch.c # requires admin
rights
x86_64-w64-mingw32-gcc -o stringpatch-w64-64 stringpatch.c # does not
require admin rights
Under 64 bit Cygwin:
gcc -o stringpatch-cyg stringpatch.c # does not require admin rights
i686-pc-mingw32-gcc -o stringpatch-pc-32 stringpatch.c # requires admin
rights
i686-w64-mingw32-gcc -o stringpatch-w64-32 stringpatch.c # requires admin
rights
x86_64-w64-mingw32-gcc -o stringpatch-w64-64 stringpatch.c # does not
require admin rights
What is the explanation for this discrepancy? Is this expected behavior? Is
there an easy way to prevent any of the compiled executables from requiring
admin rights?
All the compilers are version 4.8.2, with the exception of
i686-pc-mingw32-gcc which is version 4.7.3 in both 32 and 64 bit. Cygcheck
contents for both installations are posted here
https://gist.github.com/9492379. If providing any additional info would be
useful, please let me know.
Thanks,
Tony
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
More information about the Cygwin
mailing list