public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] The dreaded debug use flag/eclass
Date: Tue, 2 Aug 2005 09:22:37 -0400	[thread overview]
Message-ID: <200508020922.37442.vapier@gentoo.org> (raw)
In-Reply-To: <42EEDDCD.4020209@gentoo.org>

On Monday 01 August 2005 10:43 pm, Danny van Dyk wrote:
> Mike Frysinger schrieb:
> |>your USE=pic example is wrong, it does not change CFLAGS (and if your
> |>package does, it is broken)
>
> chillispot at least is not wrong. If USE="pic" is set, it compiles _only
> with_ -fPIC, ommiting to compile files twice and effectivly telling
> libtool not to produce a normal static library.

just to review ... `use_with pic` should never be used because if you dont 
have 'pic' in your USE flags, the ebuild will run `./configure 
--without-pic` ... that means libtool will try to produce shared and static 
libraries with object files which were built without PIC ... on many arches 
(like amd64), the linker will abort

btw, where do you get this information ?  my tests show that libtool still 
compiles all files twice even though --with-pic was used ...
-mike
-- 
gentoo-dev@gentoo.org mailing list



  parent reply	other threads:[~2005-08-02 15:03 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-02  1:22 [gentoo-dev] The dreaded debug use flag/eclass Alec Warner
2005-08-02  2:07 ` Mike Frysinger
2005-08-02  2:26   ` Mike Frysinger
2005-08-02  2:43     ` Danny van Dyk
2005-08-02  2:52       ` Mike Frysinger
2005-08-02 11:10         ` Danny van Dyk
2005-08-02 13:22       ` Mike Frysinger [this message]
2005-08-03 11:16         ` Martin Schlemmer
2005-08-03 12:50           ` Mike Frysinger
2005-08-03 13:11             ` Danny van Dyk
2005-08-24 11:13               ` Paul de Vrieze
2005-08-02 15:38   ` Alec Warner

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=200508020922.37442.vapier@gentoo.org \
    --to=vapier@gentoo.org \
    --cc=gentoo-dev@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