public inbox for gentoo-amd64@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Conway S. Smith" <beolach@comcast.net>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64]  Re: -fPIC - Toolchain broken?
Date: Thu, 19 Oct 2006 07:11:20 -0600	[thread overview]
Message-ID: <20061019071120.4dbd295b@mandalor.homelinux.net> (raw)
In-Reply-To: <45374B67.6010901@getdesigned.at>

[-- Attachment #1: Type: text/plain, Size: 888 bytes --]

On Thu, 19 Oct 2006 11:54:47 +0200
Sebastian Redl <sebastian.redl@getdesigned.at> wrote:
<snip>
> Speaking of which, is there any way to configure flags per package?
> Something like /etc/portage/package.flags, where I can configure
> CFLAGS, CXXFLAGS and LDFLAGS?
> 

Yes, you can use /etc/portage/env/<category>/<package>[-<version>]; for
example, I have a /etc/portage/env/app-admin/logrotate-3.7.2 file,
without -combine in the C[XX]FLAGS, as it won't compile with -combine &
I have -combine in make.conf.  I could instead have
/etc/portage/env/app-admin/logrotate, but if a future version of
logrotate worked w/ -combine, it wouldn't use it unless I removed or
edited /etc/portage/env/app-admin/logrotate.  Also note that any CFLAGS
or CXXFLAGS set in these files completely replace those in make.conf,
they are not added to those in make.conf.


Conway S. Smith

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2006-10-19 13:13 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-18 15:08 [gentoo-amd64] -fPIC - Toolchain broken? Sebastian Redl
2006-10-18 15:28 ` Hemmann, Volker Armin
2006-10-18 15:53 ` Simon Stelling
2006-10-18 16:08   ` Simon Stelling
2006-10-18 17:41   ` Sebastian Redl
2006-10-18 18:32     ` Simon Stelling
2006-10-18 21:21 ` [gentoo-amd64] " Duncan
2006-10-19  9:54   ` Sebastian Redl
2006-10-19 13:11     ` Conway S. Smith [this message]
2006-10-19 15:42       ` Simon Stelling
2006-10-19 20:43         ` Duncan
2006-10-20  9:10           ` Simon Stelling
2006-10-23 14:20           ` Kevin F. Quinn
2006-10-23 15:22             ` Duncan
2006-10-19 20:33     ` Duncan

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=20061019071120.4dbd295b@mandalor.homelinux.net \
    --to=beolach@comcast.net \
    --cc=gentoo-amd64@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