From: Lisa Seelye <lisa@gentoo.org>
To: kumba@gentoo.org
Cc: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] New Global USE: crossdev
Date: Sat, 10 Jul 2004 16:38:57 -0400 [thread overview]
Message-ID: <1089491936.20191.214.camel@lisa.thedoh.com> (raw)
In-Reply-To: <40EF480F.3070301@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 379 bytes --]
On Fri, 2004-07-09 at 21:36, Kumba wrote:
> Said USE Flag would mostly be applicable to gcc, glibc, and binutils.
> Possibly kernel-headers too, if needed.
>
> Any objections?
Sounds like a good idea. I can see this being used in conjunction with
distcc for crosscompiling somewhere down the line.
--
Regards,
-Lisa
<Quidquid latine dictum sit, altum viditur>
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-07-10 20:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-10 1:36 [gentoo-dev] New Global USE: crossdev Kumba
2004-07-10 20:38 ` Lisa Seelye [this message]
2004-07-10 22:33 ` [gentoo-dev] crossdev, distcc, and multiple toolchains... (was New global USE: crossdev) Jeremy Huddleston
2004-07-11 0:29 ` Mike Frysinger
2004-07-11 1:23 ` [gentoo-dev] crossdev, distcc, and multiple toolchains Lars Weiler
2004-07-11 3:41 ` Kumba
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=1089491936.20191.214.camel@lisa.thedoh.com \
--to=lisa@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=kumba@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