MySQL allows to just statically link mysqld, but still build the client shared libraries. Rather than just configure if the whole package will be linked statically, it would be nice to say to only apply 'static' to mysqld. (Attached is a proposed patch for mysql-5.XXX and mysql-4.1.X ebuilds) Reproducible: Always Steps to Reproduce:
Created attachment 66370 [details, diff] proposed patch for 5.0 ebuilds
Created attachment 66371 [details, diff] proposed patch for 4.1 ebuilds
why do you want mysqld built statically? it's slower than being built shared.
(In reply to comment #3) > why do you want mysqld built statically? > it's slower than being built shared. Not at all... we couldn't achieve 13% like it is stated in the documentation of mysql, but it's faster. The official binaries are also linked statically. http://dev.mysql.com/doc/mysql/en/compile-and-link-options.html If you link dynamically (without -static), the result is 13% slower on Linux. Note that you still can use a dynamically linked MySQL library for your client applications. It is the server that is most critical for performance.
umm, with your patch applied, this case also fails: USE='mysql-static-daemon ssl' emerge mysql I'm doing some benchmarking, on a new box I've got recently, as I'm very certain that shared is still faster (for the sole reason that stuff is already in the cache
me too prefere an all or nothing "static" flag, afraid to close this as wontfix.
