Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
Big mpfr/gcc/gmp-5.0.2_p1 MESS Breaks gcc [SOLVED]
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Portage & Programming
View previous topic :: View next topic  
Author Message
wrc1944
Advocate
Advocate


Joined: 15 Aug 2002
Posts: 3435
Location: Gainesville, Florida

PostPosted: Sat Aug 27, 2011 10:59 pm    Post subject: Big mpfr/gcc/gmp-5.0.2_p1 MESS Breaks gcc [SOLVED] Reply with quote

I just ran into this on my main gentoo ~x86 box.

EDIT: Been going around looking at 5-6 posts related to mpfr and gcc problems, including the sticky, but still can't get things to work.

Apparently, the tinderbox doesn't have the required package of mpfr (2.4.2)? Not sure on this- should 3.0.0_p3 work? I already have version3.0.1_p4 installed. Tinderbox only has gcc-4.4.5- I'm using 4.5.3. Should I use 4.4.5, then emerge -K mpfr, and then try emerging @world or gcc-4.5.3 first?

We really need a simple and current step-by-step on this problem- it's pretty serious.

OK- tried gcc-4.4.5 and 3.0.0_p3 from tinderbox (-k, switched to 4.4.5, and -k'd mpfr-3.0.0_p3). Still, even using gcc-4.4.5 it gives the same type errors trying to compile anything
:roll:
[/color] :roll:

On an emerge -uD @world --keep-going, I had 26 total packages, where gmp was number 4, and all the rest then failed.

I think it's related to updating dev-libs/gmp-5.0.2_p1 from plain 5.0.2, which BTW went OK, but apparently I can't revert as gcc seems broken. My system was working fine a few days ago.

I did a revdep-rebuild, and got mpc, and tried to emerge it, and got same error.

Code:
Starting rebuild
emerge --complete-graph=y --oneshot   dev-libs/mpc:0
..........

 * IMPORTANT: 4 news items need reading for repository 'gentoo'.
 * Use eselect news to read news items.

Calculating dependencies... done!

>>> Verifying ebuild manifests

>>> Emerging (1 of 1) dev-libs/mpc-0.9
 * mpc-0.9.tar.gz RMD160 SHA1 SHA256 size ;-) ...                                                                    [ ok ]
 * mpc-0.9-configure.patch.bz2 RMD160 SHA1 SHA256 size ;-) ...                                                       [ ok ]
>>> Unpacking source...
>>> Unpacking mpc-0.9.tar.gz to /var/tmp/portage/dev-libs/mpc-0.9/work
>>> Unpacking mpc-0.9-configure.patch.bz2 to /var/tmp/portage/dev-libs/mpc-0.9/work
 * Applying mpc-0.9-configure.patch ...                                                                              [ ok ]
 * Running elibtoolize in: mpc-0.9/
 *   Applying portage-2.2.patch ...
 *   Applying sed-1.5.6.patch ...
 *   Applying as-needed-2.2.6.patch ...
>>> Source unpacked in /var/tmp/portage/dev-libs/mpc-0.9/work
>>> Compiling source in /var/tmp/portage/dev-libs/mpc-0.9/work/mpc-0.9 ...
 * econf: updating mpc-0.9/config.sub with /usr/share/gnuconfig/config.sub
 * econf: updating mpc-0.9/config.guess with /usr/share/gnuconfig/config.guess
./configure --prefix=/usr --build=i686-pc-linux-gnu --host=i686-pc-linux-gnu --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc --localstatedir=/var/lib
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 build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking for i686-pc-linux-gnu-gcc... i686-pc-linux-gnu-gcc
checking whether the C compiler works... no
configure: error: in `/var/tmp/portage/dev-libs/mpc-0.9/work/mpc-0.9':
configure: error: C compiler cannot create executables
See `config.log' for more details

!!! Please attach the following file when seeking support:
!!! /var/tmp/portage/dev-libs/mpc-0.9/work/mpc-0.9/config.log
 * ERROR: dev-libs/mpc-0.9 failed (compile phase):
 *   econf failed


Here's the config.log file:
Code:
This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.

It was created by mpc configure 0.9, which was
generated by GNU Autoconf 2.67.  Invocation command line was

  $ ./configure --prefix=/usr --build=i686-pc-linux-gnu --host=i686-pc-linux-gnu --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc --localstatedir=/var/lib

## --------- ##
## Platform. ##
## --------- ##

hostname = localhost
uname -m = i686
uname -r = 3.0.1-ck1
uname -s = Linux
uname -v = #1 SMP PREEMPT Thu Aug 11 21:13:22 EDT 2011

