Comments on: Binaries of MySQL 5.0.33 Community release for AMD64 / EM64T http://www.mysqlperformanceblog.com/2007/01/12/binaries-of-mysql-5033-community-release-for-amd64-em64t/ Everything about MySQL Performance Tue, 02 Dec 2008 14:49:06 +0000 http://wordpress.org/?v=2.5.1 By: Ronald Bradford http://www.mysqlperformanceblog.com/2007/01/12/binaries-of-mysql-5033-community-release-for-amd64-em64t/#comment-96044 Ronald Bradford Tue, 27 Mar 2007 06:42:02 +0000 http://www.mysqlperformanceblog.com/2007/01/12/binaries-of-mysql-5033-community-release-for-amd64-em64t/#comment-96044 Hi Guys, I'm trying to compile this under Solaris 10 AMD64 without success. I can successfully compile MySQL 5.0.33 source. Compiling your source gives the following error. Any clues into correct the openSSL problem would be greatly appreciated. then mv -f ".deps/vio.Tpo" ".deps/vio.Po"; else rm -f ".deps/vio.Tpo"; exit 1; fi In file included from vio_priv.h:24, from vio.c:24: ../include/violite.h:95:30: openssl/opensslv.h: No such file or directory ../include/violite.h:106:25: openssl/ssl.h: No such file or directory ../include/violite.h:107:25: openssl/err.h: No such file or directory In file included from vio_priv.h:24, from vio.c:24: ../include/violite.h:111: error: syntax error before "SSL_CTX" ../include/violite.h:111: warning: no semicolon at end of struct or union make[2]: *** [vio.o] Error 1 Hi Guys,

I’m trying to compile this under Solaris 10 AMD64 without success.
I can successfully compile MySQL 5.0.33 source.
Compiling your source gives the following error. Any clues into correct the openSSL problem would be greatly appreciated.

then mv -f “.deps/vio.Tpo” “.deps/vio.Po”; else rm -f “.deps/vio.Tpo”; exit 1; fi
In file included from vio_priv.h:24,
from vio.c:24:
../include/violite.h:95:30: openssl/opensslv.h: No such file or directory
../include/violite.h:106:25: openssl/ssl.h: No such file or directory
../include/violite.h:107:25: openssl/err.h: No such file or directory
In file included from vio_priv.h:24,
from vio.c:24:
../include/violite.h:111: error: syntax error before “SSL_CTX”
../include/violite.h:111: warning: no semicolon at end of struct or union
make[2]: *** [vio.o] Error 1

]]> By: Vadim http://www.mysqlperformanceblog.com/2007/01/12/binaries-of-mysql-5033-community-release-for-amd64-em64t/#comment-70236 Vadim Mon, 05 Mar 2007 09:09:25 +0000 http://www.mysqlperformanceblog.com/2007/01/12/binaries-of-mysql-5033-community-release-for-amd64-em64t/#comment-70236 John, Here is it http://www.mysqlperformanceblog.com/files/binaries/5.0.33/mysql-mpb.spec John,

Here is it
http://www.mysqlperformanceblog.com/files/binaries/5.0.33/mysql-mpb.spec

]]> By: John http://www.mysqlperformanceblog.com/2007/01/12/binaries-of-mysql-5033-community-release-for-amd64-em64t/#comment-63199 John Tue, 27 Feb 2007 19:56:43 +0000 http://www.mysqlperformanceblog.com/2007/01/12/binaries-of-mysql-5033-community-release-for-amd64-em64t/#comment-63199 Hey dudes, Is there anyway you can publish your spec file or src.rpm ? I want to recopile mysql 5.0.33 with sphinx SE. Hey dudes,

