From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] BR2_EXTERNAL: check it is a valid BR2_EXTERNAL dir before using it
Date: Wed, 22 Jan 2014 19:55:57 +0100 [thread overview]
Message-ID: <20140122185557.GB3592@free.fr> (raw)
In-Reply-To: <1751679476.4596486.1390381240766.JavaMail.root@openwide.fr>
J?r?my, All,
On 2014-01-22 10:00 +0100, Jeremy Rosen spake thusly:
> ok, I tried your patch and I have a couple of problems
[--SNIP--]
> rosen at pcrosen:~/tmp/buildroot$ LANG=C make O=.. BR2_EXTERNAL=.. raspberrypi_defconfig
> Makefile:126: *** BR2_EXTERNAL='..' does not exist, relatively to /home/rosen/tmp/buildroot. Stop.
OK, that one's fixed.
> Which is a confusing error message, the problem is that I don't have
> a Config.in and external.mk file in tmp /(which are mandatory in
> BR2_EXTERNAL though that's not stated in the doc afaics)
Ah, right. They do be mandatory. I'll update the doc accordingly, so it
is explicit one has to provide both in an br2-external tree.
Thanks for the review and testing! :-)
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
prev parent reply other threads:[~2014-01-22 18:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-21 21:04 [Buildroot] [PATCH] BR2_EXTERNAL: check it is a valid BR2_EXTERNAL dir before using it Yann E. MORIN
2014-01-22 9:00 ` Jeremy Rosen
2014-01-22 10:21 ` yann.morin.1998 at free.fr
2014-01-22 12:43 ` Jeremy Rosen
2014-01-22 21:10 ` Yann E. MORIN
2014-01-22 18:55 ` Yann E. MORIN [this message]
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=20140122185557.GB3592@free.fr \
--to=yann.morin.1998@free.fr \
--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