/usr/bin/uname -p = AMD Athlon(tm) II X4 640 Processor
/bin/uname -X     = unknown

/bin/arch              = unknown
/usr/bin/arch -k       = unknown
/usr/convex/getsysinfo = unknown
/usr/bin/hostinfo      = unknown
/bin/machine           = unknown
/usr/bin/oslevel       = unknown
/bin/universe          = unknown

PATH: /usr/lib/portage/bin/ebuild-helpers
PATH: /usr/local/sbin
PATH: /usr/local/bin
PATH: /usr/sbin
PATH: /usr/bin
PATH: /sbin
PATH: /bin
PATH: /opt/bin
PATH: /usr/i686-pc-linux-gnu/gcc-bin/4.5.3


## ----------- ##
## Core tests. ##
## ----------- ##

configure:2429: checking for a BSD-compatible install
configure:2497: result: /usr/bin/install -c
configure:2508: checking whether build environment is sane
configure:2558: result: yes
configure:2699: checking for a thread-safe mkdir -p
configure:2738: result: /bin/mkdir -p
configure:2751: checking for gawk
configure:2767: found /usr/bin/gawk
configure:2778: result: gawk
configure:2789: checking whether make sets $(MAKE)
configure:2811: result: yes
configure:2892: checking whether to enable maintainer-specific portions of Makefiles
configure:2901: result: no
configure:2919: checking build system type
configure:2933: result: i686-pc-linux-gnu
configure:2953: checking host system type
configure:2966: result: i686-pc-linux-gnu
configure:3067: checking for i686-pc-linux-gnu-gcc
configure:3083: found /usr/bin/i686-pc-linux-gnu-gcc
configure:3094: result: i686-pc-linux-gnu-gcc
configure:3363: checking for C compiler version
configure:3372: i686-pc-linux-gnu-gcc --version >&5
i686-pc-linux-gnu-gcc (Gentoo 4.5.3-r1 p1.0, pie-0.4.5) 4.5.3
Copyright (C) 2010 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

configure:3383: $? = 0
configure:3372: i686-pc-linux-gnu-gcc -v >&5
Using built-in specs.
COLLECT_GCC=/usr/i686-pc-linux-gnu/gcc-bin/4.5.3/i686-pc-linux-gnu-gcc
COLLECT_LTO_WRAPPER=/usr/libexec/gcc/i686-pc-linux-gnu/4.5.3/lto-wrapper
Target: i686-pc-linux-gnu
Configured with: /var/tmp/portage/sys-devel/gcc-4.5.3-r1/work/gcc-4.5.3/configure --prefix=/usr --bindir=/usr/i686-pc-linux-gnu/gcc-bin/4.5.3 --includedir=/usr/lib/gcc/i686-pc-linux-gnu/4.5.3/include --datadir=/usr/share/gcc-data/i686-pc-linux-gnu/4.5.3 --mandir=/usr/share/gcc-data/i686-pc-linux-gnu/4.5.3/man --infodir=/usr/share/gcc-data/i686-pc-linux-gnu/4.5.3/info --with-gxx-include-dir=/usr/lib/gcc/i686-pc-linux-gnu/4.5.3/include/g++-v4 --host=i686-pc-linux-gnu --build=i686-pc-linux-gnu --disable-altivec --disable-fixed-point --without-ppl --without-cloog --disable-lto --enable-nls --without-included-gettext --with-system-zlib --disable-werror --enable-secureplt --disable-multilib --enable-libmudflap --disable-libssp --enable-libgomp --enable-cld --with-python-dir=/share/gcc-data/i686-pc-linux-gnu/4.5.3/python --enable-checking=release --disable-libgcj --with-arch=i686 --enable-languages=c,c++,fortran --enable-shared --enable-threads=posix --enable-__cxa_atexit --enable-clocale=gnu --with-bugurl=http://bugs.gentoo.org/ --with-pkgversion='Gentoo 4.5.3-r1 p1.0, pie-0.4.5'
Thread model: posix
gcc version 4.5.3 (Gentoo 4.5.3-r1 p1.0, pie-0.4.5)
configure:3383: $? = 0
configure:3372: i686-pc-linux-gnu-gcc -V >&5
i686-pc-linux-gnu-gcc: '-V' option must have argument
configure:3383: $? = 1
configure:3372: i686-pc-linux-gnu-gcc -qversion >&5
i686-pc-linux-gnu-gcc: unrecognized option '-qversion'
i686-pc-linux-gnu-gcc: no input files
configure:3383: $? = 1
configure:3403: checking whether the C compiler works
configure:3425: i686-pc-linux-gnu-gcc -O2 -march=native -pipe -fomit-frame-pointer  -Wl,-O1 -Wl,--as-needed conftest.c  >&5
/usr/libexec/gcc/i686-pc-linux-gnu/4.5.3/cc1: error while loading shared libraries: libgmp.so.3: cannot open shared object file: No such file or directory
configure:3429: $? = 1
configure:3467: result: no
configure: failed program was:
| /* confdefs.h */
| #define PACKAGE_NAME "mpc"
| #define PACKAGE_TARNAME "mpc"
| #define PACKAGE_VERSION "0.9"
| #define PACKAGE_STRING "mpc 0.9"
| #define PACKAGE_BUGREPORT "mpc-discuss@lists.gforge.inria.fr"
| #define PACKAGE_URL ""
| #define PACKAGE "mpc"
| #define VERSION "0.9"
| /* end confdefs.h.  */
|
| int
| main ()
| {
|
|   ;
|   return 0;
| }
configure:3472: error: in `/var/tmp/portage/dev-libs/mpc-0.9/work/mpc-0.9':
configure:3474: error: C compiler cannot create executables
See `config.log' for more details

