On 2013-12-05 22:48, wynfield wrote: > I understand that on cygwin /bin and /usr/bin both point to the same > directory.
Correct. > Given that and that the ming2-w64 gcc program is shown to be the exact same > length and have the same md5sums, I assumed that they were all equal. > > -rwxr-xr-x 2 692765 Dec 1 /bin/i686-w64-mingw32-gcc > -rwxr-xr-x 2 692765 Dec 1 /bin/i686-w64-mingw32-gcc.exe > -rwxr-xr-x 2 692765 Dec 1 /usr/bin/i686-w64-mingw32-gcc > -rwxr-xr-x 2 692765 Dec 1 /usr/bin/i686-w64-mingw32-gcc.exe > > But the gcc in /usr/bin/ works nand the one in /bin does not. > What magic causes the different behavior? These frontends call to the backends (cc1, etc. in $libexecdir) relative to themselves (e.g. ../libexec/gcc/$target/$version/cc1). The problem with using /bin/$target-gcc is that there is no /libexec directory, just a /usr/libexec. If gcc is configured with --libexecdir=/usr/lib (as it was previously), then this is not an issue, as /lib == /usr/lib as well. But where are you seeing gcc referenced under /bin instead of /usr/bin? Yaakov Cygwin Ports ------------------------------------------------------------------------------ Sponsored by Intel(R) XDK Develop, test and display web and hybrid apps with a single code base. Download it for free now! http://pubads.g.doubleclick.net/gampad/clk?id=111408631&iu=/4140/ostg.clktrk _______________________________________________ Mingw-w64-public mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
