The newest Samba 3 alpha 22 ebuild wants to use mysql v3 explictly, which is a downgrade for those running MySQL v4. I can't find anything in Bugzilla or the changelog about this change from previous ebuilds. Looking thru the configure output I see this: checking for mysql_config... /usr/bin/mysql_config checking for MYSQL - version >= 0.11.0... no *** Could not run MYSQL test program, checking why... *** The test program compiled, but did not run. This usually means *** that the run-time linker is not finding MYSQL or finding the wrong *** version of MYSQL. If it is not finding MYSQL, you'll need to set your *** LD_LIBRARY_PATH environment variable, or edit /etc/ld.so.conf to point *** to the installed location Also, make sure you have run ldconfig if that *** is required on your system *** *** If you have an old version installed, it is best to remove it, although *** you may also be able to get things to work by modifying LD_LIBRARY_PATH it then continues to build without mysql support. this would seem to be a Samba bug then. For the moment I think it would be better to allow samba builds of like anyway instead of forcing a downgrade to mysql v3. As a side note, the ebuild doesn't have a digest for samba-vscan-0.3.2.tar.bz2.
Well, just change this in the ebuild: mysql? ( =dev-db/mysql-3* sys-libs/zlib ) to: ( =dev-db/mysql-3* sys-libs/zlib )
Bjarke: That's a hack IMHO What if somebody wanted to use MySQL v4 together with Samba ?
AFAIK >=dev-db/mysql-3* instead of =dev-db/mysql-3* would allow 3 and up to be used, but I'm not sure.
If the limit to MySQL v3 was put in place because of the API change in MySQL, please be aware that MySQL 4.0.11a-r1 has -DUSE_OLD_FUNCTIONS defined, so that they are available (see bug 15099)
i'll fixit when i get to my next update round ;-)
ok.
