All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 6986] New: Make legal-info fails on uboot versions before 2014.01
Date: Mon, 24 Mar 2014 19:36:47 +0000 (UTC)	[thread overview]
Message-ID: <bug-6986-163@https.bugs.busybox.net/> (raw)

https://bugs.busybox.net/show_bug.cgi?id=6986

           Summary: Make legal-info fails on uboot versions before 2014.01
           Product: buildroot
           Version: 2014.02
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: minor
          Priority: P5
         Component: Other
        AssignedTo: unassigned at buildroot.uclibc.org
        ReportedBy: mstarr at hedonline.com
                CC: buildroot at uclibc.org
   Estimated Hours: 0.0


In buildroot 2014.02, selecting U-Boot version as custom and then entering a
version before 2014.01 results in 'make legal-info' failing with the following
message:

build/uboot-2013.07/Licenses/gpl-2.0.txt: No such file or directory

This appears to be a change made in the following commit:
http://git.buildroot.net/buildroot/commit/boot/uboot/uboot.mk?id=eb9b1f50281b4e0c3363923d461d57a165e8be15

Can this be changed to look for the COPYING file at the root of the uboot
directory for versions before 2014.01 and use the new Licenses/gpl-2.0.txt for
version 2014.01 and after?

-- 
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

             reply	other threads:[~2014-03-24 19:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-24 19:36 bugzilla at busybox.net [this message]
2014-03-24 20:20 ` [Buildroot] [Bug 6986] Make legal-info fails on uboot versions before 2014.01 bugzilla at busybox.net
2014-03-24 20:35 ` bugzilla at busybox.net
2014-03-25  7:31 ` bugzilla at busybox.net
2014-03-25 13:25 ` bugzilla at busybox.net

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-6986-163@https.bugs.busybox.net/ \
    --to=bugzilla@busybox.net \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.