Bug 99160 – c-ares-1.2.1-r1 amd64 keyword request: was: c-ares-1.2.1-r1.ebuild (Update) Build as shared library

• Product: Gentoo Linux
• Status: RESOLVED FIXED

[Description Tupone Alfredo 2005-07-15 15:54:25 UTC]

c-ares need --enable-shared as a configure option to build as a shared library.
Doing that, will allow the build of libcurl with the "use ares" option, even in amd64 architecture.
So, if that is applied, could you modify the curl ebuild too, so to enable ares even on amd64?

[Comment 1 Tupone Alfredo 2005-07-15 15:55:53 UTC]

Created attachment 63493 [details]
c-ares-1.2.1-r1.ebuild

[Comment 2 Daniel Black (RETIRED) 2005-07-16 16:47:00 UTC]

Tupone - thanks 
 
amd64 peoples - ekeyword request as per Tupone 
 
liquidx - are you interested in updating curl to use this? 

[Comment 3 Tupone Alfredo 2005-08-02 08:18:58 UTC]

I would like to have ~amd64 in c-ares, and curl c-ares enable on the amd64
architecture.
We, I'm one of the bzflag (http://www.bzflag.org) developer, use these library
to work correctly.
As gentoo is my primary OS, and one of my station is an amd64, I would like to
apply next bzflag version (not out yet) for x86 and amd64.

If you, before adding the ~amd64 keyword, are waiting for more test that I can
do,  I'm glad to help.

[Comment 4 Richard Freeman 2005-08-02 18:39:23 UTC]

Tested successfully both c-ares-1.2.1-r1 and curl-7.14.0 with USE=ares -ipv6
(after removing x86 checks from the ebuild) on mostly-stable amd64.  Recommend
keywording ~amd64 and making a new curl ebuild which removes x86 checks
(possibly with a dependancy on the 1.2.1-r1 if it breaks with earlier version -
I didn't test this but I assume that this was the purpose of the 1.2.1-r1 patch).

Tested curl on a few URLs (both text and binary) both with and without a proxy.
 Seems to work great.  Verified linked against libcares via ldd.  I can't see
anything else obvious to test.

Keywording TESTED.