From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/3] package/nodejs: bump 0.10.x branch to version 0.10.41
Date: Sun, 13 Dec 2015 22:18:57 +0100 [thread overview]
Message-ID: <20151213221857.602779ce@free-electrons.com> (raw)
In-Reply-To: <566DD825.3000105@mind.be>
Arnout,
On Sun, 13 Dec 2015 21:42:13 +0100, Arnout Vandecappelle wrote:
> I guess, when BR2_ARM_FPU_VFPV3 of _D16 is selected, we should also select
> BR2_ARM_CPU_HAS_VFPV3. Which is of course not possible because then we get a
> circular dependency. So more hidden intermediate symbols...
Yes, the FPU selection is not yet good. If you have selected a VFPv3,
then of course your VFP is compatible with VFPv2, so the corresponding
symbols should be selected.
We need to rethink a bit these VFP Config.in options to make this work
properly.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2015-12-13 21:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-08 21:18 [Buildroot] [PATCH 1/3] package/nodejs: bump 0.10.x branch to version 0.10.41 Jörg Krause
2015-12-08 21:18 ` [Buildroot] [PATCH 2/3] package/nodejs: bump 0.12.x branch to version 0.12.9 Jörg Krause
2015-12-08 21:18 ` [Buildroot] [PATCH 3/3] package/nodejs: bump 4.x branch to version 4.2.3 Jörg Krause
2015-12-12 17:32 ` [Buildroot] [PATCH 1/3] package/nodejs: bump 0.10.x branch to version 0.10.41 Thomas Petazzoni
2015-12-13 20:42 ` Arnout Vandecappelle
2015-12-13 21:18 ` Thomas Petazzoni [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=20151213221857.602779ce@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--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.