GMP incorrectly detects CPU-VENDOR-OS triplet
Ticket #2661 On my x86_64 machine ./config.guess script of GMP 5.01 (and 5.00 as well) returns 'athlon-unknown-linux-gnu' which is incorrectly considered by ./configure script as 32-bit platform, so it expects sizeof(long) to be 4, when it is actually 8: checking compiler cc -O2 -pedantic -fomit-frame-pointer has sizeof (long)==4... no which results in a compiler error: configure: error: could not find a working compiler, see config.log for details This bug can be avoided by specifying --build=x86_64-unknown-linux-gnu option to ./configure script, but without knowing that your whole LFS assembly stops. Coreutils 8.4 uname -a Linux lfslivecd 2.6.22.5-64bit #1 SMP Thu Nov 29 07:28:23 GMT 2007 x86_64 x86_64 x86_64 GNU/Linux -- Looking at GMP. they have two scripts: config.guess and configfsf.guess. Their config.guess is returning athlon. You might want to try to run those to test the results. Looking at the contents of config.guess, it looks like the cpu is being misidentified. I'd try copying configfsf.guess to overwrite config.guess and see if that makes a difference. Also, what is the contents of `cat /proc/cpuinfo` -- Bruce -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: GMP incorrectly detects CPU-VENDOR-OS triplet
Hi, I have faced the same problem. I have used kvm to build LFS, when I ran configure from GMP, it generate an error saying no suitable compiler found for pentium2-unlnown-linux-gnu. actually my machine is x86_64-unknown-linux-gnu. I had to manually specify it using build option. Regards, On Sat, May 15, 2010 at 12:03 AM, Bruce Dubbs bruce.du...@gmail.com wrote: Ticket #2661 On my x86_64 machine ./config.guess script of GMP 5.01 (and 5.00 as well) returns 'athlon-unknown-linux-gnu' which is incorrectly considered by ./configure script as 32-bit platform, so it expects sizeof(long) to be 4, when it is actually 8: checking compiler cc -O2 -pedantic -fomit-frame-pointer has sizeof (long)==4... no which results in a compiler error: configure: error: could not find a working compiler, see config.log for details This bug can be avoided by specifying --build=x86_64-unknown-linux-gnu option to ./configure script, but without knowing that your whole LFS assembly stops. Coreutils 8.4 uname -a Linux lfslivecd 2.6.22.5-64bit #1 SMP Thu Nov 29 07:28:23 GMT 2007 x86_64 x86_64 x86_64 GNU/Linux -- Looking at GMP. they have two scripts: config.guess and configfsf.guess. Their config.guess is returning athlon. You might want to try to run those to test the results. Looking at the contents of config.guess, it looks like the cpu is being misidentified. I'd try copying configfsf.guess to overwrite config.guess and see if that makes a difference. Also, what is the contents of `cat /proc/cpuinfo` -- Bruce -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page -- Prashant R Keshvani, Systems Software Engineer, Cell :- 09227945799 (Surat) -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: GMP incorrectly detects CPU-VENDOR-OS triplet
On 14 May 2010 20:03, Prashant R Keshvani (Baijoo) prashant2...@gmail.com wrote: Hi, I have faced the same problem. I have used kvm to build LFS, when I ran configure from GMP, it generate an error saying no suitable compiler found for pentium2-unlnown-linux-gnu. actually my machine is x86_64-unknown-linux-gnu. I had to manually specify it using build option. Regards, I think we're still missing something here, but I don't know what it is. The original report was 'athlon-unknown-linux-gnu', and the problem is that he was building 64-bit - that is a 32-bit host. In my own case, the logs show athlon64-unknown-linux-gnu for 64-bit. See also the discussion about ticket 2648 on -dev last weekend. Were you using a 32-bit vm with a 64-bit kernel ? ALso, was the original 'athlon-unknown-linux-gnu' reporter in a vm ? ĸen -- After tragedy, and farce, OMG poneys! -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: GMP incorrectly detects CPU-VENDOR-OS triplet
On Fri, 14 May 2010 22:20:32 +0100 Ken Moffat zarniwhoo...@googlemail.com wrote: On 14 May 2010 20:03, Prashant R Keshvani (Baijoo) prashant2...@gmail.com wrote: Hi, I have faced the same problem. I have used kvm to build LFS, when I ran configure from GMP, it generate an error saying no suitable compiler found for pentium2-unlnown-linux-gnu. actually my machine is x86_64-unknown-linux-gnu. I had to manually specify it using build option. Regards, I think we're still missing something here, but I don't know what it is. The original report was 'athlon-unknown-linux-gnu', and the problem is that he was building 64-bit - that is a 32-bit host. In my own case, the logs show athlon64-unknown-linux-gnu for 64-bit. See also the discussion about ticket 2648 on -dev last weekend. Were you using a 32-bit vm with a 64-bit kernel ? ALso, was the original 'athlon-unknown-linux-gnu' reporter in a vm ? ĸen Wasn't it that there was some kludge about setting the enviroment variable named ABI for a succesful gmp build? I sort of remember having GMP hit me in the head last summer with it. And then it went away.. Was it when I upgraded to 64-bit? Can't remember. -AKuktin -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: GMP incorrectly detects CPU-VENDOR-OS triplet
I've met something like that when I turn on optimize in jhalfs. I fix it by ./configure ABI=32. 2010/5/15 Aleksandar Kuktin akuk...@gmail.com On Fri, 14 May 2010 22:20:32 +0100 Ken Moffat zarniwhoo...@googlemail.com wrote: On 14 May 2010 20:03, Prashant R Keshvani (Baijoo) prashant2...@gmail.com wrote: Hi, I have faced the same problem. I have used kvm to build LFS, when I ran configure from GMP, it generate an error saying no suitable compiler found for pentium2-unlnown-linux-gnu. actually my machine is x86_64-unknown-linux-gnu. I had to manually specify it using build option. Regards, I think we're still missing something here, but I don't know what it is. The original report was 'athlon-unknown-linux-gnu', and the problem is that he was building 64-bit - that is a 32-bit host. In my own case, the logs show athlon64-unknown-linux-gnu for 64-bit. See also the discussion about ticket 2648 on -dev last weekend. Were you using a 32-bit vm with a 64-bit kernel ? ALso, was the original 'athlon-unknown-linux-gnu' reporter in a vm ? ĸen Wasn't it that there was some kludge about setting the enviroment variable named ABI for a succesful gmp build? I sort of remember having GMP hit me in the head last summer with it. And then it went away.. Was it when I upgraded to 64-bit? Can't remember. -AKuktin -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
