aboutsummaryrefslogtreecommitdiffstats
path: root/toolchain/nasm/Makefile
Commit message (Collapse)AuthorAgeFilesLines
* toolchain: nasm: update to 2.15.05Daniel Golle2020-09-281-2/+2
| | | | | | Compile-tested libx264 and ffmpeg with x86-asm, worked fine. Signed-off-by: Daniel Golle <daniel@makrotopia.org>
* toolchain/nasm: update to version 2.14Daniel Golle2019-05-111-2/+2
| | | | Signed-off-by: Daniel Golle <daniel@makrotopia.org>
* nasm: disable LTO, remove host specific workaroundsFelix Fietkau2018-07-101-7/+1
| | | | | | | | | | | | The recent build failures on various platforms were apparently caused by the fact that LTO build support in the configure script does not check if it has a suitable version of gcc and simply assumes that gcc-ar is available and can be used for intermediate files. Since we really don't need to build nasm with LTO, simply disable it and keep the whole build more portable Signed-off-by: Felix Fietkau <nbd@nbd.name>
* toolchain/nasm: force ar and ranlib only on macOSXHauke Mehrtens2018-07-081-3/+5
| | | | | | | | | | On Debian 9 nasm does not build when we force it to use ranlib, for macOSX this is needed. Only force this on macOSX and not on any other OS, this should fix the build of nasm on Linux systems. On my Debian system the nasm configure script selects gcc-ranlib and gcc-ar instead. Fixes: d3a7587eb95 ("toolchain/nasm: fix missing AR/RANLIB variables") Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* toolchain/nasm: fix missing AR/RANLIB variablesFelix Fietkau2018-07-071-4/+5
| | | | | | Fixes build on macOS Signed-off-by: Felix Fietkau <nbd@nbd.name>
* toolchain: Replace YASM with NASMTed Hess2018-07-051-0/+56
Packages libx264 and ffmpeg are built with ASM options on x86 platforms. The current libx264 version no longer builds with YASM and requires NASM. ffmpeg 3.x can be built with either YASM or NASM however, furture 4.x versions will require NASM. Signed-off-by: Ted Hess <thess@kitschensync.net> Acked-by: Rosen Penev <rosenp@gmail.com>