a few questions about ports

[Adriaan de Groot]

-----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 
compile and then fail, some won't even compile. YMMV, and as Brooks points 
out, the metadata is not up-to-date for amd64 (perhaps because not all the 
ports have even been tried yet).

Emacs is LISP. LISP is evil. Your average LISP interpreter wouldn't think 
twice about randomly shuffling the 32 bits in an int to get a pointer to a 
memory allocation node. That said, I believe James van Artsdalen had some 
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 
casts show up easily and generally you can replace int by long in the 
datastrcutures and things will work out OK (though binary file format 
compatibility is toast then). 

va_alist and friends are a lot harder to deal with (POSE, the Palm Emulator, 
has this problem).

In the end, your best bet is to muck about in work/ in your ports tree, sort 
it out yourself, and mail the port maintainer and possibly the upstream as 
well. Failing that, sending accurate compile-failure logs can sometimes help 
too.

- -- 
pub  1024D/FEA2A3FE 2002-06-18 Adriaan de Groot <groot at kde.org>
            If the door is ajar, can we fill it with door-jamb?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (FreeBSD)

iD8DBQFADvqEdqzuAf6io/4RAl2xAJ48PEQj9xopAVlUiQXy5XFVXakDVgCgp13S
fm1jR3k1+hkYYcbTbT488pY=
=hhXB
-----END PGP SIGNATURE-----