[SOLVED] GMP-5.1.1: ABI=32 ./configure --prefix=/usr --enable-cxx

potterius · 05-07-2013, 04:12 AM

excuse me, sorry I always asking again, again and again. :Peace:

Im now at chapter 6.14 GMP-5.1.1.
and I have a problem about this

Code:

ABI=32 ./configure --prefix=/usr --enable-cxx

and the output show like this

Code:

checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether to enable maintainer-specific portions of Makefiles... no
checking ABI=32
checking compiler gcc -m32 -O2 -pedantic -fomit-frame-pointer ... no
checking compiler gcc -O2 -pedantic -fomit-frame-pointer ... no
checking compiler icc -no-gcc ... no
checking whether cc is gcc... yes
checking compiler cc -m32 -O2 -pedantic -fomit-frame-pointer ... no
checking compiler cc -O2 -pedantic -fomit-frame-pointer ... no
configure: error: could not find a working compiler, see config.log for details

when I ignore it, and continue to make.
show the notification on my terminal

Code:

make: *** No targets specified and no makefile found.  Stop.

please help me

druuna · 05-07-2013, 04:18 AM

Why are you running:

Code:

ABI=32 ./configure --prefix=/usr --enable-cxx

instead of:

Code:

./configure --prefix=/usr --enable-cxx

Does this apply to you (quote from the book):

Quote:

Note

If you are building for 32-bit x86, but you have a CPU which is capable of running 64-bit code and you have specified CFLAGS in the environment, the configure script will attempt to configure for 64-bits and fail. Avoid this by invoking the configure command below with

Code:

ABI=32 ./configure ...

potterius · 05-07-2013, 04:30 AM

Quote:

Originally Posted by druuna

Why are you running:

Code:

ABI=32 ./configure --prefix=/usr --enable-cxx

instead of:

Code:

./configure --prefix=/usr --enable-cxx

Does this apply to you (quote from the book):

I running

Code:

ABI=32 ./configure --prefix=/usr --enable-cxx

coz in my book tutorial says that. my referensi tutorial http://pastebin.com/zz77D7uw

I also runing this code

Code:

./configure --prefix=/usr --enable-cxx

, but still error, and the notif same like before.

druuna · 05-07-2013, 04:47 AM

Quote:

Originally Posted by potterius

I running

Code:

ABI=32 ./configure --prefix=/usr --enable-cxx

coz in my book tutorial says that. my referensi tutorial http://pastebin.com/zz77D7uw

That's not the LFS book, that's a collection of commands, which might not be correct for your situation. Follow the real LFS book

Quote:

I also runing this code

Code:

./configure --prefix=/usr --enable-cxx

, but still error, and the notif same like before.

Did you remove the source directory first and start from extracting the gmp package?

potterius · 05-07-2013, 05:21 AM

Quote:

Originally Posted by druuna

That's not the LFS book, that's a collection of commands, which might not be correct for your situation. Follow the real LFS book

Did you remove the source directory first and start from extracting the gmp package?

what directory?
I remove direcory on binutils

Code:

rm -rf $LFS/sources/binutils-build/
rm -rf $LFS/sources/binutils-2.23.1/

and then continue to next step(GMP-5.1.1)

druuna · 05-07-2013, 05:47 AM

Quote:

Originally Posted by potterius

what directory?

The /sources/gmp-5.1.1 directory.

If a package build fails and you need to redo that specific package you first need to remove the created source directory, untar the package again, enter the created directory and start form the to of the chapter.

Quote:

I remove direcory on binutils

Code:

rm -rf $LFS/sources/binutils-build/
rm -rf $LFS/sources/binutils-2.23.1/

and then continue to next step(GMP-5.1.1)

If you need to use $LFS while doing chapter 6 then something is really wrong! Once you are inside the chrooted environment this variable is not longer needed/set.

potterius · 05-07-2013, 06:30 AM

Quote:

Originally Posted by druuna

The /sources/gmp-5.1.1 directory.

If a package build fails and you need to redo that specific package you first need to remove the created source directory, untar the package again, enter the created directory and start form the to of the chapter.
If you need to use $LFS while doing chapter 6 then something is really wrong! Once you are inside the chrooted environment this variable is not longer needed/set.

I was doing again, untar, n tar again, but still error.

and I using root in chapter 6, I don't use lfs user anymnore.

druuna · 05-07-2013, 06:43 AM

I notice this in the output shown in post #1:

Quote:

configure: error: could not find a working compiler, see config.log for details

This might point to an earlier problem.

I'm not able to point you to anything specific, things that come to mind are:

- a mistake was made in chapter 5, probably the gcc package,
- forgetting to mount before (re)entering chrooted environment (6.2.2 and 6.2.3),
- not using the correct chroot command (6.4),
- adjusting the toolchain did not go as planned,
- ???

Maybe it would be a good idea to remove everything, restore the backup made in chapter 5.34 and start from the top of chapter 6 (6.2).

Also: did you check the mentioned config.log?

EDIT: I just had a look at the so called book you use and it _does_ use $LFS for building in chapter 6, which is wrong!!

potterius · 05-07-2013, 07:21 AM

Quote:

Originally Posted by druuna

I notice this in the output shown in post #1: This might point to an earlier problem.

I'm not able to point you to anything specific, things that come to mind are:

- a mistake was made in chapter 5, probably the gcc package,
- forgetting to mount before (re)entering chrooted environment (6.2.2 and 6.2.3),
- not using the correct chroot command (6.4),
- adjusting the toolchain did not go as planned,
- ???

Maybe it would be a good idea to remove everything, restore the backup made in chapter 5.34 and start from the top of chapter 6 (6.2).

Also: did you check the mentioned config.log?

EDIT: I just had a look at the so called book you use and it _does_ use $LFS for building in chapter 6, which is wrong!!

druuna, I forget to input this code

Code:

chroot "$LFS" /tools/bin/env -i \
    HOME=/root                  \
    TERM="$TERM"                \
    PS1='\u:\w\$ '              \
    PATH=/bin:/usr/bin:/sbin:/usr/sbin:/tools/bin \
    /tools/bin/bash --login +h

hahaha, sorry druuna, it's my foult.
thanks to remember me about chroot.hahahaha
thx again druuna

CoolDown · 02-25-2016, 11:32 AM

I posted a new thread instead here - click