Suggestions for dealing with Linux-specific assembly in ports

[Christopher Nehren]

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.
-- 
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.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: This is a digitally signed message part
Url : http://lists.freebsd.org/pipermail/freebsd-ports/attachments/20041020/623f7b07/attachment.bin