From owner-freebsd-alpha Sun Dec 27 23:32:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA02604 for freebsd-alpha-outgoing; Sun, 27 Dec 1998 23:32:47 -0800 (PST) (envelope-from owner-freebsd-alpha@FreeBSD.ORG) Received: from mail.sat.t.u-tokyo.ac.jp (dryad.sat.t.u-tokyo.ac.jp [133.11.156.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA02598; Sun, 27 Dec 1998 23:32:45 -0800 (PST) (envelope-from simokawa@sat.t.u-tokyo.ac.jp) Received: from ett.sat.t.u-tokyo.ac.jp (ett.sat.t.u-tokyo.ac.jp [133.11.156.43]) by mail.sat.t.u-tokyo.ac.jp (8.8.6/3.4Wbeta6-SAT1.0) with ESMTP id QAA27027; Mon, 28 Dec 1998 16:32:28 +0900 (JST) (envelope-from simokawa@sat.t.u-tokyo.ac.jp) Received: from localhost by ett.sat.t.u-tokyo.ac.jp (8.8.8/sat-V0.6) id QAA22417; Mon, 28 Dec 1998 16:32:27 +0900 (JST) To: asami@FreeBSD.ORG Cc: sprice@hiwaay.net, alpha@FreeBSD.ORG Subject: Re: Alpha ports collection? In-Reply-To: Your message of "Sun, 27 Dec 1998 17:24:50 -0800 (PST)" <199812280124.RAA27021@bubble.didi.com> References: <199812280124.RAA27021@bubble.didi.com> X-Face: OE([KxWyJI0r[R~S/>7ia}SJ)i%a,$-9%7{*yihQk|]gl}2p#"oXmX/fT}Bn7:#j7i14gu$ jgR\S*&C3R/pJX Date: Mon, 28 Dec 1998 16:32:27 +0900 From: Hidetoshi Shimokawa X-Dispatcher: imput version 980905(IM100) Lines: 62 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org asami> * Some math libraries come with assembly for multiple platforms. asami> * A good example is the GNU gmp library. I do agree however that asami> * we should probably seriously consider adding ${ARCH}_ONLY and asami> * BROKEN_${ARCH} to bsd.port.mk. asami> asami> Well, the idea was to have a "Makefile.${ARCH}" that defines these asami> stuff. Do you think having variables is better? humm.. in the current framework, "BRONEN_ALPHA" is equivalent to: .if ${MACHINE_ARCH} == "alpha" BROKEN = cannot build on alpha .endif "ALPHA_ONLY" is equivalent to: .if ${MACHINE_ARCH} != "alpha" BROKEN = for alpha only .endif these may be enough for a while. I didn't think much about this. BTW, how shall we treat shareable packages (e.g. X11 and TeX fonts). It's waste of time and space to build packages on each architecture. Do we need ARCH_COMMON tag and packages-common directoy in addition to packages-i386 and packages-alpha? asami> * I'll have some time after next Wednesday (family reunion in asami> * Texas starting tomorrow) to work up some patches. Got any asami> * preferences for the new features. One think someone should asami> * probably take a look at how (Net|Open)BSD is handling this. asami> * They have a ports tree that looks somewhat like our own and asami> * surely they have something in there to handle multiple archs. asami> asami> "Someone". :) I'll try to look. asami> Meanwhile, if you can get them to work with "#ifdef __alpha" or asami> whatever, go right ahead. Shimokawa-san, do you want commit access? Yes, it should be hard to fix many ports without commit access. asami> * I certainly wouldn't mind seeing a weekly status report. I'll asami> * let Satoshi speak for himself. :) However we should probably asami> * hold off on sending this out to everyone at least in the very asami> * near term until we get established who's doing what and where asami> * all the packages are going to live. Otherwise we'll be fielding asami> * tons of Email asking where things are and if our only answer asami> * is "on our personal machines" they could get miffed. asami> asami> I can create a package-alpha dir on wcarchive if someone can build the asami> packages. Actually, are those buildable on i386 machines under a asami> chroot dir? If so, I can even build those myself. :) I afraid it's difficult. It shouldn't be difficult to get cross compiler work, but some ports may use their own bootstrap binaries (e.g. miniperl) which cannot run on i386. /\ Hidetoshi Shimokawa \/ simokawa@sat.t.u-tokyo.ac.jp PGP public key: finger -l simokawa@sat.t.u-tokyo.ac.jp To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message