| Bug #25475 | Broken download link for MySQL 5.1.11 Linux x86 generic RPM (statically linked a | ||
|---|---|---|---|
| Submitted: | 8 Jan 2007 19:48 | Modified: | 9 Jan 2007 20:57 |
| Reporter: | Rick Mann | Email Updates: | |
| Status: | Unsupported | Impact on me: | |
| Category: | MySQL Server: Packaging | Severity: | S3 (Non-critical) |
| Version: | 5.1.11 | OS: | Linux (Linux) |
| Assigned to: | CPU Architecture: | Any | |
[8 Jan 2007 19:48]
Rick Mann
[9 Jan 2007 11:03]
Sveta Smirnova
Thank you for the report. glibc 2.2 is a very old glibc, so we will not generate 5.1 for glibc 2.2. If you need MySQL server statically linked against glibc 2.2, use old binaries or compile it yourself.
[9 Jan 2007 12:10]
Joerg Bruehe
I'm sorry we have to disappoint you, but the switch to version 5.1 will be used to stop building for that obsolete version 2.2 of glibc. Early 5.1 builds were also done on that platform (that's why you see 5.1.11 there), but we have now changed that. So if you run a machine (x86) with glibc 2.2, you have these choices: 1) Build from source, using your installed glibc. 2) Build from source, but apply the MySQL patch to your glibc. 3) Move the database to a newer server, for which we provide packages. More details: 1) To build from source: This is a sample "configure" line as we used it in 5.1 for glibc 2.2 builds (broken across many lines here): CC="ccache gcc" CXX="ccache gcc" LDFLAGS=-L/usr/local/lib CPPFLAGS="-I/usr/local/include -DDEFAULT_THREAD_STACK=126976" CFLAGS="-O2 -mcpu=pentiumpro" CXXFLAGS="-O2 -mcpu=pentiumpro -felide-constructors" ./configure --prefix=/usr/local/mysql --localstatedir=/usr/local/mysql/data --libexecdir=/usr/local/mysql/bin --enable-thread-safe-client --enable-local-infile --enable-assembler --with-pic --with-fast-mutexes --disable-shared --with-big-tables --with-ssl --with-readline --with-archive-storage-engine --with-blackhole-storage-engine --with-ndbcluster --with-csv-storage-engine --with-example-storage-engine --with-partition --with-federated-storage-engine --with-innodb --with-extra-charsets=all If you like, add (some of) these options: --with-comment="insert your preferences here" --with-server-suffix="-yours" --with-debug --without-ndb-debug When we generate debug binaries, we lower (or omit) the "-O" option for the compiler optimization. Of course, you can omit "--with-" options for table handlers you do not use. Depending on your use, "--with-ndbcluster" is a likely candidate. 2) To apply the patch to glibc 2.2: Please get the details (and the reasoning) here: http://dev.mysql.com/doc/refman/5.1/en/source-notes-linux.html My knowledge there is limited, but my understanding is that you do not need that patch if you support few threads (= concurrent users) only. 3) A separate DB server: Especially for those who use MySQL to manage production data (or plan to do that), as well as for those who have high performance requirements, we recommend to use the switch to MySQL 5.1 to also move away from old platforms (both hardware and operating system). Even if you (they) have to keep the old machine running for an application you (they) cannot upgrade to a newer platform, adding a newer machine to run as a database server should be considered. They can still run their applications on old clients, accessing that server. This also allows to switch to faster CPUs and larger memories (especially 64 bit systems) and so to increase performance. So I am sorry we cannot immediately help you, and I propose you follow one of the routes above.
[9 Jan 2007 20:57]
Rick Mann
Thank you for the very helpful post on how to build things. I would only point out, then, that the broken links should be removed from the download page.
