From 1be510f9529cb082f802408b472a77d074b394c0 Mon Sep 17 00:00:00 2001 From: Nicolas Vigier Date: Sun, 14 Apr 2013 13:46:12 +0000 Subject: Add zarb MLs html archives --- zarb-ml/mageia-dev/2012-December/020765.html | 93 ++++++++++++++++++++++++++++ 1 file changed, 93 insertions(+) create mode 100644 zarb-ml/mageia-dev/2012-December/020765.html (limited to 'zarb-ml/mageia-dev/2012-December/020765.html') diff --git a/zarb-ml/mageia-dev/2012-December/020765.html b/zarb-ml/mageia-dev/2012-December/020765.html new file mode 100644 index 000000000..63b40608e --- /dev/null +++ b/zarb-ml/mageia-dev/2012-December/020765.html @@ -0,0 +1,93 @@ + + + + [Mageia-dev] python-curl build fail in cauldron + + + + + + + + + +

[Mageia-dev] python-curl build fail in cauldron

+ Colin Guthrie + mageia at colin.guthr.ie +
+ Wed Dec 12 17:31:54 CET 2012 +

+
+ +
'Twas brillig, and Dan Fandrich at 12/12/12 14:17 did gyre and gimble:
+>> can someone have a look at python-curl build fail in cauldron ?
+> 
+> Looks like a missing a -lcrypto in the link line, likely due to that
+> being an implied dependency through libcurl.  Without looking at the
+> source, it might be as easy to fix as setting env LIBS=-lcrypto on the
+> compile line.
+
+Of course if that is the problem, then a proper patch to it's build
+system (autotools, cmake or whatever is used) and submitting the fix
+upstream is the "correct" course of action :)
+
+Sometimes this happens due to "overlinking" which is often used tho'
+many distros (like us) in recent years have been trying to be more
+strict about this stuff in our build systems.
+
+Col
+
+-- 
+
+Colin Guthrie
+colin(at)mageia.org
+http://colin.guthr.ie/
+
+Day Job:
+  Tribalogic Limited http://www.tribalogic.net/
+Open Source:
+  Mageia Contributor http://www.mageia.org/
+  PulseAudio Hacker http://www.pulseaudio.org/
+  Trac Hacker http://trac.edgewall.org/
+
+ + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ -- cgit v1.2.1