Is there anyway you can publish your spec file or src.rpm ? I want to recopile mysql 5.0.33 with sphinx SE.

]]> By: Vadim http://www.mysqlperformanceblog.com/2007/01/12/binaries-of-mysql-5033-community-release-for-amd64-em64t/#comment-38883 Vadim Mon, 29 Jan 2007 09:35:54 +0000 http://www.mysqlperformanceblog.com/2007/01/12/binaries-of-mysql-5033-community-release-for-amd64-em64t/#comment-38883 James Yes, I understand your optimism :) However I'm pessimistic in this case and I will be surprised if more than one-two patches will be included in Community server this year. Anyway there are 11 months to go, will see :) James

Yes, I understand your optimism :)

However I’m pessimistic in this case and I will be surprised if more than one-two patches will be included in Community server this year. Anyway there are 11 months to go, will see :)

]]> By: James Day http://www.mysqlperformanceblog.com/2007/01/12/binaries-of-mysql-5033-community-release-for-amd64-em64t/#comment-38824 James Day Mon, 29 Jan 2007 07:08:13 +0000 http://www.mysqlperformanceblog.com/2007/01/12/binaries-of-mysql-5033-community-release-for-amd64-em64t/#comment-38824 Vadim, I'm naturally an optimist and here I'm speaking in public so I have to try to be nice. :) Besides, all I did was explain the plan. I don't know if it will work, but it is the plan. I have no good idea about how many community patches will be included in the next year. I would be surprised if it was more than 100 or less than 5. But maybe I will be surprised. Vadim, I’m naturally an optimist and here I’m speaking in public so I have to try to be nice. :) Besides, all I did was explain the plan. I don’t know if it will work, but it is the plan.

I have no good idea about how many community patches will be included in the next year. I would be surprised if it was more than 100 or less than 5. But maybe I will be surprised.

]]> By: Vadim http://www.mysqlperformanceblog.com/2007/01/12/binaries-of-mysql-5033-community-release-for-amd64-em64t/#comment-32538 Vadim Fri, 19 Jan 2007 08:29:26 +0000 http://www.mysqlperformanceblog.com/2007/01/12/binaries-of-mysql-5033-community-release-for-amd64-em64t/#comment-32538 James, You are speaking like a marketing guy :) Do you still work in MySQL Support ? ;) Well, how many community patches you expect will be included in Community release next year ? James,

You are speaking like a marketing guy :) Do you still work in MySQL Support ? ;)

Well, how many community patches you expect will be included in Community release next year ?

]]> By: James Day http://www.mysqlperformanceblog.com/2007/01/12/binaries-of-mysql-5033-community-release-for-amd64-em64t/#comment-32352 James Day Fri, 19 Jan 2007 00:17:33 +0000 http://www.mysqlperformanceblog.com/2007/01/12/binaries-of-mysql-5033-community-release-for-amd64-em64t/#comment-32352 Jason, right. The Community builds will probably be a bit less stable. On the other hand, they will have user features before those features can be incorporated into the next release of the production server version. So today you can't get a user feature into Enterprise 5.0 but you may well be able to get it into Community 5.0, because Community 5.0 can take more risks than Enterprise. Not being able to get things into the production releases has often irritated people who want to be closer to the cutting edge and this is one attempt at a solution. We'll see how it works out. Hopefully it'll show that those features are stable and really popular and they'll be incorporated into the next full release. Enterprise binaries will only be made available by MySQL to Enterprise customers, along with the source for anyone who wants it. Jason, right. The Community builds will probably be a bit less stable. On the other hand, they will have user features before those features can be incorporated into the next release of the production server version. So today you can’t get a user feature into Enterprise 5.0 but you may well be able to get it into Community 5.0, because Community 5.0 can take more risks than Enterprise. Not being able to get things into the production releases has often irritated people who want to be closer to the cutting edge and this is one attempt at a solution. We’ll see how it works out. Hopefully it’ll show that those features are stable and really popular and they’ll be incorporated into the next full release.