## ---------------- ##
## Cache variables. ##
## ---------------- ##

ac_cv_build=i686-pc-linux-gnu
ac_cv_env_CC_set=
ac_cv_env_CC_value=
ac_cv_env_CFLAGS_set=set
ac_cv_env_CFLAGS_value='-O2 -march=native -pipe -fomit-frame-pointer'
ac_cv_env_CPPFLAGS_set=
ac_cv_env_CPPFLAGS_value=
ac_cv_env_CPP_set=
ac_cv_env_CPP_value=
ac_cv_env_LDFLAGS_set=set
ac_cv_env_LDFLAGS_value='-Wl,-O1 -Wl,--as-needed'
ac_cv_env_LIBS_set=
ac_cv_env_LIBS_value=
ac_cv_env_build_alias_set=set
ac_cv_env_build_alias_value=i686-pc-linux-gnu
ac_cv_env_host_alias_set=set
ac_cv_env_host_alias_value=i686-pc-linux-gnu
ac_cv_env_target_alias_set=
ac_cv_env_target_alias_value=
ac_cv_host=i686-pc-linux-gnu
ac_cv_path_install='/usr/bin/install -c'
ac_cv_path_mkdir=/bin/mkdir
ac_cv_prog_AWK=gawk
ac_cv_prog_CC=i686-pc-linux-gnu-gcc
ac_cv_prog_make_make_set=yes

## ----------------- ##
## Output variables. ##
## ----------------- ##

