public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Duncan" <1i5t5.duncan@cox.net>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev]  Re: mulltiib cruft: /emul
Date: Tue, 22 Aug 2006 15:17:34 +0000 (UTC)	[thread overview]
Message-ID: <ecf76e$1hm$3@sea.gmane.org> (raw)
In-Reply-To: 44EA17DE.6050503@gentoo.org

Donnie Berkholz <dberkholz@gentoo.org> posted 44EA17DE.6050503@gentoo.org,
excerpted below, on  Mon, 21 Aug 2006 13:30:22 -0700:

> Herbie Hopkins wrote:
>> I'm not sure why /emul was originally chosen though it's a choice I've
>> just gone along with whilst maintaining these packages. I've always
>> viewed the emul libs as a temporary measure until we had full multilib
>> fuctionality in portage. Afaik the only person working on this was
>> eradicator who has been mia for a while now so I'm unsure weather this
>> is ever likely to arise. 
> 
> blubb was working on this but ran out of time for it or something, he 
> wrote a proto-GLEP that I've got lying around.  I'm thinking of seeing 
> what I can do because the current situation really annoys me, even 
> though I don't have a multilib box.

FWIW, eradicator active once again.
eselect-compiler: http://bugs.gentoo.org/show_bug.cgi?id=143697

BTW @ jakob and antarus re comment #18, 21: While I understand and don't
disagree with toolchain's eselect-compiler masking, for some of us on
amd64 and already used to dealing with its quirks, eselect-compiler is
less the "broken thing" than gcc-config-1* was.  After all, there'd have
never been a need for eselect-compiler if gcc-config wasn't broken re dual
bitness in the first place.

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman

-- 
gentoo-dev@gentoo.org mailing list



  reply	other threads:[~2006-08-22 15:24 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-08 15:43 [gentoo-dev] mulltiib cruft: /emul Mike Frysinger
2006-08-09 14:57 ` [gentoo-dev] " Duncan
2006-08-09 15:50   ` Mike Frysinger
2006-08-09 17:46     ` Danny van Dyk
2006-08-09 18:00     ` Richard Fish
     [not found]   ` <44DA1FBB.6060307@gentoo.org>
     [not found]     ` <1155228522.6489.97.camel@cocagne.max-t.internal>
2006-08-10 17:17       ` Donnie Berkholz
2006-08-10 17:26         ` Mike Doty
2006-08-10 19:42           ` Kevin F. Quinn
2006-08-10 20:17             ` Mike Frysinger
2006-08-11  4:24               ` Donnie Berkholz
2006-08-10 22:39           ` Chris Gianelloni
     [not found]       ` <200608101521.37851.vapier@gentoo.org>
2006-08-10 23:32         ` Doug Goldstein
2006-08-11  0:20           ` Mike Frysinger
2006-08-21 11:21 ` [gentoo-dev] " Herbie Hopkins
2006-08-21 14:29   ` Olivier Crête
2006-08-21 17:28     ` Mike Frysinger
2006-08-21 17:39       ` Olivier Crete
2006-08-21 19:08         ` Mike Frysinger
2006-08-21 20:30   ` Donnie Berkholz
2006-08-22 15:17     ` Duncan [this message]
2006-08-22 22:01       ` [gentoo-dev] " Mike Frysinger
2006-08-24 20:58   ` [gentoo-dev] " Chris Gianelloni
2006-08-25 12:26     ` Herbie Hopkins
2006-08-25 15:50       ` Chris Gianelloni

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='ecf76e$1hm$3@sea.gmane.org' \
    --to=1i5t5.duncan@cox.net \
    --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