From: jojelino <jojelino@gmail.com>
To: cygwin@cygwin.com
Subject: Re: gcc-4.8.2-1: /bin/gcc fails
Date: Fri, 22 Nov 2013 19:02:00 -0000 [thread overview]
Message-ID: <l6o9mq$60f$1@ger.gmane.org> (raw)
In-Reply-To: <52749A63.70803@acm.org>
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
next prev parent reply other threads:[~2013-11-22 19:02 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-02 6:23 David Rothenberger
2013-11-02 9:36 ` Corinna Vinschen
2013-11-03 4:54 ` Yaakov (Cygwin/X)
2013-11-03 19:22 ` David Rothenberger
2013-11-04 11:42 ` Corinna Vinschen
2013-11-04 14:45 ` Charles Wilson
2013-11-04 17:35 ` Andrey Repin
2013-11-05 2:18 ` Yaakov (Cygwin/X)
2013-11-05 9:52 ` Corinna Vinschen
2013-11-05 16:03 ` Charles Wilson
2013-11-05 16:18 ` Corinna Vinschen
2013-11-05 3:05 ` Andrey Repin
2013-11-05 3:39 ` Robert Pendell
2013-11-05 4:20 ` Robert Pendell
2013-11-05 6:35 ` Andrey Repin
2013-11-10 18:08 ` Bengt Larsson
2013-11-22 19:02 ` jojelino [this message]
2013-11-22 19:36 ` jojelino
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='l6o9mq$60f$1@ger.gmane.org' \
--to=jojelino@gmail.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).