severity 340942 important
thanks
On Mon, Nov 28, 2005 at 06:35:15PM -0800, Isaac Jones wrote:
David Roundy [EMAIL PROTECTED] writes:
(snip)
... It would help to have the config.log.
Most likely the curl-config output is messed up in some way. We use
curl-config to determine which flags to use to link with curl, but then we
check whether these flags actually work, and it is this check that fails.
So either curl-config is messed up (as it used to be on MacOS--it claimed
to be x86) or our test is misfunctioning in some way. It could be that our
workaround for the bug in curl-config on MacOS is somehow backfiring on
another platform... :(
Yes, curl-config is messed up in the sense that curl-config is *always*
messed up for purposes of dynamic linking on GNU systems. In the present
case, curl-config spits out -lkrb5 and other library options, but is missing
a dependency on libkrb5-dev. This is bug #340784, and should be fixed
reasonably soon.
On the darcs side, this is fixable by changing the Debian package to not use
curl-config -- as described at
http://lists.debian.org/debian-devel-announce/2005/11/msg00016.html. It's
understandable that upstream would not want to accept such a patch, since
it's not portable to platforms which use non-GNU linkers; but for Debian's
purposes, until curl-config adds a --static option to split these other
garbage linker options out, it's far better to replace `curl-config --libs`
with -lcurl as this is much less likely to lead to future build failures as
a result of curl bugs.
Cheers,
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
[EMAIL PROTECTED] http://www.debian.org/
signature.asc
Description: Digital signature
