public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ryan Hill <dirtyepic@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: [RFC] toolchain-funcs.eclass: functions to call compiler
Date: Mon, 31 May 2010 20:14:33 -0600	[thread overview]
Message-ID: <20100531201433.4afb5dd3@gentoo.org> (raw)
In-Reply-To: 20100531201122.55f5f674@gentoo.org

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

On Mon, 31 May 2010 20:11:22 -0600
Ryan Hill <dirtyepic@gentoo.org> wrote:

> On Mon, 31 May 2010 21:12:46 +0200
> Michał Górny <gentoo@mgorny.alt.pl> wrote:
> 
> > * media-sound/wavegain - ${LDFLAGS} before ${CFLAGS}, '-o' after sources,
> > 	defines after '-o',
> 
> Just curious why you're pointing out the ordering of options.  As far as I
> know it doesn't matter (except some LDFLAGS where you can go -Wl,--foo
> someblah -Wl,--no-foo otherblah and doesn't really apply here).

Nevermind I missed you explaining this.  Consistency == good.


-- 
fonts,                               there's a hole in my neighbourhood
gcc-porting,                  down which of late i cannot help but fall
wxwidgets @ gentoo     EFFD 380E 047A 4B51 D2BD C64F 8AA8 8346 F9A4 0662

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

  reply	other threads:[~2010-06-01  2:15 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-31 19:12 [gentoo-dev] [RFC] toolchain-funcs.eclass: functions to call compiler Michał Górny
2010-06-01  2:11 ` [gentoo-dev] " Ryan Hill
2010-06-01  2:14   ` Ryan Hill [this message]
2010-06-02  7:16 ` [gentoo-dev] " Mike Frysinger
2010-06-02 13:17   ` Michał Górny
2010-06-02 21:56     ` Mike Frysinger
2010-06-05 13:16       ` Michał Górny
2010-06-06  4:17         ` Mike Frysinger
2010-06-06  7:45           ` Michał Górny
2010-06-08 22:44             ` Mike Frysinger
2010-06-09  5:34               ` Michał Górny
2010-06-09  5:41                 ` Mike Frysinger
2010-06-17  4:17                   ` Jeroen Roovers

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=20100531201433.4afb5dd3@gentoo.org \
    --to=dirtyepic@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