From owner-freebsd-questions@FreeBSD.ORG Tue Sep 1 13:44:11 2009 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1FAFA1065670 for ; Tue, 1 Sep 2009 13:44:11 +0000 (UTC) (envelope-from stapleton.41@gmail.com) Received: from mail-yw0-f191.google.com (mail-yw0-f191.google.com [209.85.211.191]) by mx1.freebsd.org (Postfix) with ESMTP id D42DF8FC22 for ; Tue, 1 Sep 2009 13:44:10 +0000 (UTC) Received: by ywh29 with SMTP id 29so7063752ywh.33 for ; Tue, 01 Sep 2009 06:44:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=s7bWpGFEGWYMYrKpZCElhmd128Z5FdmLYRWg/+0iArI=; b=dZDUwVt320fBNuYQen5j4+3Wxc1lWMEtqiov84ha0ch2iVnTIWOozldFs/HxQlGex4 PBL98PD4jTD4XaQWE75NmoQNesYruFIEpbX9O5P5rte6k8USaJcmwHExk+RQIec065k0 ITGVXOMtrcIGMtPnkO/j8J/i4pSOJt3SHO8jM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=urC+RMPDNInPKQxO2YB0cgchBfeq0gsd1hSgLkNmfOencaqY8/ec1hJW7nfVYtmnW7 8qEKYrPWkjA0amHQ6MiXuIFZKmcdDUglz5vw+xY5g44dDYmrD/hggqjY9O8qS0+hf/ug zh8rWg6etx/eP32PpEYrDUd0h6FAWrJG0CnDM= MIME-Version: 1.0 Received: by 10.151.4.9 with SMTP id g9mr11735394ybi.35.1251812650300; Tue, 01 Sep 2009 06:44:10 -0700 (PDT) In-Reply-To: References: Date: Tue, 1 Sep 2009 09:44:10 -0400 Message-ID: <80f4f2b20909010644j7962dc4cub71e725d083072ef@mail.gmail.com> From: Jim To: "b. f." Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-questions@freebsd.org Subject: Re: 32 bit ports on an AMD64 system X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Sep 2009 13:44:11 -0000 > First, I hope that you have a good reason for doing this, because it > is going to be a PITA, and prone to all sorts of problems. [...] Unfortunately I do. The 32 bit stuff is *would be really nice, but not necessary*, but the ability to use extra memory *and* dynamically load kernel modules is a bit more important to me. > If you are just talking about unshadowed ports, you could try adding > something like the following to /etc/make.conf: > > .ifdef(32BIT) > PREFIX=/usr/local/32 > LOCALBASE=/usr/local/32 > LDCONFIG=/sbin/ldconfig -32 > CFLAGS+=-m32 > .endif > > and then wrapping your portupgrade, portmaster, or make commands with: > > env 32BIT=yes [insert rest of command here] > > If there is shadowing, you have to consider how to manage the > environment PATH so that you can actually run the 32-bit binary > executables without typing in fully-qualified pathnames every time, > and maybe also using LD_RUN_PATH or LD_LIBRARY_PATH so that the right > libraries are used --- you can see how problems crop up at every turn? I was thinking of leaving the standard paths alone, and setting up one or more [ba|c|]sh32 alias/scripts which would start up the appropriate shell, with 32-bit directories at the front of the path. I know I'll end up having both 32- and 64-bit of Python on my system (many of the main apps I use require python - but I also want to be able to use py-psyco), as well as a few copies of the various GUI toolkits in 32-bit. Thanks for the info, -Jim Stapleton -Jim Stapleton