From: Donnie Berkholz <dberkholz@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Dying on some CFLAGS instead of filtering them.
Date: Mon, 10 Jul 2006 14:22:32 -0700 [thread overview]
Message-ID: <44B2C518.7000809@gentoo.org> (raw)
In-Reply-To: <7573e9640607101330q5e9e001aia54bd275b0d0cc9c@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 538 bytes --]
Richard Fish wrote:
> I have to say I dislike allowing this "backdoor" method to set CFLAGS,
> as they won't show up in emerge --info or emerge -pv <pkg>. You'd
> have to see the actual build output to see the nasty flags, which you
> might not even think to ask for if a package builds fine but crashes
> randomly later.
How about `cat /var/db/pkg/$category/$package-$version/CFLAGS`? You
can't rely on emerge --info anyway, because it shows _current_ flags
rather than flags the package was built with.
Thanks,
Donnie
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 252 bytes --]
next prev parent reply other threads:[~2006-07-10 21:26 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-09 21:24 [gentoo-dev] Dying on some CFLAGS instead of filtering them Denis Dupeyron
2006-07-09 21:32 ` Ciaran McCreesh
2006-07-15 11:54 ` Denis Dupeyron
2006-07-15 13:59 ` Ciaran McCreesh
2006-07-09 23:51 ` [gentoo-dev] " Ryan Hill
2006-07-10 12:51 ` Denis Dupeyron
2006-07-11 2:32 ` Ryan Hill
2006-07-15 12:39 ` Denis Dupeyron
2006-07-15 16:33 ` Ryan Hill
2006-07-15 17:38 ` Ryan Hill
2006-07-16 19:55 ` Paul de Vrieze
2006-07-16 20:20 ` Ryan Hill
2006-07-16 19:37 ` Paul de Vrieze
2006-07-10 8:34 ` [gentoo-dev] " Richard Fish
2006-07-10 10:16 ` Ned Ludd
2006-07-10 16:01 ` Richard Fish
2006-07-10 17:08 ` Zac Medico
2006-07-10 20:30 ` Richard Fish
2006-07-10 20:42 ` Simon Stelling
2006-07-10 21:01 ` Richard Fish
2006-07-10 21:22 ` Donnie Berkholz [this message]
2006-07-10 12:25 ` [gentoo-dev] " Duncan
2006-07-10 13:20 ` [gentoo-dev] " Patrick McLean
2006-07-16 20:08 ` Paul de Vrieze
2006-07-10 14:42 ` Ciaran McCreesh
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=44B2C518.7000809@gentoo.org \
--to=dberkholz@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