From owner-freebsd-amd64@FreeBSD.ORG Wed Jan 21 14:18:17 2004 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 62C7D16A4CE for ; Wed, 21 Jan 2004 14:18:17 -0800 (PST) Received: from pandora.cs.kun.nl (pandora.cs.kun.nl [131.174.33.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7F22043D2F for ; Wed, 21 Jan 2004 14:17:45 -0800 (PST) (envelope-from adridg@cs.kun.nl) Received: from localhost by pandora.cs.kun.nl id i0LMHi65010518 (8.12.10/3.58); Wed, 21 Jan 2004 23:17:44 +0100 (MET) From: Adriaan de Groot To: freebsd-amd64@freebsd.org Date: Wed, 21 Jan 2004 23:17:35 +0100 User-Agent: KMail/1.6.50 References: <1074721460.400ef2b452e09@webmail.acadiau.ca> <20040121215816.GB21939@Odin.AC.HMC.Edu> In-Reply-To: <20040121215816.GB21939@Odin.AC.HMC.Edu> MIME-Version: 1.0 Content-Disposition: inline Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Message-Id: <200401212317.40273.adridg@cs.kun.nl> Subject: Re: a few questions about ports X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Jan 2004 22:18:17 -0000 =2D----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wednesday 21 January 2004 22:58, Brooks Davis wrote: > On Wed, Jan 21, 2004 at 05:44:20PM -0400, Murray Patterson wrote: > > I'm trying to get octave, scilab and emacs working for my machine. > > The ports collection contains ports which worked on at least one of > the 5+ FreeBSD architectures at some time in the past. There is a The ports collection for amd64 is wonky at best right now. Some things will= =20 compile and then fail, some won't even compile. YMMV, and as Brooks points= =20 out, the metadata is not up-to-date for amd64 (perhaps because not all the= =20 ports have even been tried yet). Emacs is LISP. LISP is evil. Your average LISP interpreter wouldn't think=20 twice about randomly shuffling the 32 bits in an int to get a pointer to a= =20 memory allocation node. That said, I believe James van Artsdalen had some=20 success getting emacs up and running, check the archives of this group. Many other compile issues can be dealt with fairly simply. pointer-to-int=20 casts show up easily and generally you can replace int by long in the=20 datastrcutures and things will work out OK (though binary file format=20 compatibility is toast then).=20 va_alist and friends are a lot harder to deal with (POSE, the Palm Emulator= ,=20 has this problem). In the end, your best bet is to muck about in work/ in your ports tree, sor= t=20 it out yourself, and mail the port maintainer and possibly the upstream as= =20 well. Failing that, sending accurate compile-failure logs can sometimes hel= p=20 too. =2D --=20 pub 1024D/FEA2A3FE 2002-06-18 Adriaan de Groot If the door is ajar, can we fill it with door-jamb? =2D----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (FreeBSD) iD8DBQFADvqEdqzuAf6io/4RAl2xAJ48PEQj9xopAVlUiQXy5XFVXakDVgCgp13S fm1jR3k1+hkYYcbTbT488pY=3D =3DhhXB =2D----END PGP SIGNATURE-----