Re: gcc-4.8.2-1: /bin/gcc fails

[Corinna Vinschen <corinna-cygwin@cygwin.com>]

[-- Attachment #1: Type: text/plain, Size: 1199 bytes --]

On Nov  1 23: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

Uh oh.  That's bad.  Maybe it wasn't such a good idea to switch
libexecdir from /usr/lib to /usr/libexec?  It breaks applications
using relative paths to search other application components when
run from /bin.

Either we revert libexecdir to /usr/lib, or we will need to add an
automount point /libexec -> /usr/libexec as for /bin and /lib.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]