Created attachment 555992 [details] dev-db:mysql-5.7.24:20181122-220133.log [ 80%] Linking CXX executable mysqlbinlog cd /var/tmp/portage/dev-db/mysql-5.7.24/work/mysql-5.7.24_build/client && /usr/bin/cmake -E cmake_link_script CMakeFiles/mysqlbinlog.dir/link.txt --verbose=1 /usr/x86_64-pc-linux-gnu/gcc-bin/7.3.0/x86_64-pc-linux-gnu-g++ -O2 -pipe -felide-constructors -fno-strict-aliasing -Wall -Wextra -Wformat-security -Wvla -Wimplicit-fallthrough=2 -Woverloaded-virtual -Wno-unused-parameter -DNDEBUG -DDBUG_OFF -Wl,-O1 -Wl,--as-needed CMakeFiles/mysqlbinlog.dir/mysqlbinlog.cc.o -o mysqlbinlog -lpthread ../archive_output_directory/libmysqlclient.a ../libbinlogevents/lib/libbinlogevents.a -lssl -lcrypto -ldl ../archive_output_directory/libmysys.a ../archive_output_directory/libdbug.a ../archive_output_directory/libmysys.a ../archive_output_directory/libdbug.a -lz -lm -lrt -latomic ../archive_output_directory/libstrings.a -lpthread ../archive_output_directory/libmysqlclient.a(mf_iocache2.c.o): In function `my_b_fill': mf_iocache2.c:(.text+0x1b0): undefined reference to `mysql_file_seek' mf_iocache2.c:(.text+0x1db): undefined reference to `mysql_file_read' ../archive_output_directory/libmysqlclient.a(mf_iocache2.c.o): In function `my_b_filelength': mf_iocache2.c:(.text+0x3c9): undefined reference to `mysql_file_seek' collect2: error: ld returned 1 exit status make[2]: *** [client/CMakeFiles/mysqlbinlog.dir/build.make:105: client/mysqlbinlog] Error 1 make[2]: Leaving directory '/var/tmp/portage/dev-db/mysql-5.7.24/work/mysql-5.7.24_build' make[1]: *** [CMakeFiles/Makefile2:1641: client/CMakeFiles/mysqlbinlog.dir/all] Error 2 make[1]: *** Waiting for unfinished jobs....
This is probably not going to be fixed: We are removing USE=client-libs and once this is gone, we don't need USE=server anymore. In other words: We don't support USE=-server anymore...
> (In reply to Thomas Deutschmann from comment #1) > This is probably not going to be fixed: We are removing USE=client-libs and > once this is gone, we don't need USE=server anymore. In other words: We > don't support USE=-server anymore... But this ebuild marked as stable still has this USE flag?! So either support it or remove that USE flag?! Or ignore it, so at least building works again?! I'm confused.
Created attachment 556974 [details, diff] Fixes build with USE=-server Found a patch fixing the build
(In reply to Peter Große from comment #2) > But this ebuild marked as stable still has this USE flag?! So either support > it or remove that USE flag?! Or ignore it, so at least building works again?! In the past we had USE=server and USE=client-libs. They are somehow counterparts. Since February 2018 (https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=91a40d40c493c2c209f9f91f3909f4164d69b08f) we have a mask for USE=client-libs in place -- USE=client-libs is going away. Once USE=client-libs is removed, we will also remove USE=server (which will be equal to enforced USE=server). So please tell us why you are installing dev-db/mysql[-server]: Without USE=client-libs (which is masked) and without USE=server, this package should be useless. So you are either already ignoring our mask or... in any case it is unsupported. :)
(In reply to Thomas Deutschmann from comment #4) > So please tell us why you are installing dev-db/mysql[-server]: Without > USE=client-libs (which is masked) and without USE=server, this package > should be useless. It provides tools like mysql or mysqldump, which I use on remote servers without having a server running locally. Do you consider this as useless? > So you are either already ignoring our mask or... in any > case it is unsupported. :) I'm not ignoring your mask. I don't have any custom settings regarding mysql apart from the USE=-server flag. To be frankly, I don't care if it's unsupported. The USE flag is still there and if I'm able to switch it off, my build should not break. During deprecation you can handle this by ignoring it within the ebuild or something like that, or at least give the user a hint via einfo that this is unsupported. It breaks my build on a stable system and I'm just annoyed by that. Please consider doing something about this.
(In reply to Thomas Deutschmann from comment #4) > (In reply to Peter Große from comment #2) > > But this ebuild marked as stable still has this USE flag?! So either support > > it or remove that USE flag?! Or ignore it, so at least building works again?! > > In the past we had USE=server and USE=client-libs. They are somehow > counterparts. Since February 2018 > (https://gitweb.gentoo.org/repo/gentoo.git/commit/ > ?id=91a40d40c493c2c209f9f91f3909f4164d69b08f) we have a mask for > USE=client-libs in place -- USE=client-libs is going away. > > Once USE=client-libs is removed, we will also remove USE=server (which will > be equal to enforced USE=server). > > So please tell us why you are installing dev-db/mysql[-server]: Without > USE=client-libs (which is masked) and without USE=server, this package > should be useless. So you are either already ignoring our mask or... in any > case it is unsupported. :) One thing is related to compilation time it's just quicker without server, second - in my case it broke system which stores data on remote mysql server and need only client libraries. It (that removal) is totaly in opposite to what gentoo is (its idea). If we start remove that basic flags (which is needed for probably many reasons) maybe we should cancel this project becasue the difference between debian packages and gentoo ebuild starts to disappear. Why should I compile package with everything client and server if I had the same within a seconds installed by deb package. I'm against these change. Please revert this move and restore -server possibility in this package
As a workaround I moved to using dev-db/mariadb -server. The latest stable compiles and works fine for me.
(In reply to Peter Große from comment #7) > As a workaround I moved to using dev-db/mariadb -server. The latest stable > compiles and works fine for me. it's even worse than I thought - even debian got package called libmysql, where we heading with these change? To monolithic system? Lets compile everything what possible at once why should one use any use flags?
I just ran into this failure today and discovered this bug. Tell me you're not serious about requiring a full server install whether it's needed or not. I can assure that everyone with, for example, a MythTV frontend system uses mysql with -server. Even binary distributions at least have separate client and server packages. Frankly I don't understand anything about the client-libs USE. I was never even aware of that before, but have always had -server on my MythTV frontend. That's been available basically forever. Is this that difficult to support. What's motivating this?
I can verify that the attached patch allows this to compile successfully. I think I understand this situation a bit better now. I take it that, since the mysql client library stuff (such as libmysqlclient.so) are now provided by dev-db/mysql-connector-c (by way of virtual/libmysqlclient-18), mysql with -server does nothing but provide cli programs like mysql etc. I started looking into the possibility of removing the virtual/mysql requirement from mythtv. The real mysql requirements there, especially for a frontend only system, are by way of things like dev-qt/qtsql, which only require virtual/libmysqlclient-18. Unfortunately however there are apparently still other packages, for example dev-python/mysql-python (which happens to be required for the mythtv python bindings), that are requiring virtual/mysql instead of virtual/libmysqlclient-18, which is probably all they need. Currently things like that would force a full mysql server install without the server USE flag.
This was all announced starting with "2015-07-28-mysql-packaging-changes" and future announcements: The server packages are no longer providing client libs. Client libs are now provided by dedicated packages like dev-db/mysql-connector-c or dev-db/mariadb-connector-c. Therefore installilng server packages without USE=server doesn't make sense anymore and is unsupported. Yes, transition is still on the way, see https://bugs.gentoo.org/buglist.cgi?list_id=4136088&query_format=advanced&resolution=---&short_desc=validate%20mysql&short_desc_type=allwordssubstr ... so there are a lot of packages who aren't updated yet.
I see. Thanks for the clarification. I noticed that that mass filing didn't mention the virtual/libmysqlclient package at all. I see a number of packages have already been changed to depend on that...for example dev-qt/qtsql. I noticed however that one I mentioned above...dev-python/mysql-python, has a version mysql-python-1.2.5-r2 that's been changed to depend directly on dev-db/mysql-connector-c. Wouldn't the virtual/libmysqlclient be the correct dependency in most cases?
*** Bug 675878 has been marked as a duplicate of this bug. ***
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/proj/mysql-extras.git/commit/?id=596d171d828ced4a268af307f42c64fa5bac993e commit 596d171d828ced4a268af307f42c64fa5bac993e Author: Thomas Deutschmann <whissi@gentoo.org> AuthorDate: 2019-01-26 19:19:24 +0000 Commit: Thomas Deutschmann <whissi@gentoo.org> CommitDate: 2019-01-26 19:19:24 +0000 Add 20018_all_mysql-5.7.25-fix-build-without-server.patch Bug: https://bugs.gentoo.org/671722 Signed-off-by: Thomas Deutschmann <whissi@gentoo.org> 20018_all_mysql-5.7.25-fix-build-without-server.patch | 12 ++++++++++++ 1 file changed, 12 insertions(+)
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=dfef360c35d4e9d197837d3d57258fca41adf785 commit dfef360c35d4e9d197837d3d57258fca41adf785 Author: Thomas Deutschmann <whissi@gentoo.org> AuthorDate: 2019-01-26 19:23:31 +0000 Commit: Thomas Deutschmann <whissi@gentoo.org> CommitDate: 2019-01-26 19:23:49 +0000 dev-db/mysql: bump to v5.7.25 Closes: https://bugs.gentoo.org/671722 Package-Manager: Portage-2.3.58, Repoman-2.3.12 Signed-off-by: Thomas Deutschmann <whissi@gentoo.org> dev-db/mysql/Manifest | 2 + dev-db/mysql/mysql-5.7.25.ebuild | 946 +++++++++++++++++++++++++++++++++++++++ 2 files changed, 948 insertions(+)
Thank you for the patch. Will there be a way in the future to install the client binaries (/usr/bin/mysql, /usr/bin/mysqldump) without installing the server? I don't mean just the client libraries here, but the binaries too.
So confusing change, until that change it was simple that if you want only libraries enable client use flag, but after this change you'll be forced - as in other distros to google how to install only mysql libraries or what's the name of package - which creates many confusions and a lot of problems related to updates needed in all portage packages using mysql library - lot of unneeded mess and trouble creating change which for me is hard to defend.
