On 01-09-16 08:53, Nathan Rossi wrote:
> On Thu, Sep 1, 2016 at 3:12 AM, Peter Smith <[email protected]> wrote:
>> Glad its not just me. Do you think it could be related to my use of the
>> master branch rather than a released version?
>>
>> On 31 August 2016 at 15:00, Mike Looijmans <[email protected]> wrote:
>>>
>>> On 31-08-16 15:40, SMITH Peter T wrote:
>>>>
>>>> Hi,
>>>>
>>>> I am trying to build core image minimal for the ZCU102 using the master
>>>> branches poky and meta-xilinx and I am receiving lots of warnings about
>>>> kernel
>>>> configurations not making it into the final kernel configurations. Is
>>>> this
>>>> normal or I have I done something wrong?
>>>
>>>
>>> Well I noticed that the kernel config doesn't quite work as expected on
>>> that particular board but I'm still investigating the "why" myself.
>
> Found the bug, it relates to a change in oe-core/kernel-yocto.bbclass
> that was made recently 0f698dfd1c8bbc0d53ae7977e26685a7a3df52a3. The
> values for KCONFIG_MODE changed, such that it is defaulting to
> "allnoconfig". This only applies to zcu102-zynqmp because its the only
> machine that uses a KBUILD_DEFCONFIG as the base.
>
> I've staged the following patch
> https://github.com/nathanrossi/meta-xilinx/commit/34e08e9f6635d4365058a96ea13bf8286d9930a8.
> Could one of you confirm that it resolves the issue and that the built
> kernel works?
Hmm, it seems to break my build:
| [INFO] Configuring target/machine combo: "alldefconfig/--reconfig"
| No build dir specified. Use "-o" to specify one.
| config of "alldefconfig/--reconfig" failed
so apparently this is for a newer OE master?
> On Thu, Sep 1, 2016 at 3:12 AM, Peter Smith <[email protected]> wrote:
>> Glad its not just me. Do you think it could be related to my use of the
>> master branch rather than a released version?
>>
>> On 31 August 2016 at 15:00, Mike Looijmans <[email protected]> wrote:
>>>
>>> On 31-08-16 15:40, SMITH Peter T wrote:
>>>>
>>>> Hi,
>>>>
>>>> I am trying to build core image minimal for the ZCU102 using the master
>>>> branches poky and meta-xilinx and I am receiving lots of warnings about
>>>> kernel
>>>> configurations not making it into the final kernel configurations. Is
>>>> this
>>>> normal or I have I done something wrong?
>>>
>>>
>>> Well I noticed that the kernel config doesn't quite work as expected on
>>> that particular board but I'm still investigating the "why" myself.
>
> Found the bug, it relates to a change in oe-core/kernel-yocto.bbclass
> that was made recently 0f698dfd1c8bbc0d53ae7977e26685a7a3df52a3. The
> values for KCONFIG_MODE changed, such that it is defaulting to
> "allnoconfig". This only applies to zcu102-zynqmp because its the only
> machine that uses a KBUILD_DEFCONFIG as the base.
>
> I've staged the following patch
> https://github.com/nathanrossi/meta-xilinx/commit/34e08e9f6635d4365058a96ea13bf8286d9930a8.
> Could one of you confirm that it resolves the issue and that the built
> kernel works?
Hmm, it seems to break my build:
| [INFO] Configuring target/machine combo: "alldefconfig/--reconfig"
| No build dir specified. Use "-o" to specify one.
| config of "alldefconfig/--reconfig" failed
so apparently this is for a newer OE master?
Kind regards,
Mike Looijmans
System Expert
|
TOPIC Products |
|
| |
|
Materiaalweg 4 |
|
| |
|
5681 RJ Best |
T: |
+31 (0) 499 33 69 69 | |
|
Postbus 440 |
E: |
||
|
5680 AK Best |
W: |
||
| The Netherlands |
Please consider the environment before printing this
e-mail
Topic zoekt gedreven (embedded) software specialisten!
-- _______________________________________________ meta-xilinx mailing list [email protected] https://lists.yoctoproject.org/listinfo/meta-xilinx
