Re: glibc 2.3 causing compile problems?
It has been standard practice with Red Hat as long as I have been using linux (MKLinux DR3 was my first distro - and that was Red Hat 5.1 except with the Mach 3 mikrokernel and ppc binaries) to create a package containing just the stuff the user needs to use the software (binary, config files, documentation) in one package - and to put the headers and stuff in a second package noted devel. This allows people who don't want to do development on their system to install far less number of packages and thus save space. A lot of people have no intention of compiling anything on their system, and it is common practice on web servers to not install a compiler so that a cracker can't compile any code on the machine should he get on. in these cases, where for whatever reason the user does not want to do any software compiling, the headers for things like bzip2 etc. really *don't* need to be installed. I agree with the Red Hat model of seperating out the headers. Back when I did some web dev on a little IBM Thinkpad with a small hard drive, I didn't *want* the extra space taken that installing headers would take. On Thu, 2002-11-28 at 16:15, Rikard Bostrom wrote: Hi, The reason the program didn't compile had something to do with bzip2. If I installed the rpm bzip2-development it worked like a charm... same thing if I downloaded the bzip2 source code and compiled that. I think it's stupid that the bzip2-development package wasn't installed in the first place, as I selected all the development packages in the install. But bzip2 isn't even listed there, so I had to install it manually. I really don't like RedHat's package tool in 8.0, is there an other tool out there I can use? /dahonk -- Michael A. Peters [EMAIL PROTECTED] -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list
Re: glibc 2.3 causing compile problems?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thu, 28 Nov 2002 00:31:40 +0100, Rikard Bostrom wrote: I'm running RedHat 8.0. I've installed all the development packages there is to be installed, but I still get errors and make stops when I try to compile certain programs. I used to run Slackware 8.1, and all programs compiled fine under it. Does this has something to do with RedHat 8.0 shipping a buggy version of glibc? Or buggy source code. ;) Is there anyway do downgrade to a older, more stable version? Can you give any particular examples of what makes you believe the shipped version would be buggy? Because if you were right, you should submit a bug report at https://bugzilla.redhat.com - -- -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) iD8DBQE95gUD0iMVcrivHFQRAmc7AKCC4Fo34UDC0bQbPxTD561Ra08JGgCeMKS9 Gr+fPFoausaKvgxzcUor3n0= =o9aP -END PGP SIGNATURE- -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list
Re: glibc 2.3 causing compile problems?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thu, 28 Nov 2002 00:31:40 +0100, Rikard Bostrom wrote: I'm running RedHat 8.0. I've installed all the development packages there is to be installed, but I still get errors and make stops when I try to compile certain programs. I used to run Slackware 8.1, and all programs compiled fine under it. Does this has something to do with RedHat 8.0 shipping a buggy version of glibc? Or buggy source code. ;) Is there anyway do downgrade to a older, more stable version? Can you give any particular examples of what makes you believe the shipped version would be buggy? Because if you were right, you should submit a bug report at https://bugzilla.redhat.com - -- -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) iD8DBQE95gUD0iMVcrivHFQRAmc7AKCC4Fo34UDC0bQbPxTD561Ra08JGgCeMKS9 Gr+fPFoausaKvgxzcUor3n0= =o9aP -END PGP SIGNATURE- -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list I was having the same problems until I realived that 8.0 builds with gcc 3.2 only. Now I update the cvs trees and apply my patches for gcc 3.2. Redhat does have a compatibility rpm for gcc 2.96 (err something like that) ie. binaries that were compiled with gcc 2.X are able to run on 8.0 but the building compiles for 3.2. The long and short, re-work your tree for 3.2 or use another build box (/w 2.9X). -- Jesse Jacobs, Supa' Noob :) -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list
Re: glibc 2.3 causing compile problems?
Hi, My problems are now addressed to the source code of the software I tried to compile, so I guess it's not really glibc's fault. But I'll keep my eyes open! :-) Thanks for all your answers. /dahonk -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list
Re: glibc 2.3 causing compile problems?
Hi, The reason the program didn't compile had something to do with bzip2. If I installed the rpm bzip2-development it worked like a charm... same thing if I downloaded the bzip2 source code and compiled that. I think it's stupid that the bzip2-development package wasn't installed in the first place, as I selected all the development packages in the install. But bzip2 isn't even listed there, so I had to install it manually. I really don't like RedHat's package tool in 8.0, is there an other tool out there I can use? /dahonk -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list
Re: glibc 2.3 causing compile problems?
On Wed, 2002-11-27 at 15:31, Rikard Bostrom wrote: Hi, I'm running RedHat 8.0. I've installed all the development packages there is to be installed, but I still get errors and make stops when I try to compile certain programs. I used to run Slackware 8.1, and all programs compiled fine under it. Does this has something to do with RedHat 8.0 shipping a buggy version of glibc? Is there anyway do downgrade to a older, more stable version? /dahonk I don't know if this will solve your problem - but where I use to work, we would do a Red Hat 6.2 install and then chroot to it when there was something we needed to compile that Red Hat 7.0's compiler choked on. The obvious disadvantage to this was that some things needed older versions of libraries when we brought the binary into the RH 7 environment - for those cases, we had a machine that was RH7 but had the older gcc on it in /usr/local - and we would specify that gcc. Perhaps if the problem is Red Hat's glibc (check with the code maintainer - he may know the problem, its possible you just need the makefile updated) you could build an older glibc and install it in /usr/local and specify those libraries when compiling this software? -- Michael A. Peters [EMAIL PROTECTED] -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list
