From owner-freebsd-stable@FreeBSD.ORG Thu Nov 2 18:36:24 2006 Return-Path: X-Original-To: freebsd-stable@FreeBSD.ORG Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4167B16A412 for ; Thu, 2 Nov 2006 18:36:24 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (lurza.secnetix.de [83.120.8.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3999043D49 for ; Thu, 2 Nov 2006 18:36:22 +0000 (GMT) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (slghcx@localhost [127.0.0.1]) by lurza.secnetix.de (8.13.4/8.13.4) with ESMTP id kA2IaGq2010815; Thu, 2 Nov 2006 19:36:21 +0100 (CET) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.13.4/8.13.1/Submit) id kA2IaFeS010814; Thu, 2 Nov 2006 19:36:15 +0100 (CET) (envelope-from olli) Date: Thu, 2 Nov 2006 19:36:15 +0100 (CET) Message-Id: <200611021836.kA2IaFeS010814@lurza.secnetix.de> From: Oliver Fromme To: freebsd-stable@FreeBSD.ORG, peterjeremy@optushome.com.au In-Reply-To: <20061101091958.GD849@turion.vk2pj.dyndns.org> X-Newsgroups: list.freebsd-stable User-Agent: tin/1.8.2-20060425 ("Shillay") (UNIX) (FreeBSD/4.11-STABLE (i386)) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.1.2 (lurza.secnetix.de [127.0.0.1]); Thu, 02 Nov 2006 19:36:22 +0100 (CET) Cc: Subject: Re: 6.x from i386 to amd64 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-stable@FreeBSD.ORG, peterjeremy@optushome.com.au List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Nov 2006 18:36:24 -0000 Peter Jeremy wrote: > Mark Linimon wrote: > > - certain ports have i386 binaries (can't be fixed) > > - certain ports have i386 asm code (can be fixed if there is fallback > > C code) > > A partial solution to this is to get the i386 emulation and cross- > building into better shape. If I really need a binary-only port > then I can build/run it in emulation mode. This has bee discussed > previously. > > IMHO, the FreeBSD/amd64 naming conventions make it much cleaner than > (eg) Solaris and Linux as long as you only want native-mode apps. > Unfortunately, it makes supporting i386 applications much harder > (bacause they need to understand they need to look in .../lib32 > ISO .../lib). Isn't someone working on porting variant symlinks over from dragonfly? I thought it was a SoC project or something like that. Using variant symlinks, the problem would be easy to solve: drwxr-xr-x ... lib32 drwxr-xr-x ... lib64 lrwxr-xr-x ... lib -> lib${ARCH_BITS} ARCH_BITS would be set to "64" globally, and it would be set to "32" for i386 applications. Then every program would find the correct libs automagically. Best regards Oliver PS: For those who are not familiar with variant symlinks: http://leaf.dragonflybsd.org/cgi/web-man?command=ln http://leaf.dragonflybsd.org/cgi/web-man?command=varsym -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing Dienstleistungen mit Schwerpunkt FreeBSD: http://www.secnetix.de/bsd Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. > Can the denizens of this group enlighten me about what the > advantages of Python are, versus Perl ? "python" is more likely to pass unharmed through your spelling checker than "perl". -- An unknown poster and Fredrik Lundh