Enterprise binaries will only be made available by MySQL to Enterprise customers, along with the source for anyone who wants it.

]]> By: peter http://www.mysqlperformanceblog.com/2007/01/12/binaries-of-mysql-5033-community-release-for-amd64-em64t/#comment-31743 peter Wed, 17 Jan 2007 22:14:04 +0000 http://www.mysqlperformanceblog.com/2007/01/12/binaries-of-mysql-5033-community-release-for-amd64-em64t/#comment-31743 Jason, The question of stability of Enterprise vs Community is good one, and the true answer will be - it is yet unknown. It will depend on number of factors, for example what kind of community patches MySQL will accept for community version, how solid they would be ? What kind of testing Enterprise version will get compared to Community - remember Enterprise goes out first as a binary, opposite to Fedora/Redhat case so Enterprise users will act as beta testers. But as it is no there should not be much of the difference as Community and Enterprise is still the same source tree. Jason,

The question of stability of Enterprise vs Community is good one, and the true answer will be - it is yet unknown. It will depend on number of factors, for example what kind of community patches MySQL will accept for community version, how solid they would be ? What kind of testing Enterprise version will get compared to Community - remember Enterprise goes out first as a binary, opposite to Fedora/Redhat case so Enterprise users will act as beta testers.

But as it is no there should not be much of the difference as Community and Enterprise is still the same source tree.

]]> By: Jason Frisvold http://www.mysqlperformanceblog.com/2007/01/12/binaries-of-mysql-5033-community-release-for-amd64-em64t/#comment-31740 Jason Frisvold Wed, 17 Jan 2007 21:59:10 +0000 http://www.mysqlperformanceblog.com/2007/01/12/binaries-of-mysql-5033-community-release-for-amd64-em64t/#comment-31740 James, Thanks for the clarification. So community builds will tend to be more cutting edge and *possibly* less stable? ie, Fedora vs RHEL. Enterprise releases won't be available for general download in binary form? Or both binary and source? James,

Thanks for the clarification. So community builds will tend to be more cutting edge and *possibly* less stable? ie, Fedora vs RHEL.

Enterprise releases won’t be available for general download in binary form? Or both binary and source?

]]> By: James Day http://www.mysqlperformanceblog.com/2007/01/12/binaries-of-mysql-5033-community-release-for-amd64-em64t/#comment-31183 James Day Tue, 16 Jan 2007 22:48:14 +0000 http://www.mysqlperformanceblog.com/2007/01/12/binaries-of-mysql-5033-community-release-for-amd64-em64t/#comment-31183 Jason, some community releases will be source only, some will be binary as well. A source build was released recently, I'm expecting (not guaranteed!) the next one sometime next month. The big schedule change has been the introduction of somewhat guaranteed monthly builds for Enterprise customers. Also the Community server builds will contain end user code that won't be in the Enterprise releases because incorporating enhancements would breach their stability objective - which largely prohibits introducing non-bugfix code. Andrisi, building is scripted but a full production release is actually lot of work and takes at least a week of some members of the build team's time per release, so their time limits how many full builds can be done. Source releases are much less time-consuming and don't tend to use resources needed by other ongoing builds that must be deconflicted. The work isn't so much the builds, although they take a while, there's also the testing and fixing of problems that show up in them and it's really easy to underestimate how much time it takes. Jason, some community releases will be source only, some will be binary as well. A source build was released recently, I’m expecting (not guaranteed!) the next one sometime next month. The big schedule change has been the introduction of somewhat guaranteed monthly builds for Enterprise customers. Also the Community server builds will contain end user code that won’t be in the Enterprise releases because incorporating enhancements would breach their stability objective - which largely prohibits introducing non-bugfix code.

Andrisi, building is scripted but a full production release is actually lot of work and takes at least a week of some members of the build team’s time per release, so their time limits how many full builds can be done. Source releases are much less time-consuming and don’t tend to use resources needed by other ongoing builds that must be deconflicted. The work isn’t so much the builds, although they take a while, there’s also the testing and fixing of problems that show up in them and it’s really easy to underestimate how much time it takes.

]]>