On 2013-11-02 PM 3:23, David Rothenberger wrote:
With gcc-4.8.2-1, the following fails:
% touch /tmp/t.c
% /bin/gcc -c /tmp/t.c
gcc: error: spawn: No such file or directory
This works correctly if gcc is invoked as "gcc" or "/usr/bin/gcc".
It also works correctly with 4.8.1.
It appears this is due to a change from /usr/lib to /usr/libexec.
/bin/gcc attempts to find cc1 under "/bin/../libexec/...". In 4.8.1,
this was "/bin/../lib/...", which works because /lib is mapped to
/usr/lib by Cygwin. /usr/bin/gcc uses "/usr/bin/../libexec" which
also works fine.
I can work around the problem as follows:
% ln -s /libexec /usr/libexec
This problem is caused by zero-byte of
${builddir}/host-i686-pc-cygwin/specs
and the specs file is created by bootstrapped gcc executable.
the bootstrapped gcc crashes when generating specs file, which is the
cause of the problem mentioned in this report. the maintainer of gcc
should have experienced this problem.
to workaround this problem, the package maintainer needed to supress
C{XX}FLAGS -static-libgcc -static-libstdc++ in
host-i686-pc-cygwin/gcc/Makefile.
--
Regards.
--
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
