| 1 |
"=?utf-8?b?0JPQvtGA0LvQvtCy?= =?utf-8?b?INCcLtCSLg==?=" |
| 2 |
<sheridan@×××××××.ru> posted 200701060330.11384.sheridan@×××××××.ru, |
| 3 |
excerpted below, on Sat, 06 Jan 2007 03:30:11 +0300: |
| 4 |
|
| 5 |
> Why qt3 build with linux-g++ , hot with linux-g++-64? |
| 6 |
|
| 7 |
I'm not the Qt maintainer, so this is simply a guess, but without |
| 8 |
investigating to deeply, probably because portage isn't setup to handle |
| 9 |
full dual-arch, that is, with a few toolchain exceptions (glibc, gcc, |
| 10 |
binutils, portage's sandbox) it handles 64-bit only, on amd64. If you |
| 11 |
want 32-bit, you either emerge the precompiled 32-bit binaries, or use a |
| 12 |
32-bit chroot, thus keeping the 32-bit portage database separate from the |
| 13 |
main system (64-bit) portage database. Since portage doesn't have to |
| 14 |
worry about keeping the two separate, the Qt build can use the generic |
| 15 |
linux-g++, instead of having to track 64-bit separately from 32-bit as it |
| 16 |
would if they were built and delivered together in the same package. |
| 17 |
|
| 18 |
-- |
| 19 |
Duncan - List replies preferred. No HTML msgs. |
| 20 |
"Every nonfree program has a lord, a master -- |
| 21 |
and if you use the program, he is your master." Richard Stallman |
| 22 |
|
| 23 |
-- |
| 24 |
gentoo-amd64@g.o mailing list |
Archives