Created attachment 306355 [details] media-libs/libjpeg-turbo-1.2.0-r1 failure build.log From the build.log: checking for nasm... no checking for nasmw... no checking for yasm... no configure: error: no nasm (Netwide Assembler) found This should be a simple fix.
The ebuild could have: x86-fbsd? ( ${ASM_DEPEND} ) amd64-fbsd? ( ${ASM_DEPEND} ) But now that I look at it, dev-lang/nasm doesn't even have ~amd64-fbsd keywording. Moving to bsd@ to handle this
(In reply to comment #1) > The ebuild could have: > > x86-fbsd? ( ${ASM_DEPEND} ) > amd64-fbsd? ( ${ASM_DEPEND} ) > > But now that I look at it, dev-lang/nasm doesn't even have ~amd64-fbsd > keywording. > > Moving to bsd@ to handle this you can add it, this will simplify the task later on so far, nothing in the tree has ~amd64-fbsd keywords as far as i can tell, adding the dep will help us once keywording starts.
(In reply to comment #2) > (In reply to comment #1) > > The ebuild could have: > > > > x86-fbsd? ( ${ASM_DEPEND} ) > > amd64-fbsd? ( ${ASM_DEPEND} ) > > > > But now that I look at it, dev-lang/nasm doesn't even have ~amd64-fbsd > > keywording. > > > > Moving to bsd@ to handle this > > you can add it, this will simplify the task later on > > so far, nothing in the tree has ~amd64-fbsd keywords as far as i can tell, > adding the dep will help us once keywording starts. http://sources.gentoo.org/viewvc.cgi/gentoo-x86/media-libs/libjpeg-turbo/libjpeg-turbo-1.2.0-r1.ebuild?r1=1.8&r2=1.9