From: Tomasz Mloduchowski <mlodutb@MIT.EDU>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] rm `which gcc` && emerge -e world
Date: Fri, 21 Oct 2005 23:12:33 -0400 [thread overview]
Message-ID: <1129950753.4942.15.camel@TSUNAMI.MIT.EDU> (raw)
[-- Attachment #1: Type: text/plain, Size: 771 bytes --]
Now, that I've got your attention. IMHO above should NOT fail - most of
the software in portage is already using ${HOST}-gcc instead and gcc
symlink is just a convenience.
But it does. In packages I will never suspect being nasty (qt, lynx) and
ones I would, but they shouldn't (fuse)
What is so important in that feature? Crosscompilation and distcc.
For example, I have alpha-unknown-linux-gnu running as a distcc server
for x86 box. And, it does not work for those packages.
I got sick of filling 3 almost identical bug reports
110040, 110086 and 110087 and I'm not even at half of emerge -uD world.
So, if you agree that it IS a problem, do the `rm` and run ebuilds you
maintain. You will save me another 10 or so unnended bugreports.
Tomasz
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2005-10-22 3:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-22 3:12 Tomasz Mloduchowski [this message]
2005-10-22 4:48 ` [gentoo-dev] rm `which gcc` && emerge -e world Mike Frysinger
2005-10-22 14:02 ` Tomasz Mloduchowski
2005-10-22 14:21 ` Diego 'Flameeyes' Pettenò
2005-10-22 19:06 ` Mike Frysinger
2005-10-22 19:11 ` Stephen P. Becker
2005-10-22 19:15 ` Mike Frysinger
2005-10-22 12:17 ` Stephen P. Becker
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=1129950753.4942.15.camel@TSUNAMI.MIT.EDU \
--to=mlodutb@mit.edu \
--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