On Thu, Mar 2, 2017 at 1:14 PM, Diego Biurrun <[email protected]> wrote: > On Thu, Mar 02, 2017 at 11:02:52AM +0100, Luca Barbato wrote: >> On 02/03/2017 09:41, Diego Biurrun wrote: >> > On Thu, Mar 02, 2017 at 09:20:45AM +0100, Luca Barbato wrote: >> >> On 01/03/2017 22:07, Diego Biurrun wrote: >> >>> NASM is more actively maintained and permits generating dependency >> >>> information >> >>> as a sideeffect of assembling, thus cutting build times in half. >> >>> --- >> >>> .travis.yml | 4 ++-- >> >>> configure | 12 ++++++------ >> >>> doc/optimization.txt | 8 ++++---- >> >>> doc/platform.texi | 12 ++++++------ >> >>> 4 files changed, 18 insertions(+), 18 deletions(-) >> >> >> >> You should check for the nasm version and if it is too old default to >> >> yasm and then fail. >> > >> > Sounds like overkill to me. Non-working nasm versions appears to be an >> > OS-X-only problem. >> >> It is not, anybody with an ancient nasm lingering and an up to date yasm >> would be surprised to have libav not building after a git pull. > > That case has a very simple solution: > > ./configure --x86asmexe=yasm >
Having to manually fuzz with build options because you changed configure seems like a bad reasoning for trying to avoid a few lines of sanity checking the assembler. - Hendrik _______________________________________________ libav-devel mailing list [email protected] https://lists.libav.org/mailman/listinfo/libav-devel
