summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-dev/2013-March/023367.html
diff options
context:
space:
mode:
Diffstat (limited to 'zarb-ml/mageia-dev/2013-March/023367.html')
-rw-r--r--zarb-ml/mageia-dev/2013-March/023367.html125
1 files changed, 125 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2013-March/023367.html b/zarb-ml/mageia-dev/2013-March/023367.html
new file mode 100644
index 000000000..2f1744abb
--- /dev/null
+++ b/zarb-ml/mageia-dev/2013-March/023367.html
@@ -0,0 +1,125 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
+<HTML>
+ <HEAD>
+ <TITLE> [Mageia-dev] A question about BuildRequires and other RPM questions.
+ </TITLE>
+ <LINK REL="Index" HREF="index.html" >
+ <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20A%20question%20about%20BuildRequires%20and%20other%20RPM%0A%09questions.&In-Reply-To=%3C5139C8EB.3030900%40apostrophe.co.uk%3E">
+ <META NAME="robots" CONTENT="index,nofollow">
+ <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
+ <LINK REL="Previous" HREF="024021.html">
+ <LINK REL="Next" HREF="023368.html">
+ </HEAD>
+ <BODY BGCOLOR="#ffffff">
+ <H1>[Mageia-dev] A question about BuildRequires and other RPM questions.</H1>
+ <B>Robert Wood</B>
+ <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20A%20question%20about%20BuildRequires%20and%20other%20RPM%0A%09questions.&In-Reply-To=%3C5139C8EB.3030900%40apostrophe.co.uk%3E"
+ TITLE="[Mageia-dev] A question about BuildRequires and other RPM questions.">robert.wood at apostrophe.co.uk
+ </A><BR>
+ <I>Fri Mar 8 12:18:03 CET 2013</I>
+ <P><UL>
+ <LI>Previous message: <A HREF="024021.html">[Mageia-dev] [changelog] [RPM] cauldron core/release libvirt-1.0.2-4.mga3
+</A></li>
+ <LI>Next message: <A HREF="023368.html">[Mageia-dev] A question about BuildRequires and other RPM questions.
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#23367">[ date ]</a>
+ <a href="thread.html#23367">[ thread ]</a>
+ <a href="subject.html#23367">[ subject ]</a>
+ <a href="author.html#23367">[ author ]</a>
+ </LI>
+ </UL>
+ <HR>
+<!--beginarticle-->
+<PRE>Even as a programmer/electronics engineer (admittedly down at an
+embedded level most of the time) some of this is going so far over my
+head, it's a vapour trail in the sky.
+
+There are far too many acronyms of stuff I've not come across, for me to
+even get the vaguest grasp of what's been talked about.
+
+I'm not sure what the answer is really, I thought maybe a you tube
+tutorial might be a good idea, but even then, how do you know what level
+to talk down to.
+
+No idea, for example. what iurt, mock are or do; how to make a minimal
+install and keep making the system go back to minimal install when
+creating the next RPM; what a btrfs subvolume is and other things.
+
+I still don't get this whole trial and error thing. It seems that you
+might submit something to the repositories that someone finds doesn't
+install because of a missing dependency and you redo it. Then you can
+retry that for up to five goes before it finally works? That seems
+crazy. I must have misunderstood.
+
+I have no problem learning stuff, I do it every single day in my work
+and it's what makes it so enjoyable, but maybe I need to take smaller
+steps first? No idea where to start or how to go about doing that
+though. As I might not have any work in a week's time it would
+potentially be an ideal time to learn, but maybe I'm just not the right
+person to do this?
+
+
+
+On 28/02/13 21:18, Dan Fandrich wrote:
+&gt;<i> On Thu, Feb 28, 2013 at 03:25:41PM +0100, Guillaume Rousse wrote:
+</I>&gt;&gt;<i> Build dependencies are usually specified in installation
+</I>&gt;&gt;<i> instructions. For humans, of course. You may also try to parse the
+</I>&gt;&gt;<i> outpout of ./configure (or equivalent) script. In both case, there is
+</I>&gt;&gt;<i> not garanty then every build dependency will get specified.
+</I>&gt;<i>
+</I>&gt;<i> The other way is to work backwards by looking at the install dependencies
+</I>&gt;<i> that rpmbuild discovered, or the NEEDED lines from objdump -x, and adding the
+</I>&gt;<i> -devel versions of those libraries. That won't catch any compile-time-only
+</I>&gt;<i> dependencies, though (like libtool, autoconf or flex) but it will give you
+</I>&gt;<i> something to start from. Note also that some programs will automatically
+</I>&gt;<i> discover what optional libraries are available at build time and configure
+</I>&gt;<i> themselves accordingly. So, if you miss some BuildRequires, you might end up
+</I>&gt;<i> with a binary that works but is missing features.
+</I>&gt;<i>
+</I>&gt;&gt;&gt;&gt;<i> Dan
+</I>&gt;<i>
+</I></PRE>
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+<!--endarticle-->
+ <HR>
+ <P><UL>
+ <!--threads-->
+ <LI>Previous message: <A HREF="024021.html">[Mageia-dev] [changelog] [RPM] cauldron core/release libvirt-1.0.2-4.mga3
+</A></li>
+ <LI>Next message: <A HREF="023368.html">[Mageia-dev] A question about BuildRequires and other RPM questions.
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#23367">[ date ]</a>
+ <a href="thread.html#23367">[ thread ]</a>
+ <a href="subject.html#23367">[ subject ]</a>
+ <a href="author.html#23367">[ author ]</a>
+ </LI>
+ </UL>
+
+<hr>
+<a href="https://www.mageia.org/mailman/listinfo/mageia-dev">More information about the Mageia-dev
+mailing list</a><br>
+</body></html>