ACLOCAL='${SHELL} /var/tmp/portage/dev-libs/mpc-0.9/work/mpc-0.9/missing --run aclocal-1.11'
AMDEPBACKSLASH=''
AMDEP_FALSE=''
AMDEP_TRUE=''
AMTAR='${SHELL} /var/tmp/portage/dev-libs/mpc-0.9/work/mpc-0.9/missing --run tar'
AR=''
AUTOCONF='${SHELL} /var/tmp/portage/dev-libs/mpc-0.9/work/mpc-0.9/missing --run autoconf'
AUTOHEADER='${SHELL} /var/tmp/portage/dev-libs/mpc-0.9/work/mpc-0.9/missing --run autoheader'
AUTOMAKE='${SHELL} /var/tmp/portage/dev-libs/mpc-0.9/work/mpc-0.9/missing --run automake-1.11'
AWK='gawk'
CC='i686-pc-linux-gnu-gcc'
CCDEPMODE=''
CFLAGS='-O2 -march=native -pipe -fomit-frame-pointer'
CPP=''
CPPFLAGS=''
CYGPATH_W='echo'
DEFS=''
DEPDIR=''
DSYMUTIL=''
DUMPBIN=''
ECHO_C=''
ECHO_N='-n'
ECHO_T=''
EGREP=''
EXEEXT=''
FGREP=''
GREP=''
INSTALL_DATA='${INSTALL} -m 644'
INSTALL_PROGRAM='${INSTALL}'
INSTALL_SCRIPT='${INSTALL}'
INSTALL_STRIP_PROGRAM='$(install_sh) -c -s'
LD=''
LDFLAGS='-Wl,-O1 -Wl,--as-needed'
LIBOBJS=''
LIBS=''
LIBTOOL=''
LIPO=''
LN_S=''
LTLIBOBJS=''
MAINT='#'
MAINTAINER_MODE_FALSE=''
MAINTAINER_MODE_TRUE='#'
MAKEINFO='${SHELL} /var/tmp/portage/dev-libs/mpc-0.9/work/mpc-0.9/missing --run makeinfo'
MKDIR_P='/bin/mkdir -p'
MPC_LOG_H=''
NM=''
NMEDIT=''
OBJDUMP=''
OBJEXT=''
OTOOL64=''
OTOOL=''
PACKAGE='mpc'
PACKAGE_BUGREPORT='mpc-discuss@lists.gforge.inria.fr'
PACKAGE_NAME='mpc'
PACKAGE_STRING='mpc 0.9'
PACKAGE_TARNAME='mpc'
PACKAGE_URL=''
PACKAGE_VERSION='0.9'
PATH_SEPARATOR=':'
RANLIB=''
SED=''
SET_MAKE=''
SHELL='/bin/sh'
STRIP=''
VERSION='0.9'
WARNINGCFLAGS=''
ac_ct_CC=''
ac_ct_DUMPBIN=''
am__EXEEXT_FALSE=''
am__EXEEXT_TRUE=''
am__fastdepCC_FALSE=''
am__fastdepCC_TRUE=''
am__include=''
am__isrc=''
am__leading_dot='.'
am__quote=''
am__tar='${AMTAR} chof - "$$tardir"'
am__untar='${AMTAR} xf -'
bindir='${exec_prefix}/bin'
build='i686-pc-linux-gnu'
build_alias='i686-pc-linux-gnu'
build_cpu='i686'
build_os='linux-gnu'
build_vendor='pc'
datadir='/usr/share'
datarootdir='${prefix}/share'
docdir='${datarootdir}/doc/${PACKAGE_TARNAME}'
dvidir='${docdir}'
exec_prefix='NONE'
host='i686-pc-linux-gnu'
host_alias='i686-pc-linux-gnu'
host_cpu='i686'
host_os='linux-gnu'
host_vendor='pc'
htmldir='${docdir}'
includedir='${prefix}/include'
infodir='/usr/share/info'
install_sh='${SHELL} /var/tmp/portage/dev-libs/mpc-0.9/work/mpc-0.9/install-sh'
libdir='${exec_prefix}/lib'
libexecdir='${exec_prefix}/libexec'
localedir='${datarootdir}/locale'
localstatedir='/var/lib'
lt_ECHO='echo'
mandir='/usr/share/man'
mkdir_p='/bin/mkdir -p'
oldincludedir='/usr/include'
pdfdir='${docdir}'
prefix='/usr'
program_transform_name='s,x,x,'
psdir='${docdir}'
sbindir='${exec_prefix}/sbin'
sharedstatedir='${prefix}/com'
sysconfdir='/etc'
target_alias=''

## ----------- ##
## confdefs.h. ##
## ----------- ##

/* confdefs.h */
#define PACKAGE_NAME "mpc"
#define PACKAGE_TARNAME "mpc"
#define PACKAGE_VERSION "0.9"
#define PACKAGE_STRING "mpc 0.9"
#define PACKAGE_BUGREPORT "mpc-discuss@lists.gforge.inria.fr"
#define PACKAGE_URL ""
#define PACKAGE "mpc"
#define VERSION "0.9"

configure: exit 77

I've looked around google, forums, and bugzilla, can't seem to get a clue on this one. :?
_________________
Main box- AsRock x370 Gaming K4
Ryzen 7 3700x, 3.6GHz, 16GB GSkill Flare DDR4 3200mhz
Samsung SATA 1000GB, Radeon HD R7 350 2GB DDR5
OpenRC Gentoo ~amd64 plasma, glibc-2.36-r7, gcc-13.2.1_p20230304
kernel-6.8.4 USE=experimental python3_11


Last edited by wrc1944 on Sun Aug 28, 2011 9:40 pm; edited 1 time in total
Back to top
View user's profile Send private message
wrc1944
Advocate
Advocate


Joined: 15 Aug 2002
Posts: 3435
Location: Gainesville, Florida

PostPosted: Sun Aug 28, 2011 9:40 pm    Post subject: Reply with quote

Solved with
Code:
localhost wrc # cd /usr/lib
localhost lib # ln -s libgmpxx.so.4.2.2 libgmp.so.3

See: https://forums.gentoo.org/viewtopic-p-6798734.html#6798734
_________________
Main box- AsRock x370 Gaming K4
Ryzen 7 3700x, 3.6GHz, 16GB GSkill Flare DDR4 3200mhz
Samsung SATA 1000GB, Radeon HD R7 350 2GB DDR5
OpenRC Gentoo ~amd64 plasma, glibc-2.36-r7, gcc-13.2.1_p20230304
kernel-6.8.4 USE=experimental python3_11
Back to top
View user's profile Send private message
Atha
Apprentice
Apprentice


Joined: 22 Sep 2004
Posts: 229

