From: Romain Naour <romain.naour@openwide.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] prevent recursion in %_defconfig rules
Date: Mon, 20 Jan 2014 23:58:28 +0100 [thread overview]
Message-ID: <52DDAA14.5060307@openwide.fr> (raw)
In-Reply-To: <748467273.4509268.1390205590826.JavaMail.root@openwide.fr>
Le 20/01/2014 09:13, Jeremy Rosen a ?crit :
> aaand reproduced.
>
> following the steps described, I get that problem systematically
>
> I use make 3.81 (debian testing) and I'm not sure what else is
> involved when crashing that early.
>
>
> I tried with LANG=C in case there was anything weird, but apparently not
>
> My make skills are not very high so i'll gladly take any help on
> figuring that one out...
>
> Cordialement
>
> J?r?my Rosen
> +33 (0)1 42 68 28 04
>
> fight key loggers : write some perl using vim
>
>
> Open Wide Ingenierie
>
> 23, rue Daviel
> 75012 Paris - France
> www.openwide.fr
>
>
>
>
>
> ----- Mail original -----
>>>> J?r?my, can you describe your setup, so we can try to reproduce
>>>> it,
>>>> and
>>>> find a proper fix?
>>
>> Ok, i'll look into it and try to figure out...
>>
>> it's really weird that you were not able to reproduce with the steps
>> in the patch, it was pretty systematic for me. I'll try to reproduce
>> and report whatever I find
>>
Hi J?r?my, Yann
I'm able to reproduce the issue here.
There is no specific setup, I used my current buildroot directory and run:
make O=.. BR2_EXTERNAL=.. raspberrypi_defconfig
make: stat: /home/naourr/git/buildroot/configs/../configs/../configs/..
[snip]
../configs/raspberrypi_defconfig ?. Stop
Or
make O=../output BR2_EXTERNAL=.. raspberrypi_defconfig
make: stat: /home/naourr/git/buildroot/configs/../configs/../configs/..
[snip]
../configs/raspberrypi_defconfig ?. Stop
But it's ok with :
make O=../output BR2_EXTERNAL=../external raspberrypi_defconfig GEN
../output/Makefile
#
# configuration written to ../output/.config
#
I have no solution currently, but I hope this help...
Yann, what's wrong with relative path for BR2_EXTERNAL or O ?
Best regards,
Romain Naour
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20140120/bc34c76b/attachment.html>
next prev parent reply other threads:[~2014-01-20 22:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-07 16:22 [Buildroot] [PATCH] prevent recursion in %_defconfig rules Jérémy Rosen
2014-01-13 8:52 ` Jeremy Rosen
2014-01-13 8:59 ` Peter Korsgaard
2014-01-17 17:52 ` Yann E. MORIN
2014-01-17 18:09 ` Yann E. MORIN
2014-01-17 19:54 ` Yann E. MORIN
2014-01-20 8:03 ` Jeremy Rosen
2014-01-20 8:13 ` Jeremy Rosen
2014-01-20 18:31 ` Yann E. MORIN
2014-01-20 22:58 ` Romain Naour [this message]
2014-01-20 23:58 ` Yann E. MORIN
2014-01-21 8:44 ` Jeremy Rosen
2014-01-21 18:38 ` Yann E. MORIN
2014-01-22 14:16 ` Jeremy Rosen
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=52DDAA14.5060307@openwide.fr \
--to=romain.naour@openwide.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