| 1 |
>> - what is the goal for that? (well, my personal goal would be, to have a |
| 2 |
>> 32-bit system so that i can use all that pre-compiled software that's |
| 3 |
>> not available in amd64 yet - and well, no multilib anymore) |
| 4 |
> |
| 5 |
> It's meant to be a developing profile. Portage does not yet handle |
| 6 |
> ABI-dependant dependencies, but we want to work on the 32bit side of |
| 7 |
> things nevertheless. |
| 8 |
|
| 9 |
So it is a profile that - someday - can be used by normal users? |
| 10 |
|
| 11 |
> -- |
| 12 |
> $ cat profiles/default-linux/amd64/2006.0/32bit-userland/README |
| 13 |
> |
| 14 |
> Disclaimer: Don't even think about using this profile outside a chroot. |
| 15 |
> All problems related to the profile should block tracker bug #124816. |
| 16 |
> |
| 17 |
> Since getting this profile running with a stage3 is rather... "tricky", |
| 18 |
> I've put together an experimental stage: |
| 19 |
> |
| 20 |
> http://dev.gentoo.org/~blubb/32bit-userland.tar.bz2 |
| 21 |
> |
| 22 |
> Have fun! |
| 23 |
> -- |
| 24 |
|
| 25 |
Yes, i've read that. I don't want to use it now. |
| 26 |
|
| 27 |
> In other words: It's a great way to mess up your box *very* fast. It |
| 28 |
> won't even let you do `emerge -e system` yet. If you feel like digging |
| 29 |
> around in mud, contact me off-list and I'll give you some pointers. But |
| 30 |
> don't file bugs without having a patch ready, we're simply not there yet. |
| 31 |
|
| 32 |
OK, actually i've just setup my 64bit gentoo in parallel to my 32bit |
| 33 |
gentoo. So i'm not yet in the mood to "dig around in mud" :-) |
| 34 |
|
| 35 |
|
| 36 |
-- |
| 37 |
gentoo-amd64@g.o mailing list |
Archives