aMule Forum

English => Compilation problems => Topic started by: tuxteno2006 on May 25, 2006, 05:50:10 AM

Title: compilation in red hat 9
Post by: tuxteno2006 on May 25, 2006, 05:50:10 AM: I can't compile aMule 2.1.1 in red hat 9. I've updated some packages required for wxWidgets and seems to be installed fine.

config output:
Code: [Select]
checking build system type... i686-pc-linux-gnu checking host system type... i686-pc-linux-gnu checking target system type... i686-pc-linux-gnu checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for gawk... gawk checking whether make sets $(MAKE)... yes checking whether to enable maintainer-specific portions of Makefiles... no checking for g++... g++ checking for C++ compiler default output file name... a.out checking whether the C++ compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C++ compiler... yes checking whether g++ accepts -g... yes checking for style of include used by make... GNU checking dependency style of g++... gcc3 checking how to run the C++ preprocessor... g++ -E checking for gcc... gcc checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ANSI C... none needed checking dependency style of gcc... gcc3 checking how to run the C preprocessor... gcc -E checking whether make sets $(MAKE)... (cached) yes checking for a BSD-compatible install... /usr/bin/install -c checking for ranlib... ranlib checking for bison... bison -y checking for ranlib... (cached) ranlib checking for strip... strip checking for ar... ar checking for ld... ld checking for egrep... grep -E checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking for zlib >= 1.1.4... yes (version 1.1.4) checking whether we need the GUI... yes checking for wx-config... /usr/bin/wx-config checking for wxWidgets version >= 2.6.0... yes (version 2.6.3) checking for wxWidgets static library... no checking that wxWidgets has support for large files... yes checking whether to use embedded Crypto... yes checking for bfd headers... yes checking for autopoint... yes (0.11.4) checking for extended flex capabilities... no configure: Your flex version doesn't support --header-file flag. This is not critical, but an upgrade is recomended checking for X... libraries /usr/X11R6/lib, headers /usr/X11R6/include checking for working alloca.h... yes checking for alloca... yes checking for dirent.h that defines DIR... yes checking for library containing opendir... none required checking for ANSI C header files... (cached) yes checking argz.h usability... yes checking argz.h presence... yes checking for argz.h... yes checking arpa/inet.h usability... yes checking arpa/inet.h presence... yes checking for arpa/inet.h... yes checking fcntl.h usability... yes checking fcntl.h presence... yes checking for fcntl.h... yes checking for inttypes.h... (cached) yes checking langinfo.h usability... yes checking langinfo.h presence... yes checking for langinfo.h... yes checking libintl.h usability... yes checking libintl.h presence... yes checking for libintl.h... yes checking limits.h usability... yes checking limits.h presence... yes checking for limits.h... yes checking locale.h usability... yes checking locale.h presence... yes checking for locale.h... yes checking malloc.h usability... yes checking malloc.h presence... yes checking for malloc.h... yes checking mntent.h usability... yes checking mntent.h presence... yes checking for mntent.h... yes checking netdb.h usability... yes checking netdb.h presence... yes checking for netdb.h... yes checking netinet/in.h usability... yes checking netinet/in.h presence... yes checking for netinet/in.h... yes checking stddef.h usability... yes checking stddef.h presence... yes checking for stddef.h... yes checking for stdint.h... (cached) yes checking stdio_ext.h usability... yes checking stdio_ext.h presence... yes checking for stdio_ext.h... yes checking for stdlib.h... (cached) yes checking for string.h... (cached) yes checking for strings.h... (cached) yes checking sys/ioctl.h usability... yes checking sys/ioctl.h presence... yes checking for sys/ioctl.h... yes checking sys/mount.h usability... yes checking sys/mount.h presence... yes checking for sys/mount.h... yes checking sys/param.h usability... yes checking sys/param.h presence... yes checking for sys/param.h... yes checking sys/socket.h usability... yes checking sys/socket.h presence... yes checking for sys/socket.h... yes checking sys/statvfs.h usability... yes checking sys/statvfs.h presence... yes checking for sys/statvfs.h... yes checking sys/time.h usability... yes checking sys/time.h presence... yes checking for sys/time.h... yes checking for unistd.h... (cached) yes checking for sys/wait.h that is POSIX.1 compatible... yes checking for stdbool.h that conforms to C99... yes checking for _Bool... yes checking for an ANSI C-conforming const... yes checking for inline... inline checking for mode_t... yes checking for off_t... yes checking for size_t... yes checking whether time.h and sys/time.h may both be included... yes checking whether struct tm is in sys/time.h or time.h... time.h checking for uid_t in sys/types.h... yes checking for working volatile... yes checking for ptrdiff_t... yes checking whether closedir returns void... no checking for msgfmt... /usr/bin/msgfmt checking for gmsgfmt... /usr/bin/msgfmt checking for xgettext... /usr/bin/xgettext checking for msgmerge... /usr/bin/msgmerge checking for library containing strerror... none required checking for stdlib.h... (cached) yes checking for unistd.h... (cached) yes checking for getpagesize... yes checking for working mmap... yes checking whether we are using the GNU C Library 2.1 or newer... yes checking whether integer division by zero raises SIGFPE... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unsigned long long... yes checking for inttypes.h... yes checking whether the inttypes.h PRIxNN macros are broken... no checking for ld used by GCC... ld checking if the linker (ld) is GNU ld... yes checking for shared library run path origin... done checking for argz.h... (cached) yes checking for limits.h... (cached) yes checking for locale.h... (cached) yes checking nl_types.h usability... yes checking nl_types.h presence... yes checking for nl_types.h... yes checking for malloc.h... (cached) yes checking for stddef.h... (cached) yes checking for stdlib.h... (cached) yes checking for string.h... (cached) yes checking for unistd.h... (cached) yes checking for sys/param.h... (cached) yes checking for feof_unlocked... yes checking for fgets_unlocked... yes checking for getc_unlocked... yes checking for getcwd... yes checking for getegid... yes checking for geteuid... yes checking for getgid... yes checking for getuid... yes checking for mempcpy... yes checking for munmap... yes checking for putenv... yes checking for setenv... yes checking for setlocale... yes checking for stpcpy... yes checking for strcasecmp... yes checking for strdup... yes checking for strtoul... yes checking for tsearch... yes checking for __argz_count... yes checking for __argz_stringify... yes checking for __argz_next... yes checking for iconv... yes checking for iconv declaration... extern size_t iconv (iconv_t cd, char * *inbuf, size_t *inbytesleft, char * *outbuf, size_t *outbytesleft); checking for nl_langinfo and CODESET... yes checking for LC_MESSAGES... yes checking for bison... bison checking version of bison... 1.35, ok checking whether NLS is requested... yes checking whether included gettext is requested... no checking for GNU gettext in libc... yes checking for getmntent in -lsun... no checking for getmntent in -lseq... no checking for getmntent in -lgen... no checking for getmntent... yes checking whether gcc needs -traditional... no checking for pid_t... yes checking for unistd.h... (cached) yes checking vfork.h usability... no checking vfork.h presence... no checking for vfork.h... no checking for fork... yes checking for vfork... yes checking for working fork... yes checking for working vfork... (cached) yes checking whether lstat dereferences a symlink specified with a trailing slash... yes checking whether lstat accepts an empty string... no checking whether lstat dereferences a symlink specified with a trailing slash... (cached) yes checking for stdlib.h... (cached) yes checking for GNU libc compatible malloc... yes checking for working memcmp... yes checking for stdlib.h... (cached) yes checking for unistd.h... (cached) yes checking for getpagesize... (cached) yes checking for working mmap... (cached) yes checking for stdlib.h... (cached) yes checking for GNU libc compatible realloc... yes checking sys/select.h usability... yes checking sys/select.h presence... yes checking for sys/select.h... yes checking for sys/socket.h... (cached) yes checking types of arguments for select... int,fd_set *,struct timeval * checking for function prototypes... yes checking whether setvbuf arguments are reversed... no checking return type of signal handlers... void checking whether stat accepts an empty string... no checking for strftime... yes checking for working strtod... yes checking for __argz_count... (cached) yes checking for __argz_next... (cached) yes checking for __argz_stringify... (cached) yes checking for endpwent... yes checking for floor... no checking for ftruncate... yes checking for getcwd... (cached) yes checking for gethostbyaddr... yes checking for gethostbyname... yes checking for gethostname... yes checking for getmntent... (cached) yes checking for getmntinfo... no checking for getpass... yes checking for gettimeofday... yes checking for inet_ntoa... yes checking for memmove... yes checking for mempcpy... (cached) yes checking for memset... yes checking for munmap... (cached) yes checking for nl_langinfo... yes checking for select... yes checking for setlocale... (cached) yes checking for socket... yes checking for sqrt... no checking for stpcpy... (cached) yes checking for strcasecmp... (cached) yes checking for strchr... yes checking for strcspn... yes checking for strdup... (cached) yes checking for strerror... yes checking for strncasecmp... yes checking for strstr... yes checking for strtoul... (cached) yes checking sys/resource.h usability... yes checking sys/resource.h presence... yes checking for sys/resource.h... yes checking sys/timeb.h usability... yes checking sys/timeb.h presence... yes checking for sys/timeb.h... yes checking for mkdir... yes checking for getrlimit... yes checking for setrlimit... yes checking if the applications should be statically linked... no checking for CVSDATE... None required checking if this is a FreeBSD 4 or earlier system... no checking whether ccache support should be added... no configure: creating ./config.status config.status: creating Makefile config.status: creating docs/Makefile config.status: creating docs/man/Makefile config.status: creating intl/Makefile config.status: creating m4/Makefile config.status: creating src/Makefile config.status: creating src/kademlia/Makefile config.status: creating src/kademlia/utils/Makefile config.status: creating src/kademlia/io/Makefile config.status: creating src/kademlia/kademlia/Makefile config.status: creating src/kademlia/routing/Makefile config.status: creating src/kademlia/net/Makefile config.status: creating src/pixmaps/Makefile config.status: creating src/libs/Makefile config.status: creating src/libs/ec/Makefile config.status: creating src/libs/common/Makefile config.status: creating src/utils/Makefile config.status: creating src/utils/aLinkCreator/Makefile config.status: creating src/utils/aLinkCreator/docs/Makefile config.status: creating src/utils/aLinkCreator/src/Makefile config.status: creating src/utils/cas/Makefile config.status: creating src/utils/cas/docs/Makefile config.status: creating src/utils/wxCas/Makefile config.status: creating src/utils/wxCas/docs/Makefile config.status: creating src/utils/wxCas/src/Makefile config.status: creating src/utils/xas/Makefile config.status: creating src/utils/xas/docs/Makefile config.status: creating src/webserver/Makefile config.status: creating src/webserver/src/Makefile config.status: creating src/webserver/default/Makefile config.status: creating src/webserver/php-default/Makefile config.status: creating src/webserver/chicane/Makefile config.status: creating unittests/Makefile config.status: creating unittests/muleunit/Makefile config.status: creating unittests/tests/Makefile config.status: creating po/Makefile.in config.status: creating Compilation.flags config.status: creating config.h config.status: executing depfiles commands config.status: executing default-1 commands config.status: creating po/POTFILES config.status: creating po/Makefile Configure script has finished system check. Configured aMule 2.1.1 for 'i686-pc-linux-gnu'. aMule enabled options: **** aMule Core **** Prefix where aMule should be installed? /usr/local Should aMule be compiled with i18n support? yes Should aMule be compiled in debug mode? no Should aMule be compiled with profiling? no Should aMule be compiled with optimizations? yes Should aMule monolithic application be built? yes Should aMule daemon version be built? no Should aMule remote gui be built? (EXPERIMENTAL) no Crypto++ library/headers style? embedded **** aMule TextClient **** Should aMule Command Line Client be built? no **** aMule WebServer **** Should aMule WebServer be built? no **** aMule ED2K Links Handler **** Should aMule ED2K Links Handler be built? yes **** aMuleLinkCreator **** Should aMuleLinkCreator GUI version (alc) be built? no Should aMuleLinkCreator for console (alcc) be built? no **** aMule Statistics **** Should C aMule Statistics (CAS) be built? no Should aMule GUI Statistics (wxCas) be built? no **** General Libraries and Tools **** Should ccache support be enabled? no Libraries aMule will use to build: wxWidgets 2.6.3 crypto++ embedded zlib 1.1.4
Make error ?(
Code: [Select]
En el fichero incluído de ED2KLinkParser.cpp:44: FileLock.h: En destructor `CFileLock::~CFileLock()': FileLock.h:80: `close' sin declarar (primero use esta función) FileLock.h:80: (Cada identificador sin declarar es reportado sólo una vez para cada función en el que aparece.) make[2]: *** [ED2KLinkParser.o] Error 1 make[2]: Saliendo directorio `/home/mari/prg/amule/aMule-2.1.1/src' make[1]: *** [install-recursive] Error 1 make[1]: Saliendo directorio `/home/mari/prg/amule/aMule-2.1.1/src' make: *** [install-recursive] Error 1
More info:
$ ls -l /usr/bin/wx*
lrwxrwxrwx 1 root root 43 may 24 16:13 /usr/bin/wx-config -> /usr/lib/wx/config/gtk2-unicode-release-2.6
lrwxrwxrwx 1 root root 8 may 24 16:13 /usr/bin/wxrc -> wxrc-2.6
-rwxr-xr-x 1 root root 87951 may 24 16:13 /usr/bin/wxrc-2.6

$ ls -l /usr/local/bin/wx*
ls: /usr/local/bin/wx*: No existe el fichero o el directorio

rpm -qa | grep wx
wx-base-unicode-2.6.3-1

I've tryed some things posted in this forum, but still nothing.

Any ideas?
Title: Re: compilation in red hat 9
Post by: stefanero on May 25, 2006, 09:30:34 AM: gcc -v

plz
Title: Re: compilation in red hat 9
Post by: tuxteno2006 on May 25, 2006, 05:43:49 PM: Here it is...

$ gcc -v
Leyendo especificaciones de /usr/lib/gcc-lib/i386-redhat-linux/3.2.2/specs
Configurado con: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --host=i386-redhat-linux
Modelo de hilos: posix
gcc versión 3.2.2 20030222 (Red Hat Linux 3.2.2-5)
Title: Re: compilation in red hat 9
Post by: stefanero on May 25, 2006, 09:13:41 PM: well you need atleas gcc 3.3 :)
Title: Re: compilation in red hat 9
Post by: thedude0001 on May 25, 2006, 11:14:56 PM: Can somebody please explain me why people are still running redhat 9? If you counf RHEL as it's successor then there have been 2 subsequent release, if you count fedora (which is what redhat itself sees as the successor for home users) they have moved 5 (five!) versions on since then...

And somehow I don't think there are still security updates for RH9, are there?
Title: Re: compilation in red hat 9
Post by: stefanero on May 25, 2006, 11:23:01 PM: nope :rolleyes:
Title: Re: compilation in red hat 9
Post by: phoenix on May 26, 2006, 12:12:32 AM: tuxteno2006,

If you have root access, I suggest you take some time and do an upgrade to FC5.

Cheers!
Title: Re: compilation in red hat 9
Post by: tuxteno2006 on May 26, 2006, 12:30:46 AM: Quote
Originally posted by thedude0001
Can somebody please explain me why people are still running redhat 9? If you counf RHEL as it's successor then there have been 2 subsequent release, if you count fedora (which is what redhat itself sees as the successor for home users) they have moved 5 (five!) versions on since then...

And somehow I don't think there are still security updates for RH9, are there?

There are several explanations, you'll see:
1_ Not in every country the access to tecnology is so easy. In 3rd. world countries, to buy a new computer that can run a new SO is to expensive and many people can't.
2_ Not everybody have time to move from an old SO to a newest version every time it's available (wich is my case, I may have time at the end of the year)
3- Some people simply don't need to.
etc...

I guess some of us have to deal with this every time we need to install some new software. :(
And no, there are no security updates, so... I'm DEFENCELESS 8o

I will try de GCC update, thanks...

P.D: sorry about my english.
Title: Re: compilation in red hat 9
Post by: stefanero on May 26, 2006, 01:07:39 AM: well about your pc hardware, linux will run fine on pretty much every pc

so upgrading to fc4-5 would fail because your hardware is to old , its not windows you know :)
Title: Re: compilation in red hat 9
Post by: tuxteno2006 on May 26, 2006, 02:21:32 AM: Quote
Originally posted by stefanero
well about your pc hardware, linux will run fine on pretty much every pc

so upgrading to fc4-5 would fail because your hardware is to old , its not windows you know :)

OK! i know is not windows. i'm considering an upgrade in the near future.. Anyway, updating gcc worked! now i've got it running, on my old rh9, thanks!!!!!

also, i found this page with gcc 3.3 rpms for old rh versions, for everyone who has the same problem!!!!

http://www.trilithium.com/software/misc/

thank you again, guys!!!!!
Title: Re: compilation in red hat 9
Post by: phoenix on May 26, 2006, 03:27:05 AM: Well, hardware should not be a problem, I run debian on a 486-DX4-100 with 16 MB memory and it routes my network just fine 8) Try to do that with windows XP :D
Title: Re: compilation in red hat 9
Post by: masster on May 28, 2006, 07:37:19 PM: Quote
Originally posted by tuxteno2006
also, i found this page with gcc 3.3 rpms for old rh versions, for everyone who has the same problem!!!!

http://www.trilithium.com/software/misc/

well... odd enough... I tried upgrading from gcc 3.2.2.5 that I have presently to 3.3 but Redhat tells me that fails dependencies... of guess what???? of 2.3.3.5 THAT I ALREADY HAVE INSTALLED... 8o

So.. plz anyone lend a hand. But don't say 'quit RedHat', for me that is not a solution.
Title: Re: compilation in red hat 9
Post by: Gerd78 on May 28, 2006, 07:39:49 PM: @masster: Please post the exact error message. This is really necessary to solve the problem. And no, "Red Hat" doesn't tell you anything - these package are not Red Hat packages, they are 3rd party packages made for Red Hat.

PS: Alternatively, you might try the just released aMule 2.1.2 instead of aMule 2.1.1. The new version can be compiled with GCC 3.2 according to the ChangeLog. I didn't test, but this is what the ChangeLog suggests.
Title: Re: compilation in red hat 9
Post by: masster on May 28, 2006, 10:45:52 PM: Quote
Originally posted by Gerd78
@masster: Please post the exact error message. This is really necessary to solve the problem.
Install failed :
error: Failed dependencies:
cpp = 3.2.2-5 is needed by (installed) gcc-3.2.2-5

And same goes for gcc...
Quote
Originally posted by Gerd78
And no, "Red Hat" doesn't tell you anything - these package are not Red Hat packages, they are 3rd party packages made for Red Hat.
Let's not get picky about the words I used... I said RedHat thinking to a message issued in RedHat environment. Or is gcc issued error messages outside RedHat?
Quote
Originally posted by Gerd78
PS: Alternatively, you might try the just released aMule 2.1.2 instead of aMule 2.1.1. The new version can be compiled with GCC 3.2 according to the ChangeLog. I didn't test, but this is what the ChangeLog suggests.
I'll try, thx. But that stupid prior error bothers me. It was the same type of error that blocked me when I tried installing other software packages.
Title: Re: compilation in red hat 9
Post by: wuischke on May 28, 2006, 10:53:50 PM: When the automatic dependency solution fails, you have to do all these things by yourself.
This means: Install cpp, try to install gcc, install g++ (which will be probably another dependency) and so on.
When all dependencies are installed, you'll be able to install gcc as well.

It's not very funny, but the only way to install it this way.
Title: Re: compilation in red hat 9
Post by: Gerd78 on May 28, 2006, 11:05:55 PM: masster, stai linistit ;)

Sorry, but this is the way a package manager works. It tells you that you need a C preprocessor (=cpp) for the C compiler (=gcc). So you need the C preprocessor first, and afterwards you can install the C compiler.

You have to learn how to read the error messages correctly. The error message means that the same versions of cpp and gcc are needed. Trying to use a certain version of cpp with a different version gcc will not work. In other words, you have to update all of them at once.

To resolve the issue, you can do the following: Download everything you need into an otherwise empty directory. This includes at least cpp and gcc, but probably more. An then, change into this directory and execute:
Code: [Select]
rpm -Uvh * --testIf this doesn't return any error messages, you have everything you need and can perform the actual installation:
Code: [Select]
rpm -Uvh *If there are still error messages, you need more packages from the above site. Feel free to post them if you need help, but keep in mind that the actual error messages are much more helpful than emotions. ;)

This is especially important if you ran into the same problem in the past, as you said. rpm is a very helpful tool, but it's necessary to learn it, actually. An update to a recent release of Fedora Core could make your life much easier because it includes yum, a frontend to rpm that handles packages with complex inter-dependencies much better.

As far as it concerns my recommendation, I don't quite understand. You don't want to try compiling aMule 2.1.2 with GCC 3.2 because the installation of GCC 3.3 failed? Why? After the failed installation of GCC 3.3, GCC 3.2 is still your only compiler, why not use it?

Servus ;)
Title: Re: compilation in red hat 9
Post by: masster on May 29, 2006, 12:02:52 AM: ok... I don't get it where it comes this need of telling me the ABC of Linux (such as a needed order when installing packages). This time I'll get over. And only because I didn't mention all errors. So here they are:

1. I downloaded ALL RH9 precompiled RPMs from http://www.trilithium.com/software/misc/ (although not all were needed)

2. I started with cpp-3.3.3-1.i386.rpm (obviously, doh, I knew that). Result:
error: Failed dependencies:
cpp = 3.2.2-5 is needed by (installed) gcc-3.2.2-5

But cpp 3.2.2.5 IS ALREADY INSTALLED, because when I try to re-install cpp-3.2.2-5.i386.rpm (the SAME one I used to upgrade some 3 months ago) I get:

package cpp-3.2.2-5 is already installed

So how about that??? Installed? Not installed? What is this? Twilight zone? Or a Laurel&Hardy movie?

Oh, and another thing about version 2.1.2 compiled against gcc 3.2.
It DOESN'T WORK, got exactly the same error as the author of this thread (except in English :))
Title: Re: compilation in red hat 9
Post by: GonoszTopi on May 29, 2006, 01:39:00 AM: The error message means that you cannot upgrade cpp from 3.2.2-5 to 3.3.3-1, because the installed gcc-3.2.2-5 requires cpp-3.2.2-5 to be installed, so you canot uninstall it. In order to be able to upgrade, you either
1) install ALL 3.3.3-1 packages with the same command (e.g. rpm -i cpp-3.3.3-1.i386.rpm gcc-3.3.3-1.i386.rpm ...), or
2) first uninstall 3.2.2-5 versions of gcc, cpp, etc, then install the 3.3.3-1 versions.

I do not guarantee that these techniques work as I said, I used rpm long-long time ago, but something similar will be the solution for sure.
Title: Re: compilation in red hat 9
Post by: Gerd78 on May 29, 2006, 10:11:49 AM: Quote
Originally posted by masster
2. I started with cpp-3.3.3-1.i386.rpm (obviously, doh, I knew that). Result:
error: Failed dependencies:
cpp = 3.2.2-5 is needed by (installed) gcc-3.2.2-5

But cpp 3.2.2.5 IS ALREADY INSTALLED, because when I try to re-install cpp-3.2.2-5.i386.rpm (the SAME one I used to upgrade some 3 months ago) I get:

package cpp-3.2.2-5 is already installed

So how about that??? Installed? Not installed? What is this? Twilight zone? Or a Laurel&Hardy movie?
Sorry, masster, please calm down read my posts twice, if needed, and more carefully.

Again: This error message means that cpp-3.2.2-5 is needed by the already installed gcc-3.2.2-5. It is not needed by the to-be-installed gcc-3.3.3-1, but by the old one you already have. You cannot update cpp without updating gcc at the same time (i.e., with the same command) because cpp and gcc must be exactly the same version.

So, please, do the following:

1. Create an empty directory somewhere on your harddisk. Let's say, /tmp/gcc_update:
Code: [Select]
mkdir -p /tmp/gcc_update2. Change into that directory:
Code: [Select]
cd /tmp/gcc_update3. Download the new cpp package into that directory.
4. Test installing all packages that are stored in this directory (cpp only, at the moment):
Code: [Select]
rpm -Uvh * --test5. The error message will be the same as above. And know, after knowing what the error message means, you know that you must update gcc in the same command. Therefore:
6. Download the new gcc package into the same directory
7. Execute the same command as above, again (now it will cover cpp and gcc):
Code: [Select]
rpm -Uvh * --testThis time the error message will be different, and you are one step further. It will tell you that even more packages need to be updated at the same time.
8. Download the new versions of the packages it complains about in step 7. and then repeat step 7.
9. Repeat step 7. for all packages it complains about, until the command
Code: [Select]
rpm -Uvh * --testdoes not return any error message.
10. If you're done resolving the dependencies and the command
Code: [Select]
rpm -Uvh * --testdoes not return any error messages any more, you can perform the real installation:
Code: [Select]
rpm -Uvh *OK?
Title: Re: compilation in red hat 9
Post by: masster on May 29, 2006, 02:17:34 PM: It finally worked!

Thank you Gerd78 and everybody :)