public inbox for gentoo-amd64@lists.gentoo.org
 help / color / mirror / Atom feed
From: Duncan <1i5t5.duncan@cox.net>
To: gentoo-amd64@lists.gentoo.org
Subject: [gentoo-amd64]  Re: qt3
Date: Sat, 6 Jan 2007 05:10:37 +0000 (UTC)	[thread overview]
Message-ID: <ennb0d$hdk$3@sea.gmane.org> (raw)
In-Reply-To: 200701060330.11384.sheridan@stavcom.ru

"=?utf-8?b?0JPQvtGA0LvQvtCy?= =?utf-8?b?INCcLtCSLg==?="
<sheridan@stavcom.ru> posted 200701060330.11384.sheridan@stavcom.ru,
excerpted below, on  Sat, 06 Jan 2007 03:30:11 +0300:

> Why qt3 build with linux-g++ , hot with linux-g++-64?

I'm not the Qt maintainer, so this is simply a guess, but without
investigating to deeply, probably because portage isn't setup to handle
full dual-arch, that is, with a few toolchain exceptions (glibc, gcc,
binutils, portage's sandbox) it handles 64-bit only, on amd64.  If you
want 32-bit, you either emerge the precompiled 32-bit binaries, or use a
32-bit chroot, thus keeping the 32-bit portage database separate from the
main system (64-bit) portage database.  Since portage doesn't have to
worry about keeping the two separate, the Qt build can use the generic
linux-g++, instead of having to track 64-bit separately from 32-bit as it
would if they were built and delivered together in the same package.

-- 
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-amd64@gentoo.org mailing list



      parent reply	other threads:[~2007-01-06  5:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-06  0:30 [gentoo-amd64] qt3 Горлов М.В.
2007-01-06  4:11 ` Boyd Stephen Smith Jr.
2007-01-06 10:39   ` Горлов М.В.
2007-01-06  5:10 ` Duncan [this message]

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