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-January/021410.html | 115 ++++++++++++++++++++++++++++ 1 file changed, 115 insertions(+) create mode 100644 zarb-ml/mageia-dev/2013-January/021410.html (limited to 'zarb-ml/mageia-dev/2013-January/021410.html') diff --git a/zarb-ml/mageia-dev/2013-January/021410.html b/zarb-ml/mageia-dev/2013-January/021410.html new file mode 100644 index 000000000..cc3cb4f14 --- /dev/null +++ b/zarb-ml/mageia-dev/2013-January/021410.html @@ -0,0 +1,115 @@ + + + + [Mageia-dev] rpmrc [5221] build with -fPIC on x86_64 too (pok, mdv) + + + + + + + + + +

[Mageia-dev] rpmrc [5221] build with -fPIC on x86_64 too (pok, mdv)

+ EatDirt + dirteat at gmail.com +
+ Thu Jan 10 10:44:49 CET 2013 +

+
+ +
On 10/01/13 02:54, Anssi Hannula wrote:
+
+>
+> I have to strongly disagree with this.
+>
+> - This hides problems in build scripts. Shared libraries should normally
+>    be linked with -fPIC on *all* architectures. Not doing this causes
+>    some issues, like the library to actually become unshareable across
+>    different processes. Since these are allowed in iX86 but not on
+>    x86_64, building all objects on x86_64 with -fPIC will hide any
+>    "missing -fPIC from build script" issues.
+>    Note that there can't be very many problematic failing packages, since
+>    we and mdv have managed this far without it.
+>
+> - It is not needed except on shared libraries, and will cause a small
+>    performance penalty (due to one less register being available when
+>    using relative addressing). (AFAIU it is negligible, but still..)
+
++1
+
+That's killing flies with a steamroller.
+
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+

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