From owner-freebsd-amd64@FreeBSD.ORG Mon Jan 17 20:48:59 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9357C16A4CF for ; Mon, 17 Jan 2005 20:48:59 +0000 (GMT) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.198]) by mx1.FreeBSD.org (Postfix) with ESMTP id DD38C43D41 for ; Mon, 17 Jan 2005 20:48:58 +0000 (GMT) (envelope-from astrodog@gmail.com) Received: by wproxy.gmail.com with SMTP id 68so781820wri for ; Mon, 17 Jan 2005 12:48:56 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=SWWHvfnmjQAd4rB6HQnE94E9sVDeAQ70BkRVcCwWzEW60zN9eGGzsqkWKyiPzePUv+mArXzT4IvgUBrJ/3GZ3UIMaEHSgugciepUreiXd3qws3QP/ZoQo9ouvIxpb7QZVyuF8KhI4JKWZTyt7M/SBmSs/d3ZZ7WhWCI7bYEeXEY= Received: by 10.54.52.40 with SMTP id z40mr102946wrz; Mon, 17 Jan 2005 12:48:56 -0800 (PST) Received: by 10.54.40.73 with HTTP; Mon, 17 Jan 2005 12:48:56 -0800 (PST) Message-ID: <2fd864e0501171248791ddd18@mail.gmail.com> Date: Mon, 17 Jan 2005 14:48:56 -0600 From: Astrodog To: freebsd-amd64@freebsd.org In-Reply-To: <20050117203818.GA29131@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <20050117203818.GA29131@dragon.nuxi.com> Subject: Re: [RFC] what to name linux 32-bit compat X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Astrodog List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Jan 2005 20:48:59 -0000 On Mon, 17 Jan 2005 12:38:18 -0800, David O'Brien wrote: > [ Respect the Reply-to:! ] > > /usr/ports Linux 32-bit compatibility on AMD64 is a mess and too rough > for what is expected of FreeBSD. Anyway... > > We need to decide how to have both Linux i686 and Linux amd64 compat > support live side-by-side. At the moment my leanings are for > /compat/linux32 and /compat/linux. We could also go with /compat/linux > and /compat/linux64 <- taking a page from the Linux LSB naming convention > (ie, they have lib and lib64). > > Linux 32-bit support is most interesting -- that is how we get Acrobat > reader and some other binary-only ports. The only Linux 64-bit things we > might want to run that truly matter 32-bit vs. 64-bit is Oracle and > IBM-DB2. For other applications 32-bit vs. 64-bit is mostly a "Just > Because Its There(tm)" thing. So making Linux 32-bit support the > cleanest looking from a /usr/ports POV has some merit. > > What do others think? > > -- > -- David (obrien@FreeBSD.org) > _______________________________________________ > freebsd-amd64@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 > To unsubscribe, send any mail to "freebsd-amd64-unsubscribe@freebsd.org" > What about having linux32, linux64, and linux (Which builds whatever the arch on the local machine is)? Seems like the easiest for all involved, as well as people with clean, 64-bit safe code, who want to avoid the problem entirely can just use linux as a dep too, instead of having to have some ugly kludgery to figure out which one they're on, and which one they should depend on, based on arch. --- Harrison Grundy