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/2013-February/023191.html | 72 ++++++++++++++++++++++++++++ 1 file changed, 72 insertions(+) create mode 100644 zarb-ml/mageia-dev/2013-February/023191.html (limited to 'zarb-ml/mageia-dev/2013-February/023191.html') diff --git a/zarb-ml/mageia-dev/2013-February/023191.html b/zarb-ml/mageia-dev/2013-February/023191.html new file mode 100644 index 000000000..394f8dbdb --- /dev/null +++ b/zarb-ml/mageia-dev/2013-February/023191.html @@ -0,0 +1,72 @@ + + + + [Mageia-dev] A question about BuildRequires and other RPM questions. + + + + + + + + + +

[Mageia-dev] A question about BuildRequires and other RPM questions.

+ Dan Fandrich + dan at coneharvesters.com +
+ Thu Feb 28 22:18:53 CET 2013 +

+
+ +
On Thu, Feb 28, 2013 at 03:25:41PM +0100, Guillaume Rousse wrote:
+> Build dependencies are usually specified in installation
+> instructions. For humans, of course. You may also try to parse the
+> outpout of ./configure (or equivalent) script. In both case, there is
+> not garanty then every build dependency will get specified.
+
+The other way is to work backwards by looking at the install dependencies
+that rpmbuild discovered, or the NEEDED lines from objdump -x, and adding the
+-devel versions of those libraries. That won't catch any compile-time-only
+dependencies, though (like libtool, autoconf or flex) but it will give you
+something to start from.  Note also that some programs will automatically
+discover what optional libraries are available at build time and configure
+themselves accordingly. So, if you miss some BuildRequires, you might end up
+with a binary that works but is missing features.
+
+>>> Dan
+
+ + + +
+

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