PostPosted: Wed Oct 26, 2011 11:05 pm    Post subject: Reply with quote

I just ran into the same problem. After emerging gmp-5.0.2 I had that elog telling me to run revdep-rebuild --library '/usr/lib64/libgmp.so.3', which I did. I then deleted this library with rm '/usr/lib64/libgmp.so.3', like mentioned in the elog also, and the elog itself, since I was done with it. I use the elogs to do all that manual stuff when I have the time, not when the emerge finishes. I know this could be dangerous, but so far I was always right about which packages need my attention right away and which don't.

Code:
# equery b /usr/lib64/libgmpxx.so.4.2.2
 * Searching for /usr/lib64/libgmpxx.so.4.2.2 ...
dev-libs/gmp-5.0.2 (/usr/lib64/libgmpxx.so.4.2.2)


This is odd. Why do you link libgmp.so.3 to libgmpxx.so.4.2.2 from gmp-5.0.2?

What I did to resolve this issue: I linked libgmp.so.3 to libgmp.so.10. gcc thereafter worked again.
Then I ran ACCEPT_KEYWORDS="~amd64" emerge -O1Bv dev-libs/gmp:3.
Code:
These are the packages that would be built, in order:

[ebuild  NS    ] dev-libs/gmp-4.3.2-r1 [5.0.2] 1,854 kB

Total: 1 package (1 in new slot), Size of downloads: 1,854 kB

>>> Verifying ebuild manifests
>>> Emerging (1 of 1) dev-libs/gmp-4.3.2-r1
>>> Jobs: 1 of 1 complete                           Load avg: 1.68, 0.54, 0.27

Now I could extract the files libgmp.so.3.5.2 and its symlink libgmp.so.3 from the binpkg (found in $PKGDIR from /etc/make.conf) and copy it to /usr/lib64.

I still have no clue why gcc stopped working, since revdep-rebuild didn't show anything.
Back to top
View user's profile Send private message
wrc1944
Advocate
Advocate


Joined: 15 Aug 2002
Posts: 3435
Location: Gainesville, Florida

PostPosted: Thu Oct 27, 2011 2:43 pm    Post subject: Reply with quote

Atha wrote:
Quote:
This is odd. Why do you link libgmp.so.3 to libgmpxx.so.4.2.2 from gmp-5.0.2?


IIRC, It was because I read of that linking fix but it referred to lib64, so I just looked in /usr/lib (32 bit) and adapted to what was there.

Since it worked, I didn't give it any more thought as to if that was really correct, or not. Maybe I should look at this again and see if that added link is not really needed.
_________________
Main box- AsRock x370 Gaming K4
Ryzen 7 3700x, 3.6GHz, 16GB GSkill Flare DDR4 3200mhz
Samsung SATA 1000GB, Radeon HD R7 350 2GB DDR5
OpenRC Gentoo ~amd64 plasma, glibc-2.36-r7, gcc-13.2.1_p20230304
kernel-6.8.4 USE=experimental python3_11
Back to top
View user's profile Send private message
Atha
Apprentice
Apprentice


Joined: 22 Sep 2004
Posts: 229

PostPosted: Thu Oct 27, 2011 4:55 pm    Post subject: How to get that original libgmp.so.3 back… Reply with quote

wrc1944 wrote:
Since it worked, I didn't give it any more thought as to if that was really correct, or not.


If gcc or any other vital program stops working after removing the symlink, I suggest to re-emerge dev-libs/gmp-4.3.2 (has no slot) or better dev-libs/gmp-4.3.2-r1 (slot:3). For this and to be able to compile anything, I'd link libgmp.so.3 to libgmp.so.10, or any other library that worked for you (libgmpxx.so.4.4.2 ???). Just make sure to use the real libgmp.so.3 as soon as possible.

  # cd /usr/lib
  # ln -s libgmp.so.10 libgmp.so.3

Emerge the original libgmp.so.3, or rather not emerge (thus: emerge -1), but only build that package (thus: emerge -B), since both versions cannot coexist (thus: emerge -O).

  # emerge -O1B =dev-libs/gmp-4.3.2
or
  # ACCEPT_KEYWORDS="~arch" emerge -O1B dev-libs/gmp:3
  (use your ~arch as required, e.g. ~x86 or ~amd64)

Then extract the original libgmp.so.3 from the package tarball, found in $PKGDIR as defined in /etc/make.conf, and copy it to /usr/lib (removing the symlink to libgmp.so.10, which is no good).

This should make your system safe. It is a workaround until at least gcc works without this older library, and hopefully uses the new one.

Cheers,
A.
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Portage & Programming 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