when emerging libmilter with LDFLAGS="-Wl,--as-needed" it isn't recognized by clamav during configure-stage thus letting clamav fail
hope I set up the dependency correctly, sorry for any inconvenience thanks :)
Please attach the config.log from such failure.
Created attachment 151809 [details] output of emerge-log (app-antivirus:clamav) & failure
I think this blocks the tracker, rather than depends on the tracker being fixed. I've updated it accordingly... 5:)
:D that was what I originally had intended to do ! Thanks ;)
Can you post the generated config.log file? It's probably a problem with libmilter, which affects clamav, rather than a problem with clamav.
will do within the next days... I just found out that "only" clamav is affected: if I try to compile clamav with as-needed set it fails, if as-needed was set on libmilter only & is filtered out / omitted with clamav, clamav compiles & works fine
Created attachment 161173 [details] /var/tmp/portage/app-antivirus/clamav-0.93.3/work/clamav-0.93.3/config.log I also hit the same problem. Attached config.log.
any news on this one? A config.log file is posted.
Created attachment 166319 [details, diff] Applied against configure.in, lets clamav build support for libmilter with --as-needed I figured out how to get this to compile on my machine, since this problem has bugged me 2 or three times in the last year. The problem is that when configure tests whether or not libmilter can be "lunk" to, the libraries are passed to GCC in the wrong order. This is because configure uses LDFLAGS rather than LIBS to pass the libs to gcc. This patch sets the libs libmilter needs to the LIBS variable rather than the LDFLAGS variable and causes clamav to compile with LDFLAGS="-Wl,--as-needed" and with libmilter on my machine.
(In reply to comment #9) > any news on this one? A config.log file is posted. > If this is news, I posted the same patch I attached to this bug to ClamAV's bugzilla. According to the bug as of today, I think the next bugfix release of 0.94.1 will be fixed. https://wwws.clamav.net/bugzilla/show_bug.cgi?id=1204
Maybe this bug should depend on bug #245450, because app-antivirus/clamav-0.94.1 supports --as-needed.
app-antivirus/clamav-0.94.1 is now in the Portage tree and stable by bug #245450. app-antivirus/clamav-0.94.2 also is in the tree, by bug #248798. These versions of clamav compile fine with LDFLAGS="-Wl,--as-needed" and USE="milter". Thus, I think this bug's Status should be FIXED. Please mark it as such.
(In reply to comment #13) > Thus, I think this bug's Status should be FIXED. Please mark it as such. Just doing so. Thanks for testing & reporting back!
sorry for resurrecting this bug but it appeared again with 0.95.2: configure: error: Cannot find libmilter !!! Please attach the following file when seeking support: !!! /var/tmp/portage/app-antivirus/clamav-0.95.2/work/clamav-0.95.2/config.log * * ERROR: app-antivirus/clamav-0.95.2 failed. [U] app-antivirus/clamav Available versions: 0.95.1!t 0.95.2!t {bzip2 clamdtop crypt iconv ipv6 milter selinux} Installed versions: 0.95.1!t(17:15:21 04/10/09)(bzip2 crypt iconv ipv6 milter -clamdtop -selinux) Homepage: http://www.clamav.net/ Description: Clam Anti-Virus Scanner libmilter: mail-filter/libmilter-8.14.3 afaik 0.95.1 emerged fine with as-needed ...
(In reply to comment #15) > sorry for resurrecting this bug but it appeared again with 0.95.2: I have 0.95.2 installed, I think I use LDFLAGS="-Wl,--as-needed", and it seems to work fine for me. However, I don't force --as-needed in my specfile... do you? > > configure: error: Cannot find libmilter > > !!! Please attach the following file when seeking support: > !!! /var/tmp/portage/app-antivirus/clamav-0.95.2/work/clamav-0.95.2/config.log May you please attach this file? This reveals what part of that configure test failed. It hopefully tells why it failed (or why --as-needed caused that test to fail).
(In reply to comment #15) > sorry for resurrecting this bug New version, new bug. Do *not* do this; the bug will have dozens of comments that would now be stale, as well as attachments that would now be stale. The bug in 0.94 was fixed. Open a new bug.
