Created attachment 400194 [details] Build log When topal use flag is enabled then this bug shows up.
Created attachment 400196 [details] emerge --info
Created attachment 400198 [details] emerge -pqv
Created attachment 408282 [details, diff] Diff that fixes existing files/2.00-c-client.patch I hit the same problem with: undefined reference to 'crypt'... 'topal' use flag is a red herring and isn't relevant: [ebuild N ] mail-client/alpine-2.00-r5 USE="ipv6 nls ssl -chappa -doc -kerberos -ldap -onlyalpine -passfile -smime -spell -threads -topal" The 'hammer' fix ended up having to modify files/2.00-c-client.patch as the position of -lcrypt is important when linking against -lc-client... I have attached the patch, and even though it allows for a successful emerge, take it as a POC fix... -- FutureQuest, Inc. Terra
The last two comments on bug #456928 suggest that this is due to net-libs/c-client being underlinked.
I just dug into this over on the PHP bug. I think c-client should always pass -lcrypt on Linux... here's my comment from over there: When building net-libs/c-client, there are a number of different "targets" listed in its Makefile. The one we wind up using is "lnx": if use kernel_linux ; then use pam && target=lnp passwdtype=pam || target=lnx passwdtype=std However, "lnx" is... lnx: # Linux non-shadow passwords and that's clearly not us. In the "lnx" target, "-lcrypt" does not get appended to LDFLAGS. This looks a lot more promising: slx: # Secure Linux ... BASELDFLAGS="-lcrypt" I would suggest that net-mail@ change "lnx" to "slx" in the c-client ebuild. That should add "-lcrypt" to LDFLAGS and fix the issue.
I thought this was the same problem I had in PHP over in bug #456928. However, I was unable to reproduce the failure with the current version of alpine, and the old versions no longer build (I've since removed them). I did ultimately commit a new revision of c-client to fix the PHP thing. Can one of the reporters please test the latest net-libs/c-client-2007f-r6 to see if you still experience this build failure? If the problem persists for you, I'll dig into it. Otherwise, it may have been fixed in one of those intermediate revisions.
(In reply to Michael Orlitzky from comment #6) > > Can one of the reporters please test the latest net-libs/c-client-2007f-r6 > to see if you still experience this build failure? If the problem persists > for you, I'll dig into it. Otherwise, it may have been fixed in one of those > intermediate revisions. Ping.. if we don't hear a failure report after a few months, I think it makes sense to close this as NEEDINFO or similar.
The problem was caused when the topal USE flag was set on the alpine package, that USE flag no longer exists on the package. I have successfully built the latest stable alpine and c-client packages. USE == c-client chappa doc ipv6 kerberos ssl static-libs topal alpine chappa doc ipv6 kerberos smime spell ssl threads If this is indeed the configuration needed that would ordinarily cause the failure then this bug can be closed. Thanks
Thanks for the update. The comment #3 suggested that maybe USE=topal wasn't necessary, but I wasn't able to reproduce the failure without USE=topal, and none of the versions with the USE flag would compile any longer. I'll leave this open for a few more days and then close it if I don't hear any bad news. Worst case, someone will file a new bug if there's another underlinking issue lurking in c-client.
I'm not sure if this is FIXED or OBSOLETE.. I guess you could say I... NEEDINFO?