error: could not find a working compiler
Hari Narasimhan H.N
hari.narasimhanhn at gmail.com
Sat Jul 18 05:48:35 UTC 2015
Thanks for your reply. I will compare the two config.log files again and
get back to you if I face any problem.
Meanwhile, could you please let me know what does the error "could not find
a working compiler" mean in general, since I already have a working gcc
(gcc4.9.3) installed, verified and working.
On Fri, Jul 17, 2015 at 8:27 PM, Torbjörn Granlund <tg at gmplib.org> wrote:
> "Hari Narasimhan H.N" <hari.narasimhanhn at gmail.com> writes:
> Yes, I did. I had done this exercise on ubuntu (sun virtual box) and was
> successful. This error is appearing only on cygwin. The config.log in
> cases is the same.
> Er, this does not make sense. You say that a successful build had the
> same config.log contents as an unsuccessful build? Then, a successful
> build had fatal error messages in config.log, or an unsuccessful build
> had a config.log which appears fine.
> Please try again: Read config log from the unsuccessful build. It is
> not hard, and it should enlighten you on what needs to be adjusted on
> your system, or how to correctly tailor you configure command in order
> to accomodate your system's quirks.
> Uploading the config.log file is blocked here at my workplace.
> This should be no problem, reading config.log does not require a GMP
> Please encrypt, key id 0xC8601622
More information about the gmp-bugs