fivemack: (Default)
Tom Womack ([personal profile] fivemack) wrote2007-06-04 05:32 pm

Two Linux frustrations

We've just got a new machine at work on which I've been asked to install OpenSuSE 10.2 64-bit; this felt entirely straightforward.

Unfortunately, the default install of OpenSuSE doesn't include gcc. When I try installing gcc using YaST2, I get something which looks superficially like gcc, but which says 'gcc: error trying to exec 'cc1': execvp: No such file or directory' whenever I try to compile anything with it.

So, where's cc1 coming from? Deciding now would be a good time to use up some of the EU Assorted Symbol Mountain, I type

for i in /media/SU1020.001/suse/x86_64/*.rpm; do rpm -qpl $i | sed -e "s/^/${i//\//_}/g" | grep cc1; done

which tells me that /usr/lib64/gcc/x86_64-suse-linux/4.1.2/cc1 is provided by cpp41-4.1.2_20061115-5.x86_64.rpm

And indeed /usr/lib64/gcc/x86_64-suse-linux/4.1.2/cc1 exists on the machine. So, why isn't /usr/bin/gcc-4.1 finding it?

Normally strace comes to the rescue, but 'strace /usr/bin/gcc-4.1 -c foo.c' outputs many lines of the form

stat64(0x806b628, 0xff885abc) = -1 ENOENT (No such file or directory)

which are totally useless because strace is failing to dereference the pointer to the filename passed to stat64.

[identity profile] jojomojo.livejournal.com 2007-06-04 06:00 pm (UTC)(link)
Does simply running cc1 directly from the command line do anything useful? I'm wondering if it's, I don't know, making a reference to a version of ld-linux.so that's not installed on the machine, or something.

[identity profile] arnhem.livejournal.com 2007-06-04 09:25 pm (UTC)(link)
Errm, I've got some OpenSuSE 10.2 64-bit machines with a perfectly functional gcc. I think there's something fundamentally funted about your machine.

The trick with suse installs is to click the "software selection" link when you get to the "this is what we're going to install" page; you then get the chance to say "development tools, that sounds cool" ...

[identity profile] davidcook.livejournal.com 2007-06-05 06:56 am (UTC)(link)
Could there be a permissions issue somewhere ? Check that cc1 and the directory path leading to it have appropriate perms, ownership, etc.
Maybe you could try uninstalling the gcc package and reinstalling ? Double-check that there are no error messages on installation ?