public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Jon Portnoy <avenj@gentoo.org>
To: donnie berkholz <spyderous@gentoo.org>
Cc: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] 'Distro Day (Measuring the benefits of the Gentoo approach)'
Date: Wed, 13 Aug 2003 21:13:45 -0400	[thread overview]
Message-ID: <20030814011345.GA25275@cerberus.oppresses.us> (raw)
In-Reply-To: <34297.172.130.207.3.1060823240.squirrel@spidermail.richmond.edu>

On Wed, Aug 13, 2003 at 08:07:20PM -0500, donnie berkholz wrote:
> On Wednesday 13 August 2003 15:02, Mike Frysinger wrote:
> > On Wednesday 13 August 2003 15:00, Jon Portnoy wrote:
> >> At the moment Zadeh and einride are working on ICC integration.
> >> einride has some excellent ideas about Portage integration, so
> >> hopefully that'll get us somewhere.
> >
> > hopefully the idea isnt icc-centric ... that is, it'll support say
> > uclibc  compiler, or dietlibc, or tcc, or what have you :)
> > -mike
> 
> Perhaps gcc-config should be expanded to toolchain-config ...
> 

In the past the plan has been to move gcc-config to cc-config and modify 
it to support other compilers.

einride had some thoughts about Portage modifications instead, but I 
haven't really been keeping up with what's going on there.

-- 
Jon Portnoy
avenj/irc.freenode.net

--
gentoo-dev@gentoo.org mailing list


  reply	other threads:[~2003-08-14  1:13 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-13 13:38 [gentoo-dev] "Distro Day (Measuring the benefits of the Gentoo approach)" Philippe Lafoucrière
2003-08-13 14:07 ` brett holcomb
2003-08-13 15:03   ` Sven Vermeulen
2003-08-13 16:15     ` Alan
2003-08-13 20:30       ` Chris Gianelloni
2003-08-13 14:08 ` Chris Gianelloni
2003-08-13 14:12   ` Brad Laue
2003-08-13 14:20   ` Philippe Lafoucrière
2003-08-13 14:25     ` Philippe Lafoucrière
2003-08-13 14:32     ` Chris Gianelloni
2003-08-13 16:17       ` Alan
2003-08-13 16:22         ` Patrick Kursawe
2003-08-13 20:35           ` Chris Gianelloni
2003-08-13 20:32         ` Chris Gianelloni
2003-08-14 10:02           ` Paul de Vrieze
2003-08-13 21:15     ` FRLinux
2003-08-13 22:49       ` William Kenworthy
2003-08-14  2:04         ` Brian Jackson
2003-08-14 10:10         ` Paul de Vrieze
2003-08-14 12:30         ` Chris Gianelloni
2003-08-14 16:59           ` William Kenworthy
2003-08-14 17:38             ` [gentoo-dev] "Distro Day (Measuring the benefits of the Gentooapproach)" matt c
2003-08-14 19:22         ` [gentoo-dev] "Distro Day (Measuring the benefits of the Gentoo approach)" FRLinux
2003-08-14 23:01           ` William Kenworthy
2003-08-13 14:24 ` David Holm
2003-08-13 14:28   ` Philippe Lafoucrière
2003-08-13 16:16     ` Eric Olinger
2003-08-13 19:00   ` Jon Portnoy
2003-08-13 20:02     ` Mike Frysinger
2003-08-14  1:07       ` [gentoo-dev] 'Distro Day (Measuring the benefits of the Gentoo approach)' donnie berkholz
2003-08-14  1:13         ` Jon Portnoy [this message]
2003-08-14 11:01         ` Chris Gianelloni
2003-08-13 14:34 ` [gentoo-dev] "Distro Day (Measuring the benefits of the Gentoo approach)" Stuart Herbert
2003-08-13 14:34 ` Svyatogor
2003-08-13 17:46 ` Adam Porich

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=20030814011345.GA25275@cerberus.oppresses.us \
    --to=avenj@gentoo.org \
    --cc=gentoo-dev@gentoo.org \
    --cc=spyderous@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