Skip to contentSkip to conversation

buildman dtc check error

U-Boot York Sun 2 participants 5 messages Jul 23, 2015 – Jul 24, 2015

lore
Share & tools
lore

York Sun

author
#0 lore raw

Simon,

I am facing a weird issue on the latest u-boot. I can successfully build u-boot manually, but with buildman I see checkdtc error.

aarch64: + ls2085aqds
+make[1]: *** [checkdtc] Error 1
+make: *** [sub-make] Error 2

I have DTC 1.4.1-ge5e6df7c. Is there any flag for buildman I can see more information? I always use -vVeu as the flag.

York

#1 lore raw

Hi York,

Quoted 11 lines · York Sun

Simon,

I am facing a weird issue on the latest u-boot. I can successfully build u-boot manually, but with buildman I see checkdtc error.

   aarch64:  +   ls2085aqds
(quoted diff) +2 -0
+make[1]: *** [checkdtc] Error 1
+make: *** [sub-make] Error 2

I have DTC 1.4.1-ge5e6df7c. Is there any flag for buildman I can see more information? I always use -vVeu as the flag.

That's not very helpful, sorry. You can always look at the raw logs. You could try an in-tree build with -i if that is what you are using normally.

Regards,
Simon

author
#2 lore raw
Quoted 12 lines · Simon Glass

Hi York,

Quoted 9 lines · York Sun

Simon,

I am facing a weird issue on the latest u-boot. I can successfully build u-boot manually, but with buildman I see checkdtc error.

   aarch64:  +   ls2085aqds
(quoted diff) +2 -0
+make[1]: *** [checkdtc] Error 1
+make: *** [sub-make] Error 2
Quoted 7 lines
Quoted 2 lines

I have DTC 1.4.1-ge5e6df7c. Is there any flag for buildman I can see more information? I always use -vVeu as the flag.

That's not very helpful, sorry. You can always look at the raw logs. You could try an in-tree build with -i if that is what you are using normally.

Simon,

The raw log has been a mystery for me since beginning. Where do I find it? Using -i flag also has the same error message.

York

#3 lore raw

Hi York,

Quoted 23 lines · York Sun
Quoted 12 lines · Simon Glass

Hi York,

Quoted 9 lines · York Sun

Simon,

I am facing a weird issue on the latest u-boot. I can successfully build u-boot manually, but with buildman I see checkdtc error.

   aarch64:  +   ls2085aqds
(quoted diff) +2 -0
+make[1]: *** [checkdtc] Error 1
+make: *** [sub-make] Error 2
Quoted 7 lines
Quoted 2 lines

I have DTC 1.4.1-ge5e6df7c. Is there any flag for buildman I can see more information? I always use -vVeu as the flag.

That's not very helpful, sorry. You can always look at the raw logs. You could try an in-tree build with -i if that is what you are using normally.

Quoted 4 lines

Simon,

The raw log has been a mystery for me since beginning. Where do I find it? Using -i flag also has the same error message.

We really should solve this mystery :-) It's documented in the buildman README.

By default, ../<branch>/<commit>/<board>/

or if you are just building current source it is in ../current

Regards,
Simon

author
#4 lore raw
Quoted 28 lines · Simon Glass

Hi York,

Quoted 25 lines · York Sun
Quoted 12 lines · Simon Glass

Hi York,

Quoted 9 lines · York Sun

Simon,

I am facing a weird issue on the latest u-boot. I can successfully build u-boot manually, but with buildman I see checkdtc error.

   aarch64:  +   ls2085aqds
(quoted diff) +2 -0
+make[1]: *** [checkdtc] Error 1
+make: *** [sub-make] Error 2
Quoted 7 lines
Quoted 2 lines

I have DTC 1.4.1-ge5e6df7c. Is there any flag for buildman I can see more information? I always use -vVeu as the flag.

That's not very helpful, sorry. You can always look at the raw logs. You could try an in-tree build with -i if that is what you are using normally.

Simon,

Quoted 9 lines
Quoted 2 lines

The raw log has been a mystery for me since beginning. Where do I find it? Using -i flag also has the same error message.

We really should solve this mystery :-) It's documented in the buildman README.

By default, ../<branch>/<commit>/<board>/

or if you are just building current source it is in ../current

Thanks, Simon. I didn't use --force-build. So I guess repeat build didn't actually build anything. I found the file "log" but it is empty for a successful build.

York