From: Tim Prince <TimothyPrince@sbcglobal.net>
To: Angelo Graziosi <angelo.graziosi@alice.it>
Cc: Fortran <fortran@gcc.gnu.org>, GCC <gcc@gcc.gnu.org>
Subject: Re: Failure building current 4.5 snapshot on Cygwin
Date: Fri, 26 Jun 2009 14:33:00 -0000 [thread overview]
Message-ID: <4A44D72B.4030406@sbcglobal.net> (raw)
In-Reply-To: <4A44A724.6040804@alice.it>
Angelo Graziosi wrote:
> I want to flag the following failure I have seen on Cygwin 1.5 trying to
> build current 4.5-20090625 gcc snapshot:
> checking whether the C compiler works... configure: error: in
> `/tmp/build/intl':
> configure: error: cannot run C compiled programs.
> If you meant to cross compile, use `--host'.
> See `config.log' for more details.
I met the same failure on Cygwin 1.7 with yesterday's and last week's
snapshots. I didn't notice that it refers to intl/config.log, so will go
back and look, as you didn't show what happened there.
On a slightly related subject, I have shown that the libgfortran.dll.a and
libgomp.dll.a are broken on cygwin builds, including those released for
cygwin, as shown on the test case I submitted on cygwin list earlier this
week. The -enable-shared has never been satisfactory for gfortran cygwin.
next prev parent reply other threads:[~2009-06-26 14:12 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-26 11:18 Angelo Graziosi
2009-06-26 11:42 ` Dave Korn
2009-06-26 13:09 ` Angelo Graziosi
2009-06-26 13:19 ` Seiji Kachi
2009-06-26 13:52 ` Kai Tietz
2009-06-26 15:59 ` Tim Prince
2009-06-26 16:28 ` Kai Tietz
2009-06-26 16:36 ` Steve Kargl
2009-06-26 17:01 ` Angelo Graziosi
2009-06-26 17:06 ` Steve Kargl
2009-06-26 17:29 ` Tim Prince
2009-06-27 0:55 ` Seiji Kachi
2009-08-23 6:45 ` Eric Niebler
2009-08-23 10:16 ` Ralf Wildenhues
2009-08-23 22:26 ` Eric Niebler
2009-06-26 15:41 ` Tim Prince
2009-06-26 14:33 ` Tim Prince [this message]
2009-08-23 14:20 Angelo Graziosi
2009-08-23 17:57 ` Eric Niebler
2009-08-23 18:08 ` Tim Prince
2009-08-23 19:59 ` Eric Niebler
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=4A44D72B.4030406@sbcglobal.net \
--to=timothyprince@sbcglobal.net \
--cc=angelo.graziosi@alice.it \
--cc=fortran@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=tprince@computer.org \
/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).