public inbox for gentoo-hardened@lists.gentoo.org
 help / color / mirror / Atom feed
From: "René Rhéaume" <rene.rheaume@gmail.com>
To: gentoo-hardened@lists.gentoo.org
Subject: Re: [gentoo-hardened] removing .text relocations from mplayer and xine-lib
Date: Sat, 4 Jun 2005 11:31:18 -0400	[thread overview]
Message-ID: <35572ca80506040831d2ea8bb@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0506021435290.4678-100000@lnx.bridge.intra>

> Better yet, add --enable-fpic to econf. The change proposed above w/ the
> link is allowed conditionally, if use has_pic && use x86 (probably amd64
> too)
Yes, --enable-fpic worked.

> xineplug_decode_ff.so is clean as of 1.0.1, I remove the rest from the
> system, else xine-lib fails to load (see original bug-report, failure on
> planar)
Which revision? I based my ebuild on 1.0.1-r1 and I have never been
able to suppress text relocations from xineplug_decode_ff.so. Grr, the
Xine team remade the ffmpeg build system from scratch using the GNU
autotools. Also, when I looked up for 'planar' in Gentoo Bugzilla, I
got the famous 'Zarro boogs found' message.

But why xineplug_decode_w32dll.so is built even when win32codecs is
not in USE? Looks like a build system bug to be resolved upstream.

-- 
gentoo-hardened@gentoo.org mailing list


  reply	other threads:[~2005-06-04 15:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-29 15:27 [gentoo-hardened] removing .text relocations from mplayer and xine-lib René Rhéaume
2005-05-29 17:24 ` Ned Ludd
2005-05-30 16:49   ` René Rhéaume
2005-06-02 12:42     ` Peter S. Mazinger
2005-06-04 15:31       ` René Rhéaume [this message]
2005-06-09 12:43         ` Peter S. Mazinger

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=35572ca80506040831d2ea8bb@mail.gmail.com \
    --to=rene.rheaume@gmail.com \
    --cc=gentoo-hardened@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox