public inbox for gentoo-amd64@lists.gentoo.org
 help / color / mirror / Atom feed
From: Jeremy Huddleston <eradicator@gentoo.org>
To: gentoo-amd64@lists.gentoo.org
Subject: [gentoo-amd64] compiler-config 2.0: request for help
Date: Fri, 28 Oct 2005 01:00:40 -0700	[thread overview]
Message-ID: <1130486440.11723.85.camel@cloud.outersquare.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1329 bytes --]

Compiler-config is pretty much 98% done, but I haven't had time to work
on it these past few weeks because I'm in mid semester crunch mode.  I
was hoping to get it done before school got busy, but that's not going
to happen.  I'd like to solicit some help finishing it up, and since
most of the remaining issues are pertinent to multilib toolchains, I
figured it'd be best to try here than -dev.

The remaining issues before release are:

Fixup the migration code to intelligently choose the correct profile.
Currently, it just deletes all the ones installed by toolchain.eclass,
converts the gcc-config-1.X profiles (so it knows the profile names) and
activates the one corresponding to the old profile.  This isn't so great
on multilib systems because it destroys the alternative target profiles
(like i686 in our case).  Additionally, the migration script should
activate profiles for the alternative targets.

toolchain.eclass needs to be updated to properly set the new profile for
all targets of the toolchain, not just the current one.

the eselect module could do with some cleanup... especially user
feedback.

Any help would be greatly appreciated... especially since I was hoping
to get this done in time for use in 2006.0, then the corresponding
binutils tool for 2006.1.

Thanks,
Jeremy

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

                 reply	other threads:[~2005-10-28  8:05 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1130486440.11723.85.camel@cloud.outersquare.org \
    --to=eradicator@gentoo.org \
    --cc=gentoo-amd64@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