From: Stephan Hoffmann <sho@relinux.de>
To: buildroot@busybox.net
Subject: [Buildroot] make legal-info fails when override is active
Date: Thu, 11 Oct 2012 10:19:34 +0200 [thread overview]
Message-ID: <50768116.4000506@relinux.de> (raw)
Hello all,
in my setup using the override srcdir feature for the kernel make
legal-info fails.
> make legal-info
> >>> Collecting legal info
> make: *** No rule to make target `linux-extract', needed by
> `linux-legal-info'. Stop.
Tested with actual git head (526badc94)
Kind regards
Stephan
--
reLinux - Stephan Hoffmann
Am Schmidtgrund 124 50765 K?ln
Tel. +49.221.95595-19 Fax: -64
www.reLinux.de sho at reLinux.de
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: defconfig
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20121011/573c0fce/attachment.ksh>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: local.mk
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20121011/573c0fce/attachment-0001.ksh>
next reply other threads:[~2012-10-11 8:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-11 8:19 Stephan Hoffmann [this message]
2012-10-14 14:41 ` [Buildroot] [PATCH] pkg-infra: rename <pkg>-rsync to <pkg>-extract Arnout Vandecappelle
2012-10-14 18:01 ` Thomas Petazzoni
2012-10-14 21:00 ` Arnout Vandecappelle
2012-10-14 21:06 ` Thomas Petazzoni
2012-10-14 21:19 ` [Buildroot] [PATCH v2] pkg-infra: add <pkg>-extract and <pkg>-patch targets to OVERRIDE support Arnout Vandecappelle
2012-10-14 21:42 ` Thomas Petazzoni
2012-10-15 12:38 ` Luca Ceresoli
2012-11-12 8:27 ` [Buildroot] [PATCH] pkg-infra: rename <pkg>-rsync to <pkg>-extract Stephan Hoffmann
2012-11-13 23:48 ` Arnout Vandecappelle
2012-11-14 8:20 ` Stephan Hoffmann
2012-12-03 9:58 ` Stephan Hoffmann
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=50768116.4000506@relinux.de \
--to=sho@relinux.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox