Correct. It's hard to nail down the right terminology when I'm learning by
doing. I want GCC to ignore x86 flags that aren't znver1, and keep znver1
as the default.
On Fri, Mar 8, 2019, 3:44 PM Jonathan Wakely wrote:
> On Fri, 8 Mar 2019 at 22:00, Vanida Plamondon
> wrote:
> >
> > OK, so it see
On Fri, 8 Mar 2019 at 22:00, Vanida Plamondon
wrote:
>
> OK, so it seems I need to give more information to clarify what I am
> trying to do.
>
> I am not invoking or configuring gcc directly.
(If you're creating a toolchain then surely you're configuring GCC.)
> I am creating debian
> source co
OK, so it seems I need to give more information to clarify what I am
trying to do.
I am not invoking or configuring gcc directly. I am creating debian
source code packages which are then dispatched to launchpad.net, which
then automatically compiles and builds my package based on the debian
config
On Fri, 8 Mar 2019 at 11:28, Vanida Plamondon
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 thr
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 tha
On Fri, Mar 8, 2019 at 8:56 AM Vanida Plamondon
wrote:
>
> I have been working on some PPA's that will provide standard Ubuntu
> and Linux Mint packages that are compiled with the znver1 cpu
> optimisations (Ryzen CPU). It has been quite tedious (though not
> particularly hard) to modify existing
