From: Chris Gianelloni <wolf31o2@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Why arch-specific make.conf files?
Date: Tue, 15 Nov 2005 16:01:07 -0500 [thread overview]
Message-ID: <1132088467.9703.52.camel@cgianelloni.nuvox.net> (raw)
In-Reply-To: <20051115200112.GG22083@toucan.gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1000 bytes --]
On Tue, 2005-11-15 at 20:01 +0000, Mike Frysinger wrote:
> On Tue, Nov 15, 2005 at 02:52:28PM -0500, Chris Gianelloni wrote:
> > On Tue, 2005-11-15 at 20:19 +0100, Marius Mauch wrote:
> > > Was just about to finally commit the elog related config stuff into
> > > make.conf just to notice (again) that there are 14 (in words: fourteen)
> > > different make.conf files there, with almost all of them just differing
> > > in CFLAGS and CHOST (only exception is make.conf.mac which isn't used
> > > anymore in any way AFAICT).
> >
> > Where are these files that you're even talking about?
>
> before catalyst started nuking make.conf, they were the standard
> /etc/make.conf files ... now though, you can find them at
> /etc/make.conf.example
Ahh... and there's different ones installed based on some criteria,
rather than a single example? Now it makes sense.
--
Chris Gianelloni
Release Engineering - Strategic Lead
x86 Architecture Team
Games - Developer
Gentoo Linux
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-11-15 21:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-15 19:19 [gentoo-dev] Why arch-specific make.conf files? Marius Mauch
2005-11-15 19:26 ` Diego 'Flameeyes' Pettenò
2005-11-15 19:54 ` Chris Gianelloni
2005-11-16 2:30 ` Marius Mauch
2005-11-16 12:50 ` Chris Gianelloni
2005-11-16 15:04 ` Marius Mauch
2005-11-16 17:47 ` [gentoo-dev] " Duncan
2005-11-15 19:52 ` [gentoo-dev] " Chris Gianelloni
2005-11-15 20:01 ` Mike Frysinger
2005-11-15 21:01 ` Chris Gianelloni [this message]
2005-11-15 21:12 ` Mike Frysinger
2005-11-16 2:40 ` Marius Mauch
2005-11-15 19:55 ` Chris Gianelloni
2005-11-16 17:18 ` Gustavo Zacarias
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=1132088467.9703.52.camel@cgianelloni.nuvox.net \
--to=wolf31o2@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