In my musings on what turned out to be an incomplete change to libjpeg-turbo when upgrading from jpegsrc [ .so.8 needed to be remade ] I wrote: > > For once, I had changed my log directory names across the builds, > so the rebuilds weren't overwriting the previous logs. I wondered > if nasm was still needed (if I wasn't going to build jpeg turbo in > the upgrade, did firefox need nasm ?), so I looked at the logs. > > The only references to nasm were parameters passed to yasm when > building [ -rnasm -pnasm ], so I wondered if yasm could build > libjpeg-turbo-1.2.1 : the answer is that it can, and the .so is a > bit smaller.
I'm now in the process of downgrading my oldest x86_64 to x86_32 [ i.e. i686 ] - recent g++ is unusable on a desktop x86_64 with only 2 GB of memeory and a uniprocessor (i.e. the desktop becomes unresponsive when compiling). And I find that here (unlike x86_64, where yasm can be used) nasm _is_ needed. ĸen -- das eine Mal als Tragödie, das andere Mal als Farce -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
