Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
Error with emerge --update --deep world w/ dev-libs/gmp-4.2.
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Installing Gentoo
View previous topic :: View next topic  
Author Message
dman777
Veteran
Veteran


Joined: 10 Jan 2007
Posts: 1004

PostPosted: Thu Feb 28, 2008 6:07 pm    Post subject: Error with emerge --update --deep world w/ dev-libs/gmp-4.2. Reply with quote

I just finished installing Gentoo on my computer. I did a emerge --update --deep world to update my system. I then got this message:
ERROR: dev-libs/gmp-4.2.2 failed
Call Stack:
ebuild.sh, line 49: Called src_compile
environment, line 2616: Called econf ;src_compile' 'src_compile'
'--localstateddir/var/state/gmp' '--disable-mpfr'
ebuild.sh, line 513: Called die
The specific snippet of code:
die "econf failed"


I am following the Gentoo Doc. for installation. So, I have not install X11 yet. I also updated my portage tree before I did this.

I don't know if this matters, but in my make.conf file I have these flags set to keep my system lite wieght: USE="-kde -gnome X jpeg tiff png"


Does anyone know why and what I should do?

Thanks,
-Darin
Back to top
View user's profile Send private message
schachti
Advocate
Advocate


Joined: 28 Jul 2003
Posts: 3765
Location: Gifhorn, Germany

PostPosted: Thu Feb 28, 2008 6:25 pm    Post subject: Reply with quote

Please give us the error message (about 20-30 more lines of output).
_________________
Never argue with an idiot. He brings you down to his level, then beats you with experience.

How-To: Daten verschlüsselt auf DVD speichern.
Back to top
View user's profile Send private message
dman777
Veteran
Veteran


Joined: 10 Jan 2007
Posts: 1004

PostPosted: Thu Feb 28, 2008 10:46 pm    Post subject: Reply with quote

>>> Unpacking source...
>>> Unpacking gmp-4.2.2.tar.bz2 to /var/tmp/portage/dev-libs/gmp-4.2.2/work
* Applying gmp-4.1.4-noexecstack.patch ...
 [ ok ]
* Applying gmp-4.2.2-ABI-multilib.patch ...
 [ ok ]
* Applying gmp-4.2.1-s390.diff ...
 [ ok ]
