This is the mail archive of the
mailing list for the Cygwin project.
Re: Building cross toolchain on cygwin from source
- From: Michael Enright <mike at kmcardiff dot com>
- To: cygwin at cygwin dot com
- Date: Tue, 29 Sep 2015 23:46:02 -0700
- Subject: Re: Building cross toolchain on cygwin from source
- Authentication-results: sourceware.org; auth=none
- References: <CAKuw2Eo8r8VSRQ0iEiZr_6H9GEQ=fHgMzyK8ztj+yer20Ng4bQ at mail dot gmail dot com> <CAOC2fq87f4b8LESynWX0ij=3kqXhi0GLm-KYv+491OheyWmWvA at mail dot gmail dot com> <CAKuw2ErpaDcBnE81-Z+eJetp3yb1_GRPbUbRh-XhFx5cQWDYdQ at mail dot gmail dot com>
On Tue, Sep 29, 2015 at 10:06 PM, Hari Narasimhan H.N wrote:
> I am using a crosstool-NG system. During configuration of GMP it
> throws the following error
> "could not find a working compiler"
> whereas I have gcc4.9.3 installed and working.
You should be able to tell from config.log what GMP's configure tried
to use as the compiler. GCC is capable of being compiled with an old
compiler and that applies equally to creating a native compiler or a
My best guess is that this problem is not a Cygwin problem. I have had
that same error message from configure scripts run under Linux,
attempting to cross-compile various open-source libraries, and it
comes down to some over-looked detail in the configure arguments that
impact how the script finds the compiler to use. Possibly a good
question for Stack Overflow.
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple