-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tuesday 12 August 2003 05:20 pm, Philipp Thomas wrote:
The Wizard
[Tue, 12 Aug 2003 08:16:44 -0700]: I saw the Apache/libphp4.so error after I upgraded to the newer GCC 3.3 from ftp://ftp.suse.com/pub/projects (the 8.2 GCC gave "prerelease" in the version message) and fixed it by re-installing libgcc-3.3-43.i586.rpm and running "ldconfig" .
Yes, gcc needs more than one package to be usable. These packages form the base on which all other packages build:
libgcc (shared runtime support library) cpp (preprocessor, actually the C frontend as there is no separate preprocessor anymore). gcc (compiler driver, gcc specific headers etc.)
This base is all you need if you only want to compile C Programs.
All following package sets need the C compiler, i.e. must be installed in addition to the above base packages.
C++:
gcc-c++ (compiler driver plus C++ frontend) libstdc++ (standard C++ library, shared libraries only) libstdc++-devel (static libraries and header files)
Fortran77:
gcc-g77
Java:
gcc-java (java compiler) libgcj (java libraries, shared version only) libgcj-devel (headers, static libraries, symlinks for linking)
Ada:
gnat (nearly complete Ada development package) gnat-runtime (ADA shared runtime libraries)
Objective C:
gcc-objc (objective C frontend) libobjc (libraries, headers etc.)
And independently from the rest the documentation in texinfo format:
gcc-info
Maybe I should expand the README to make it clear which packages are needed?
Philipp
I had installed all the packages via the project/gcc directory weeks ago and followed the instruction posted on both the website and the README. rpm -qa | grep cpp cpp-3.3-43 rpm -qa | grep gcc gcc-c++-3.3-43 libgcc-3.3-43 gcc-g77-3.3-43 gcc-info-3.3-43 gcc-java-3.3-43 gcc-objc-3.3-43 gcc-3.3-43 rpm -qa | grep libgcc libgcc-3.3-43 rpm -qa | grep libgcj libgcj-3.3-43 libgcj-devel-3.3-43 rpm -qa | grep libgcj-devel libgcj-devel-3.3-43 rpm -qa | grep gcc-g77 gcc-g77-3.3-43 rpm -qa | grep libstdc libstdc++-3.3-43 libstdc++-devel-3.3-43 rpm -qa | grep gcc-java gcc-java-3.3-43 rpm -qa | grep gcc-objc gcc-objc-3.3-43 rpm -qa | grep libobjc libobjc-3.3-43 rpm -qa | grep gccinfo nada zip zilch. After updating the new kernel via rpm as suggested in the announcement and via yast the NVIDIA drivers (kernel/GLX) won't install via the installer, sources rpms under rebuild give the following: *** Failed cc sanity check. Bailing out! *** make: *** [gcc-check] Error 1 + exit 0 Executing(%install): /bin/sh -e /var/tmp/rpm-tmp.51101 + umask 022 + cd /usr/src/packages/BUILD + cd NVIDIA_kernel-1.0-4496 + rm -f /tmp/files.lst + '[' -z '' ']' ++ uname -r + export TARGET_KERNEL=2.4.20-4GB-athlon + TARGET_KERNEL=2.4.20-4GB-athlon + '[' -d /lib/modules/2.4.20-4GB-athlon/kernel ']' + INSTALLPATH=/lib/modules/2.4.20-4GB-athlon/kernel/drivers/video + mkdir -p /var/tmp/NVIDIA_kernel-1.0//lib/modules/2.4.20-4GB-athlon/kernel/drivers/video + install -m 0444 nvidia.o /var/tmp/NVIDIA_kernel-1.0//lib/modules/2.4.20-4GB-athlon/kernel/drivers/video install: cannot stat `nvidia.o': No such file or directory Bad exit status from /var/tmp/rpm-tmp.51101 (%install) But the GLX drivers will rebuild, but an rpm -ba for the GLX returns the essentially the same as above: *** Failed cc sanity check. Bailing out! *** make: *** [gcc-check] Error 1 + exit 0 Executing(%install): /bin/sh -e /var/tmp/rpm-tmp.57628 + umask 022 + cd /usr/src/packages/BUILD + cd NVIDIA_kernel-1.0-4496 + rm -f /tmp/files.lst + '[' -z '' ']' ++ uname -r + export TARGET_KERNEL=2.4.20-4GB-athlon + TARGET_KERNEL=2.4.20-4GB-athlon + '[' -d /lib/modules/2.4.20-4GB-athlon/kernel ']' + INSTALLPATH=/lib/modules/2.4.20-4GB-athlon/kernel/drivers/video + mkdir -p /var/tmp/NVIDIA_kernel-1.0//lib/modules/2.4.20-4GB-athlon/kernel/drivers/video + install -m 0444 nvidia.o /var/tmp/NVIDIA_kernel-1.0//lib/modules/2.4.20-4GB-athlon/kernel/drivers/video install: cannot stat `nvidia.o': No such file or directory Bad exit status from /var/tmp/rpm-tmp.57628 (%install) This also happens with most others sources/src.rpm's. The strange thing is that this is a recent occurance. It didn't give me problems until early this week <shrugs> Cheers, Curtis. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2-rc1-SuSE (GNU/Linux) iD8DBQE/OZLUiqnGhdjCOJsRAvXbAJ4hN3nzP5wp2UZmE1vhkKVRpfXmPACeP2FY 43e+5LnLtAU3yVAdWRaMknM= =pGDo -----END PGP SIGNATURE-----