HELP! broke rpm and gcc

theetderks · 10-22-2004, 05:48 PM

HELP!

I have a Cobalt Raq4 web server that I was wanting to install Zope 2.7 onto... This meant upgrading Python 1.5.2 to 2.3.3.

Which meant a whole lot of software was outdated:

glibc
ncurese
gmp

...etc... including gcc and rpm.

To make a long (and sad) story .... a little shorter:

both gcc and rpm seem to be broken.

I tried rebuilding rpm-4.0.4 from a tarball and got this:

Code:

# ./configure
loading cache ./config.cache
checking host system type... i586-pc-linux-gnuoldld
checking target system type... i586-pc-linux-gnuoldld
checking build system type... i586-pc-linux-gnuoldld
checking for a BSD compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking whether make sets ${MAKE}... yes
checking for working aclocal... found
checking for working autoconf... found
checking for working automake... found
checking for working autoheader... found
checking for working makeinfo... found
checking for gcc... gcc
checking whether the C compiler (gcc  ) works... no
configure: error: installation or configuration problem: C compiler cannot create executables.

I need to find a way to get an excutable installed that will allow me to rebuild gcc... or something??!

The Cobalt runs a custom dist of linux that is based on RH (I thinK)...

# cat /etc/vendor-release
Cobalt Linux release 6.0 (Shinkansen)

Kernel: Kernel 2.2.16C32_III on an i586

# gcc -v
Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/2.96/specs
gcc version 2.96 20000731 (Red Hat Linux 7.3 2.96-113)

Any brilliant suggestions would be much appreciated!

teval · 10-22-2004, 05:59 PM

Try to run a simple main.c file against gcc.
In case you don't know C this should be fine:

int main()
{ return 0; }

See what errors that give. It's possible the configure failed to create an executable for a different reason than gcc being broken.
Also in what way is rpm broken?
And what did you install that led up to this?

theetderks · 10-22-2004, 06:38 PM

Thanks for the reply teval.

I tried the main.c ...

# gcc main.c
main.c:1: parse error before `main'

... I may be doing something wrong (I'm not too experienced writing & compiling C)

The sequence went like this...

I needed to upgrade both rpm (rpm-4.0.4 rpm-build-4.0.4 rpm-devel-4.0.4) and
glibc (glibc-2.3.2 glibc-common-2.3.2 glibc-devel-2.3.2)
But they both had dependencies on each other... so I figured I'd have to force an update on each... unfortuneately I started with rpm (without enough thought)

So I have an updated rpm that is looking for the libc.so.6 library from glibc... which hasn't
yet been installed... and now can't be installed...

As far as gcc is concerned, I think the problem may be that I upgraded the compiler without
upgrading libgcc...?

shazam75 · 10-22-2004, 10:38 PM

I had the same error when i tried to update my gcc library to install Opera and it had to do with installing libc.so.6 - and I had to do a new install of linux - it sux!
configure: error: installation or configuration problem: C compiler cannot create executables.

Regards

foo_bar_foo · 10-22-2004, 11:06 PM

do you have access to another small partition you can put a minimalistic version of the same Linux system on.
very dificult to upgrade such an old system to new gcc3 and glibc
all your apps were going to be broken after not just rpm.
possibly on another patrition or from another machine you can unpack the old versions of the stuff you messed up and replace the new with the old and get you back to where you were..

from now on if you want to upgrade the core that far you need something like apt to do it..

teval · 10-29-2004, 08:41 PM

What you can do, is get the binary for something to unpack rpms

There are lots of programs that will do that. Unpack your libc rpm and copy the libc file, if not, if you look at the redhat site, or on rpmfind it used to be that you could get a specific file from inside an rpm. That should do the trick.

Next time, update glibc first, followed by gcc, and then rpm

The new glibc should not break things, if you suspect it might, you can always first unpack glibc gcc and rpm noting where things will go (rpm does this, man rpm) and then copy things to their proper spot.