On Thu, 14 Jan 2010 19:50:03 -0600, Johan Hattne
> On 12 Jan 2010, at 04:20, Fabian Groffen wrote:
>> On 11-01-2010 23:20:57 -0600, Johan Hattne wrote:
>>> I just installed snow leopard on my MacBook Pro and wanted to give the
>>> whole 64-bit thing a spin. Oddly enough I could only access 32-bit
>>> macos profiles. Also, the mask on ">=sys-apps/portage-2.2_pre"
>>> in profiles/package.mask, but overridden in
>>> profiles/prefix/package.mask?) is in effect, so I've got the sneaky
>>> suspicion I've missed something obvious to everyone but me. Question
>> You'll have to explain a bit what you did. Did you try to switch, did
>> you rebootstrap? Do you use multiple trees?
> I upgraded from Leopard to Snow Leopard, set CHOST to
> x86_64-apple-darwin10 in etc/make.conf, upgraded Xcode and used that to
> emerge new gcc-apple and binutils-apple into place, and then did an
> --emptytree system". So, no, I did not rebootstrap.
Well, you can't just change the CHOST and expect everything to work.
Actually, it is quite a process to change your CHOST.
> I'm also using the svn prefix overlay. That one still had the full
> licenses and profiles directories in it. Removing the profiles
> took care of the portage package mask from above.
You should be using rsync only.
> The problem with "invisible" 64 bit profiles went away after reemerging
> all the eselect stuff (but I still don't understand why "arch=$(arch)"
> gives x64-macos in the profile.eselect module, while "arch" on the
> line gives i386)?
Your toolchain is in a weird state.
> I'll now find some lint to stuff the still-smoking bullet holes in my
Your best best is to save your configuration files and world file and
rebootstrap. Although, technically you can probably work through this. It
is just not that fun.
> // Cheers; Johan