On Fri, 8 Mar 2019 at 11:28, Vanida Plamondon <vanida.plamon...@gmail.com> wrote: > > I realise that, however, debian packages seem to use multiple build > systems (automake, dh_automake, ninja, etc.), and have no standard > (that is adhered to), for setting up each build environment. > Additionally, some packages seem to throw their build configuration > setup throughout multiple files that are difficult to pin down, and > usually have little documentation. I am trying to set up a toolchain > that automatically fetches upstream sources when updated, updates the > changelog to reflect that the package is znver1 optimised, and > automatically compiles the package with the znver1 optimisations. Even > worse, many packages use different environmental variables, and some > even unset some of such standard variables. > > This means I need to setup gcc so that any x86 code thrown at it is > automatically compiled with znver1 optimisations to overcome these > limitations.
That's what the configure options Richi showed will do. N.B. he didn't say to use -march=znver1 when compiling with GCC, he said to use --with-arch=znver1 when configuring GCC itself.
