From: James Broadhead <jamesbroadhead@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Calls compiler directly, and strange parameters passed. Is this a bug?
Date: Mon, 31 Oct 2011 09:40:46 +0000 [thread overview]
Message-ID: <CA+hid6HFwtUi11gUSUOv=H9yDHjb6YphzbpJMSOP5TpUgD-+Fw@mail.gmail.com> (raw)
In-Reply-To: <CA+czFiBou9y9myfQxp9B9+B7MOs8AWkz8nNKUBCQa5zgsdxu_w@mail.gmail.com>
On 29 October 2011 01:03, Michael Mol <mikemol@gmail.com> wrote:
> Is this incorrect? Does it qualify as a bug?
Yes. The ebuild should respect your CFLAGS unless there is a USE flag
to enable/disable them. The counter to this is when a package won't
build without specific flags, then disregarding the user is okay.
Since this is over-optimising (rather than under-), this probably
isn't the case.
File a minor bug, and if you're super-interested, please take a look
at ebuild writing. I get the feeling that maintaining calibre is a bit
messy, I'm sure that they'd appreciate the help.
prev parent reply other threads:[~2011-10-31 9:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-29 0:03 [gentoo-user] Calls compiler directly, and strange parameters passed. Is this a bug? Michael Mol
2011-10-31 9:40 ` James Broadhead [this message]
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='CA+hid6HFwtUi11gUSUOv=H9yDHjb6YphzbpJMSOP5TpUgD-+Fw@mail.gmail.com' \
--to=jamesbroadhead@gmail.com \
--cc=gentoo-user@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