Date: Wed, 20 Oct 2004 13:25:20 -0400 From: Christopher Nehren <apeiron@comcast.net> To: FreeBSD Ports List <ports@freebsd.org> Subject: Suggestions for dealing with Linux-specific assembly in ports Message-ID: <1098293121.59168.52.camel@prophecy.dyndns.org>
next in thread | raw e-mail | index | archive | help
--=-J2yBaFQhX6D9Uge35leD Content-Type: text/plain Content-Transfer-Encoding: quoted-printable I'm looking to make a FreeBSD port out of OpenSPC (http://web.umr.edu/~bmartin/snes.htm) which is an SPC (sound format used by SNES ROM dumpers for music files) plugin for XMMS. There's a small issue, though, which I'm not sure of how to handle: the port uses some Linux-specific assembly code in order to increase performance. Now, the port *does* work -- I'm listening to the original Chrono Trigger sound track as I write this, and it's crystal clear -- but I'm not sure of how to handle the Linux assembly code. Should I mark the port as BROKEN for !i386 and set USE_LINUX? I know next to nothing of assembly, so I won't be able to patch the code myself. --=20 I abhor a system designed for the "user", if that word is a coded pejorative meaning "stupid and unsophisticated". -- Ken Thompson - Unix is user friendly. However, it isn't idiot friendly. --=-J2yBaFQhX6D9Uge35leD Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQBBdp+Ak/lo7zvzJioRAgbbAKCAf1iMxaHXpFtVMvhRR40Wuwsv8wCbBJdq 2gTqvW1a5W0zTt+0aUbdaDQ= =saoM -----END PGP SIGNATURE----- --=-J2yBaFQhX6D9Uge35leD--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1098293121.59168.52.camel>