Skip to contentSkip to conversation

u-boot 2013.10 LIC_FILES_CHKSUM points to an invalid file

DISCUSSION Robert Berger 3 participants 4 messages Dec 23, 2013 – Dec 24, 2013

lore
Share & tools
lore
#0 lore raw

Hi,

I try to build instead of u-boot v2013.07 [1] the latest and greatest released version i.e. v2013.10[2].

... which does not build because LIC_FILES_CHKSUM points to an invalid file ...

... and yes it does, since the COPYING file is gone ...

The licencense info is contained in the source code itself as SPDX-License-Identifiers.

How do I get it to build?

Regards,

Robert

[1]
http://git.denx.de/?p=u-boot.git;a=tree;h=63e74bc767dda75feff521c40b779018397fe1e7;hb=62c175fbb8a0f9a926c88294ea9f7e88eb898f6c

[2]
http://git.denx.de/?p=u-boot.git;a=tree;h=b6756a15fd1e165107adf57e7c4a393f7dbcba38;hb=183acb700378a8cfc5d50a01a65de93fb2c24586..."In
C++ it's harder to shoot yourself in the foot, but when you do, you blow off your whole leg." - Bjarne Stroustrup

My public pgp key is available,at:
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x90320BF1

#1 lore raw

Hi Robert,

Quoted 10 lines · On Monday 23 December 2013 22:47:00 Robert Berger wrote:

I try to build instead of u-boot v2013.07 [1] the latest and greatest released version i.e. v2013.10[2].

... which does not build because LIC_FILES_CHKSUM points to an invalid file ...

... and yes it does, since the COPYING file is gone ...

The licencense info is contained in the source code itself as SPDX-License-Identifiers.

Hmm, I'm not sure upstream should really have removed it, but I guess it's up to them...

Quoted 1 line

How do I get it to build?

In the absence of any other license statement, you'd have to point to one or more of the source files and use beginline and endline to select just the part of the header specifying the license.

Cheers,
Paul

Signature · 2 lines
Paul Eggleton
Intel Open Source Technology Centre
#2 lore raw

Hi Paul,

Quoted 6 lines · Paul Eggleton
Quoted 2 lines

How do I get it to build?

In the absence of any other license statement, you'd have to point to one or more of the source files and use beginline and endline to select just the part of the header specifying the license.

Thanks!

This might be tricky to know upfront in same cases and would in worst case require different recipes with different license info since it depends on what configuration you build for, or which files are being included.

A mechanism to extract the relevant info from the executable is most likely more accurate.

But I guess not we have a chicken and egg problem ;)

Quoted 4 lines

Cheers,
Paul

Regards,

Robert

..."My employer doesn't even agree with me about C indentation style." - Used as a disclaimer

My public pgp key is available,at:
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x90320BF1

#3 lore raw
In reply to Paul Eggleton

Am 23.12.2013 21:56, schrieb Paul Eggleton:

Quoted 9 lines

Hi Robert,

Quoted 6 lines · On Monday 23 December 2013 22:47:00 Robert Berger wrote:

I try to build instead of u-boot v2013.07 [1] the latest and greatest released version i.e. v2013.10[2].

... which does not build because LIC_FILES_CHKSUM points to an invalid file ...

Quoted 6 lines
Quoted 4 lines

... and yes it does, since the COPYING file is gone ...

The licencense info is contained in the source code itself as SPDX-License-Identifiers.

Hmm, I'm not sure upstream should really have removed it, but I guess it's up to them...

The project switch to the Software Package Data Exchange (SPDX) and move the license information in a Licenses directory.