On Tuesday 22 April 2008 02:28:55 Brad wrote: > On Tuesday 22 April 2008 01:58:06 Antoine Jacoutot wrote: > > On Mon, 21 Apr 2008, Brad wrote: > > > On Wed 2008.04.16 at 17:10 +0200, syl wrote: > > > > I've update the nasm package to version 2.02. > > > > > > Add amd64 to ONLY_FOR_ARCHS and make sure it works. > > > > And if it does, wouldn't it might be needed to add nasm as build_depends > > for ports that already do this for i386 in case it gets picked up by > > configure or so. > > No I would not just blindly add amd64 in. You would have to check each > port that uses nasm on a case by case basis and see if what is there > would even use nasm on amd64 since some autoconf tests only check > for i386 and then make sure the code builds and the program works.
I should also add that I looked at most of the ports using nasm and from a quick look at them it seems most of them only have code for i386. But I would check the ports on a amd64 box to make sure that with nasm installed they either ignore nasm or if nasm is picked up but the code is for i386 that it doesn't break during compilation so you'll probably have to pass some flag to disable the use of nasm, -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.
