With expat-2.2.2 the tests are invoked from a run.sh script. But that script starts: #! /usr/bin/env bash
(I didn't know you could put a space after the shebang). At this point we do not yet have /usr/bin/env (from coreutils), but we do have /bin/bash. The following sed, run before configure, solves this: sed -i 's%^.*env bash$%#!/bin/bash%' run.sh.in Please note that for the moment I'll only be noticing new test failures which cause tests that previously sailed through in my builds to now fail. I might get round to looking at the full results, or I might not. ĸen -- I live in a city. I know sparrows from starlings. After that everything is a duck as far as I'm concerned. -- Monstrous Regiment -- http://lists.linuxfromscratch.org/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
