Problems with GCC

unihiekka · 07-05-2006, 04:05 PM

I have just tried

Code:

apt-get install gcc

in the konsole of my SuSE 10.1 system and got:

gcc is already the newest version.
0 upgraded, 0 newly installed, 0 removed and 0 not upgraded.

Then, I want to run

Code:

./configure

for a certain piece of software (Freeciv) and then I get:

checking for C99 variadic macros... no
configure: error: A compiler supporting C99 variadic macros is required

Moreover, if I write

Code:

gcc -v

in bash I see the following:

Reading specs from /usr/local/lib/gcc-lib/i686-pc-linux-gnu/egcs-2.91.66/specs
gcc version egcs-2.91.66 19990314 (egcs-1.1.2 release)

Which does not seem to be the newest version. What's wrong here? I can "update" to the newest over YaST, but the same sh*t...

unihiekka · 07-05-2006, 04:29 PM

The output of

Code:

cc -v

is (should that be of any help):

Quote:

Using built-in specs.
Target: i586-suse-linux
Configured with: ../configure --enable-threads=posix --prefix=/usr --with-local-prefix=/usr/local --infodir=/usr/share/info --mandir=/usr/share/man --libdir=/usr/lib --libexecdir=/usr/lib --enable-languages=c,c++,objc,fortran,java,ada --enable-checking=release --with-gxx-include-dir=/usr/include/c++/4.1.0 --enable-ssp --disable-libssp --enable-java-awt=gtk --enable-gtk-cairo --disable-libjava-multilib --with-slibdir=/lib --with-system-zlib --enable-shared --enable-__cxa_atexit --enable-libstdcxx-allocator=new --without-system-libunwind --with-cpu=generic --host=i586-suse-linux
Thread model: posix
gcc version 4.1.0 (SUSE Linux)

Note the different architectures 586 here (and correct gcc version) and above 686 (and the wrong one), which is obviously used by ./configure... Does the problem lie here?

unihiekka · 07-05-2006, 04:40 PM

And (just for the record):

Code:

uname -p

returns:

Quote:

i686

. I thought i586 packages work fine on i686...

AwesomeMachine · 07-05-2006, 05:21 PM

A lot of SuSE stuff, especially 10.x is custom for SuSE. If you want a distro that isn't fussy about source packages, use debian. SuSE is pretty fussy about source packages. I have failed more times than I have succeeded to compile sources in SuSE 10.x. The other option is to go to http://rpmfind.net and see if there is a SuSE 10.x rpm for the program you want to install and dowload it. I found the best way to install rpm's in SuSE 10.x is not with yast2, but with rpm.

rpm -iv package.rpm

I think I might move away from SuSE as it is getting pretty far away from standard linux. Nothing works with it except SuSE 10.x rpm's, and it's got all kinds of windosey garbage I dislike. All that new crap doesn't make it better, it makes it worse. Yast2 can still be launched from from a shell. If you know the name of a prog you can do

yast2 --install packagename

unihiekka · 07-12-2006, 09:59 AM

A fresh installation helped, so it's just because I upgraded from 9.3 to 10.1, which isn't the best of ideas.
Not only RPMs work fine under SuSE... source packages are as easy to install as RPMs... It was my fault to upgrade "too much"...