* Running elibtoolize in: gmp-4.2.2
* Applying install-sh-1.5.6.patch ...
* Applying portage-1.5.10.patch ...
* Applying sed-1.5.6.patch ...
>>> Source unpacked.
>>> Compiling source in /var/tmp/portage/dev-libs/gmp-4.2.2/work/gmp-4.2.2 ...
* econf: updating gmp-4.2.2/config.sub with /usr/share/gnuconfig/config.sub
* econf: updating gmp-4.2.2/config.guess with /usr/share/gnuconfig/config.guess
./configure --prefix=/usr --host=x86_64-pc-linux-gnu --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc --localstatedir=/var/lib --localstatedir=/var/state/gmp --disable-mpfr --disable-mpbsd --enable-cxx --build=x86_64-pc-linux-gnu
checking build system type... x86_64-pc-linux-gnu
checking host system type... x86_64-pc-linux-gnu
checking for a BSD-compatible install... /bin/install -c
checking whether build environment is sane... yes
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether to enable maintainer-specific portions of Makefiles... no
checking GMPABI=64
checking compiler gcc -march=opteron -O2 -pipe ... yes
checking for x86_64-pc-linux-gnu-gcc... gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ANSI C... none needed
checking how to run the C preprocessor... gcc -E
checking build system compiler gcc... yes
checking for build system preprocessor... gcc -E
checking for build system executable suffix...
checking whether build system compiler is ANSI... yes
checking for build system compiler math library... -lm
checking for x86_64-pc-linux-gnu-g++... no
checking for x86_64-pc-linux-gnu-c++... no
checking for x86_64-pc-linux-gnu-gpp... no
checking for x86_64-pc-linux-gnu-aCC... no
checking for x86_64-pc-linux-gnu-CC... no
checking for x86_64-pc-linux-gnu-cxx... no
checking for x86_64-pc-linux-gnu-cc++... no
checking for x86_64-pc-linux-gnu-cl... no
checking for x86_64-pc-linux-gnu-FCC... no
checking for x86_64-pc-linux-gnu-KCC... no
checking for x86_64-pc-linux-gnu-RCC... no
checking for x86_64-pc-linux-gnu-xlC_r... no
checking for x86_64-pc-linux-gnu-xlC... no
checking for g++... g++
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking C++ compiler g++ -march=opteron -O2 -pipe... yes
checking how to run the C++ preprocessor... g++ -E
checking for egrep... grep -E
using GMPABI="64"
CC="gcc"
CFLAGS="-march=opteron -O2 -pipe"
CPPFLAGS=""
CXX="g++"
CXXFLAGS="-march=opteron -O2 -pipe"
MPN_PATH=" x86_64 generic"
checking for function prototypes... yes
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking for string.h... (cached) yes
checking for x86_64-pc-linux-gnu-ar... no
checking for ar... ar
checking for BSD-compatible nm... /usr/bin/nm -B
checking for a sed that does not truncate output... /bin/sed
checking for ld used by gcc... /usr/i686-pc-linux-gnu/bin/ld
checking if the linker (/usr/i686-pc-linux-gnu/bin/ld) is GNU ld... yes
checking for /usr/i686-pc-linux-gnu/bin/ld option to reload object files... -r
checking whether ln -s works... yes
checking how to recognize dependent libraries... pass_all
checking dlfcn.h usability... yes
checking dlfcn.h presence... yes
checking for dlfcn.h... yes
checking how to run the C++ preprocessor... g++ -E
checking the maximum length of command line arguments... 98304
checking command to parse /usr/bin/nm -B output from gcc object... ok
checking for objdir... .libs
checking for x86_64-pc-linux-gnu-ar... ar
checking for x86_64-pc-linux-gnu-ranlib... no
checking for ranlib... ranlib
checking for x86_64-pc-linux-gnu-strip... no
checking for strip... strip
checking if gcc supports -fno-rtti -fno-exceptions... no
checking for gcc option to produce PIC... -fPIC
checking if gcc PIC flag -fPIC works... yes
checking if gcc static flag -static works... yes
checking if gcc supports -c -o file.o... yes
checking whether the gcc linker (/usr/i686-pc-linux-gnu/bin/ld -m elf_i386) supports shared libraries... yes
checking whether -lc should be explicitly linked in... no
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... yes
configure: creating libtool
appending configuration tag "CXX" to libtool
checking for ld used by g++... /usr/i686-pc-linux-gnu/bin/ld -m elf_i386
checking if the linker (/usr/i686-pc-linux-gnu/bin/ld -m elf_i386) is GNU ld... yes
checking whether the g++ linker (/usr/i686-pc-linux-gnu/bin/ld -m elf_i386) supports shared libraries... yes
checking for g++ option to produce PIC... -fPIC
checking if g++ PIC flag -fPIC works... yes
checking if g++ static flag -static works... yes
checking if g++ supports -c -o file.o... yes
checking whether the g++ linker (/usr/i686-pc-linux-gnu/bin/ld -m elf_i386) supports shared libraries... yes
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking for ANSI C header files... (cached) yes
checking whether time.h and sys/time.h may both be included... yes
checking fcntl.h usability... yes
checking fcntl.h presence... yes
checking for fcntl.h... yes
checking float.h usability... yes
checking float.h presence... yes
checking for float.h... yes
checking invent.h usability... no
checking invent.h presence... no
checking for invent.h... no
checking langinfo.h usability... yes
checking langinfo.h presence... yes
checking for langinfo.h... yes
checking locale.h usability... yes
checking locale.h presence... yes
checking for locale.h... yes
checking nl_types.h usability... yes
checking nl_types.h presence... yes
checking for nl_types.h... yes
checking sys/attributes.h usability... no
checking sys/attributes.h presence... no
checking for sys/attributes.h... no
checking sys/iograph.h usability... no
checking sys/iograph.h presence... no
checking for sys/iograph.h... no
checking sys/mman.h usability... yes
checking sys/mman.h presence... yes
checking for sys/mman.h... yes
checking sys/param.h usability... yes
checking sys/param.h presence... yes
checking for sys/param.h... yes
checking sys/processor.h usability... no
checking sys/processor.h presence... no
checking for sys/processor.h... no
checking sys/pstat.h usability... no
checking sys/pstat.h presence... no
checking for sys/pstat.h... no
checking sys/sysinfo.h usability... yes
checking sys/sysinfo.h presence... yes
checking for sys/sysinfo.h... yes
checking sys/syssgi.h usability... no
checking sys/syssgi.h presence... no
checking for sys/syssgi.h... no
checking sys/systemcfg.h usability... no
checking sys/systemcfg.h presence... no
checking for sys/systemcfg.h... no
checking sys/time.h usability... yes
checking sys/time.h presence... yes
checking for sys/time.h... yes
checking sys/times.h usability... yes
checking sys/times.h presence... yes
checking for sys/times.h... yes
checking for sys/resource.h... yes
checking for sys/sysctl.h... yes
checking for machine/hal_sysinfo.h... no
checking whether fgetc is declared... yes
checking whether fscanf is declared... yes
checking whether optarg is declared... yes
checking whether ungetc is declared... yes
checking whether vfprintf is declared... yes
checking whether sys_errlist is declared... yes
checking whether sys_nerr is declared... yes
checking return type of signal handlers... void
checking for intmax_t... yes
checking for long double... yes
checking for long long... yes
checking for ptrdiff_t... yes
checking for quad_t... yes
checking for uint_least32_t... yes
checking for preprocessor stringizing operator... yes
checking for working volatile... yes
checking whether <stdarg.h> exists and works... yes
checking whether gcc __attribute__ ((const)) works... yes
checking whether gcc __attribute__ ((malloc)) works... yes
checking whether gcc __attribute__ ((mode (XX))) works... yes
checking whether gcc __attribute__ ((noreturn)) works... yes
checking for inline... inline
checking for cos in -lm... yes
checking for working alloca.h... yes
checking for alloca (via gmp-impl.h)... yes
checking how to allocate temporary memory... alloca
checking whether byte ordering is bigendian... no
checking format of `double' floating point... IEEE little endian
checking for alarm... yes
checking for attr_get... no
checking for clock... yes
checking for clock_gettime... no
checking for cputime... no
checking for getpagesize... yes
checking for getrusage... yes
checking for gettimeofday... yes
checking for getsysinfo... no
checking for localeconv... yes
checking for memset... yes
checking for mmap... yes
checking for mprotect... yes
checking for nl_langinfo... yes
checking for obstack_vprintf... yes
checking for popen... yes
checking for processor_info... no
checking for pstat_getprocessor... no
checking for raise... yes
checking for read_real_time... no
checking for sigaction... yes
checking for sigaltstack... yes
checking for sigstack... yes
checking for syssgi... no
checking for strchr... yes
checking for strerror... yes
checking for strnlen... yes
checking for strtol... yes
checking for strtoul... yes
checking for sysconf... yes
checking for sysctl... yes
checking for sysctlbyname... no
checking for times... yes
checking for vsnprintf... yes
checking whether vsnprintf works... yes
checking whether sscanf needs writable input... no
checking for struct pst_processor.psp_iticksperclktick... no
checking sstream usability... yes
checking sstream presence... yes
checking for sstream... yes
checking for std::locale... yes
checking for suitable m4... m4
checking if m4wrap produces spurious output... no
checking how to switch to text section... .text
checking how to switch to data section... .data
checking for assembler label suffix... :
checking for assembler global directive... .globl
checking for assembler global directive attribute...
checking if globals are prefixed by underscore... no
checking how to switch to read-only data section... .section .rodata
checking for assembler .type directive... .type $1,@$2
checking for assembler .size directive... .size $1,$2
checking for assembler local label prefix... .L
checking for assembler byte directive... .byte
checking how to define a 32-bit word... .long
checking if .align assembly directive is logarithmic... no
checking if the .align directive accepts an 0x90 fill in .text... yes
checking for unsigned short... yes
checking size of unsigned short... 2
checking for unsigned... yes
checking size of unsigned... 4
checking for unsigned long... yes
checking size of unsigned long... 4
checking for mp_limb_t... yes
checking size of mp_limb_t... 4
configure: error: Oops, mp_limb_t is 32 bits, but the assembler code
in this configuration expects 64 bits.
You appear to have set $CFLAGS, perhaps you also need to tell GMP the
intended ABI, see "ABI and ISA" in the manual.

!!! Please attach the following file when seeking support:
!!! /var/tmp/portage/dev-libs/gmp-4.2.2/work/gmp-4.2.2/config.log
*
* ERROR: dev-libs/gmp-4.2.2 failed.
* Call stack:
* ebuild.sh, line 49: Called src_compile
* environment, line 2616: Called econf 'src_compile' 'src_compile' '--localstatedir=/var/state/gmp' '--disable-mpfr'
* ebuild.sh, line 513: Called die
* The specific snippet of code:
* die "econf failed"
* The die message:
* econf failed
*
* If you need support, post the topmost build error, and the call stack if relevant.
* A complete build log is located at '/var/tmp/portage/dev-libs/gmp-4.2.2/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/dev-libs/gmp-4.2.2/temp/environment'.
*



I hope this is read able enough.
What do you think?
Back to top
View user's profile Send private message
Nick C
Guru
Guru


Joined: 18 Mar 2005
Posts: 526
Location: Portsmouth, England

PostPosted: Thu Feb 28, 2008 10:55 pm    Post subject: Reply with quote

post your /etc/make.conf and emerge --info output.
Also what livecd are you using and are you doing a 32 or 64 bit install?
_________________
Please add [solved] to the initial post's subject line if you feel your problem is resolved.
www.monkeydust.net
Back to top
View user's profile Send private message
dman777
Veteran
Veteran


Joined: 10 Jan 2007
Posts: 1004

PostPosted: Thu Feb 28, 2008 11:03 pm    Post subject: Reply with quote

# These settings were set by the catalyst build script that automatically
# built this stage.
# Please consult /etc/make.conf.example for a more detailed example.
CFLAGS="-march=opteron -O2 -pipe"
CXXFLAGS="${CFLAGS}"
# This should not be changed unless you know exactly what you are doing. You
# should probably be using a different stage, instead.
CHOST="x86_64-pc-linux-gnu"
MAKEOPTS="-j3"

CONFIG_PROTECT="-*"

INPUT_DEVICES="keyboard mouse"

#USE="-kde -gnome X jpeg tiff png"


I went ahead and disabled the USE flags just to see if would help but didn't.

I used the 32 bit minimum install cd.
Back to top
View user's profile Send private message
Nick C
Guru
Guru


Joined: 18 Mar 2005
Posts: 526
Location: Portsmouth, England

PostPosted: Thu Feb 28, 2008 11:12 pm    Post subject: Reply with quote

thats your problem then, your trying to use a 64 bit stage file with a 32 bit cd, this doesnt work. You need a matching cd and stage3 file. For example to install a 32bit x86 install you would need the x86 i686 livecd and stage3 file. Likewise to do a 64bit install you need both a 64bit livecd and stage 3 file.
_________________
Please add [solved] to the initial post's subject line if you feel your problem is resolved.
www.monkeydust.net
Back to top
View user's profile Send private message
dman777
Veteran
Veteran


Joined: 10 Jan 2007
Posts: 1004

PostPosted: Thu Feb 28, 2008 11:30 pm    Post subject: Reply with quote

I'd rather stay 32 bit, since all the software I want to use is 32 bit. Should I change CHOST="x86_64-pc-linux-gnu" to CHOST="x86_32-pc-linux-gnu" in my make.conf? I put the "....x86_64-...." in the CHOST because I was following the gentoo wiki safe flags for my processor. Also, does this mean I need to start from scratch with install or can I just change it to 32 and do a emerge update?

Thanks,
-Darin
Back to top
View user's profile Send private message
slycordinator
Advocate
Advocate


Joined: 31 Jan 2004
Posts: 3065
Location: Korea

PostPosted: Thu Feb 28, 2008 11:46 pm    Post subject: Reply with quote

dman777 wrote:
I'd rather stay 32 bit, since all the software I want to use is 32 bit. Should I change CHOST="x86_64-pc-linux-gnu" to CHOST="x86_32-pc-linux-gnu" in my make.conf? I put the "....x86_64-...." in the CHOST because I was following the gentoo wiki safe flags for my processor. Also, does this mean I need to start from scratch with install or can I just change it to 32 and do a emerge update?

Thanks,
-Darin


No, considering there's no such thing as that CHOST value.

You could try CHOST="i686-pc-linux-gnu"

And you have to NOT simply follow some wiki. The info in that wiki is used with the basic assumption that you generally know what you're doing. It's not meant to be rude but the idea that a 32-bit host OS can't be used to build a 64-bit host is considered basic.
Back to top
View user's profile Send private message
dman777
Veteran
Veteran


Joined: 10 Jan 2007
Posts: 1004

PostPosted: Thu Feb 28, 2008 11:58 pm    Post subject: Reply with quote

Ya, I understand...I couldn't tell if that "x86_64-pc-linux-gnu" was just the title/syntax for my particular CPU(because it's been referred to as a 64 bit processor) or if it actually enabled 64 bit mode. Would it be best for me to reformat and re-install from scratch or can I do a emerge --update --deep world?
Back to top
View user's profile Send private message
SLBMEH
Apprentice
Apprentice


Joined: 16 Aug 2003
Posts: 299
Location: Pittsburgh, PA

PostPosted: Fri Feb 29, 2008 12:23 am    Post subject: Reply with quote

The least painful approach would be to reinstall with the correct tarball. Changing the CHOST can be done, but it's generally recommended not to do so because it's a rather advanced topic and has no gain over doing a fresh install.
_________________
Steve - Semper Fi
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Installing Gentoo All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum