Main Stories
Slash Boxes

Slash Open Source Project

Slashcode Log In

Log In

[ Create a new account ]

Article Poll

Poll I found this article to be
Very Helpful
Helpful
Not Helpful
Not Very Helpful
[ Results | Polls ]
Comments:0 | Votes:0

MySQL Installation

posted by Krow on 09:00 AM August 3rd, 2001   Printer-friendly   Email story
mb12036 writes "I've run out of places to turn to, so I'm hoping somebody here will be able to help. I've just put a fresh default install of Red Hat 7.1 on a new box here. Some developers wanted to have a slash site setup for some projects going on here. I'm not hugely familiar with linux, but usually I can get done what I need to, sometimes it just takes awhile. But danged if I can get past that rotten MySQL installation...I've compiled the source and I've tried to install the binary distribution...Never works. There are too many different errors to really provide here. I'm just wondering if anyone has tips/tricks for installing MySQL on Redhat 7.1 that I should know about? Is there some dumb thing I'm not doing? Clearly this is operator error, but I can't find crap about MySQL and Red Hat 7.1 installations. Doing exactly what the MySQL instructions tell me to do, is not getting me anwhere. Thanks for any help -- Matt"
This discussion has been archived. No new comments can be posted.
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login
Loading... please wait.
  • Take a look at: http://mysql.com/downloads/mysql-3.23.html and grab the rpm. I know this sounds simple, but this is exactly what I did earlier this week myself. mySQL on a fresh RH7.1 install in order to setup slash... They mySQL part went pretty smooth, although I had a little trouble with slash...
  • I did the same thing ... the RPM installation is very easy. Take advantage of red hats main feature, RPM.
  • by Anonymous Coward
    As others have suggested, the mysql rpm is the way to go... It is part of the default install of redhat (all versions I have seen). Installing from source could be painfull since redhat doesn't always put it's files in the same places as other Unices. You should have the mysql rpm on your redhat cd. (sheesh, it won't let me post this comment with the proper capitilization!)
  • ok...now that IE crashed before I was going to submit my comment, I'll try again. Now for the short, short version. I disagree with the other posts. I just got finished with a SLASHCODE install on RH 7.1. I haven't had much luck with installing APACHE, PHP, MYSQL, PERL using RPM on servers. Maybe that has changed since I tried last, but I found that it was easier with source. I recommend getting the latest MySQL source tarball from here [mysql.com] and then finding a tutorial like this one here [lycos.com]. The only other thing I can tell you is start with the first error and fix it and continue down the line. Retrying the build/install after each error is fixed (or you believe has been fixed). Trial and error my friend. Time consumming? Absolutely, but its the only way.
    You could always post the error message up here, swallow your pride, take some heat, but get an answer that may help. Usually, I find that it is some library missing from the box, and once that is installed, things run pretty smooth with MySQL installs. btw, if you did a custom install on that box, I hope you didn't ignore package dependencies. That tends to be a real bitch to fix. Otherwise, your probably just missing something like a library or utility. Also, don't use any configure flags other than PREFIX= just in case that is where the problem is orginating. ok...one last thing....I just found this in with some of my documentation. If you're getting errors with ld. once, I had to edit /etc/ld.so.conf and add the line "/usr/local/mysql/lib/mysql" (the directory with libmysqlclient.so in it). then do a /sbin/ldconfig I can't remember what that was about exactly, but I think its necessary for the MySQL daemon to start. I found that out while troubleshooting something once and it fixed my problem regarding the .so that was not found error message I was getting.
    Conclusion:
    Either post the errors or take the weekend off and start over fresh Monday and try to fix the errors one at a time.
    have fun!