After upgrading to the latest gabber, I realized that my gabber client did not have the 'Enable SSL' option on the gui anymore. I have USE="ssl" (among other use flags) /etc/make.profile/make.defaults and it seems the earlier gabber ebuild (gabber-0.8.7-r3.ebuild) was built with SSL support as a result. (I can confirm this since I see the GUI option and ldd shows a link to ssl in the old version) However, using the new ebuild (0.8.7.12), I cannot have SSL support compiled in. I have tried putting USE="ssl" in /etc/make.conf and invoking emerge with export USE="ssl"; emerge gabber No matter what I tried (including removing the || myconf="${myconf} --disable-ssl" line from the ebuild file), I cannot get the latest Gabber to build with SSL support. I am not too experienced with USE flags and how to use them, but discussing this on the #gentoo channel, it seems like this qualifies as a bug. Reproducible: Always Steps to Reproduce: 1. emerge gabber-0.8.7.12.ebuild with USE flags for SSL 2. 3. Actual Results: Gabber installed without error messages. However the resulting binary does not have SSL support and the GUI does not have the SSL option in connection settings. Expected Results: The binary should have been linked to the SSL library and the GUI should have the had the SSL feature. Since this is an upgrade from the previous ebuild, it should have kept the config settings about SSL also (I am not sure if portage can handle such persistent configs) Thank you.
Created attachment 9863 [details] ebuild for ssl Have not tried any other options but ssl
The problem appears to be in the ebuild file. ssl is enabled by default so it doesn't need the --enable-ssl option. I didn't look into it but if this is used this shows up during the build process. Enable OpenSSL support: no If you remove this line from the ebuild it works fine. && myconf="${myconf} --enable-ssl" \ Now when you run emerge look for Enable OpenSSL support: Yes If this is there ssl support will be compiled in This worked for me anyway. I have attached my ebuild that worked for me.
Hi there, it's a bug in the ebuild. gabber doesn't know anything about --enable-ssl. There are two options in the configure script for ssl: --disable-ssl and --with-ssl-path=... (i think so, i don't know the correct option anymore ;)) So, if you emerge gabber, gabber won't find the ssl path (which is for gentoo: /usr) so, what i did is: exchange --enable-ssl with --with-ssl-path=/usr and voila, it worked with ssl. think this must be changed. regards, \sh
well, close but not cigar. it was --with-ssl-dir=/usr, i've just fixed it in the ebuild.
