Hey Derek, I would advise against this, inc files aren't supposed to be appended to, priorities would work, adding TUNEVALID on your machine conf is also possible, but I'd say those are both temporary solutions, you might also just wait a little bit until they release their 2020.x releases already compatible with Zeus.
Alejandro On Sat, 28 Mar 2020 at 15:00, Konrad Weihmann <[email protected]> wrote: > What you could do is to override the file in a layer with higher priority. > Just create the same file under the same path (e.g. > <your-layer>/conf/machine/include/microblaze/feature-microblaze-versions.inc) > and apply the changes there - this should help for now. > > But be aware that this way could lead to trouble in case the overridden > file does change on an update - so use with caution. > Unfortunately you can't BBMASK the original inc file, you have to rely on > layer prio. > On 28.03.20 22:42, Derek Dresser wrote: > > Hello, > > I am trying to update a build for a custom board based on the Xilinx > zcu102-zynqmp (using meta-xilinx) to 'zeus' and am getting the following > error message: > > Toolchain tunings invalid: > Tuning 'microblaze' has the following errors: > Feature 'v11.0' is not defined. > > > I have tracked this down to the following file: > > poky/meta/conf/machine/include/microblaze/feature-microblaze-versions.inc > > Editing this file allows me to build without errors. I'd like to apply a > patch to this file (or override the file with an edited version.) > > diff --git > meta/conf/machine/include/microblaze/feature-microblaze-versions.inc > meta/conf/machine/include/microblaze/feature-microblaze-versions.inc > index 955674fff9..3221e2aab7 100644 > --- meta/conf/machine/include/microblaze/feature-microblaze-versions.inc > +++ meta/conf/machine/include/microblaze/feature-microblaze-versions.inc > @@ -44,6 +44,7 @@ TUNEVALID[v9.4] = "MicroBlaze version 9.4" > TUNEVALID[v9.5] = "MicroBlaze version 9.5" > TUNEVALID[v9.6] = "MicroBlaze version 9.6" > TUNEVALID[v10.0] = "MicroBlaze version 10.0" > +TUNEVALID[v11.0] = "MicroBlaze version 11.0" > > # Version conflict matrix > TUNECONFLICTS[v8.00] = "" > @@ -60,6 +61,7 @@ TUNECONFLICTS[v9.4] = "v8.00 v8.10 v8.20 v8.30 v8.40 > v8.50 v9.0 v9.1 v9.2 v9.3" > TUNECONFLICTS[v9.5] = "v8.00 v8.10 v8.20 v8.30 v8.40 v8.50 v9.0 v9.1 > v9.2 v9.3 v9.4" > TUNECONFLICTS[v9.6] = "v8.00 v8.10 v8.20 v8.30 v8.40 v8.50 v9.0 v9.1 > v9.2 v9.3 v9.4 v9.5" > TUNECONFLICTS[v10.0] = "v8.00 v8.10 v8.20 v8.30 v8.40 v8.50 v9.0 v9.1 > v9.2 v9.3 v9.4 v9.5 v9.6" > +TUNECONFLICTS[v11.0] = "v8.00 v8.10 v8.20 v8.30 v8.40 v8.50 v9.0 v9.1 > v9.2 v9.3 v9.4 v9.5 v9.6 v10.0" > > # Version flags > TUNE_CCARGS += "-mcpu=${@microblaze_current_version(d, True)}" > > I know how to apply a patch against a recipe source file, but not this > toolchain tuning include file. How can I accomplish this without editing > the files in openembedded-core? I'd like to override or patch this in my > own layer. > > Thanks, > Derek > > >
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#48971): https://lists.yoctoproject.org/g/yocto/message/48971 Mute This Topic: https://lists.yoctoproject.org/mt/72619232/21656 Group Owner: [email protected] Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
