Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Jörg Krause" <jkrause@posteo.de>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/nodejs: fix hard float error
Date: Mon, 12 Jan 2015 21:42:18 +0100	[thread overview]
Message-ID: <1421095338.1971.1.camel@posteo.de> (raw)
In-Reply-To: <20150112123342.5b5a616c@free-electrons.com>

Hello Thomas,

On Mo, 2015-01-12 at 12:33 +0100, Thomas Petazzoni wrote:
> Dear J?rg Krause,
> 
> On Sun, 11 Jan 2015 22:04:19 +0100, J?rg Krause wrote:
> 
> > diff --git a/package/nodejs/nodejs.mk b/package/nodejs/nodejs.mk
> > index ad598d9..3389c3c 100644
> > --- a/package/nodejs/nodejs.mk
> > +++ b/package/nodejs/nodejs.mk
> > @@ -56,14 +56,16 @@ else ifeq ($(BR2_mipsel),y)
> >  NODEJS_CPU = mipsel
> >  else ifeq ($(BR2_arm),y)
> >  NODEJS_CPU = arm
> > -# V8 needs to know what floating point ABI the target is using.  There's also
> > -# a 'hard' option which we're not exposing here at the moment, because
> > -# buildroot itself doesn't really support it at present.
> > +# V8 needs to know what floating point ABI the target is using.
> > +ifeq ($(BR2_ARM_EABIHF),y)
> > +NODEJS_ARM_FP = hard
> > +else
> >  ifeq ($(BR2_SOFT_FLOAT),y)
> >  NODEJS_ARM_FP = soft
> >  else
> >  NODEJS_ARM_FP = softfp
> > -endif
> > +endif # BR2_SOFT_FLOAT
> > +endif # BR2_ARM_EABIHF
> >  endif
> 
> Why don't we simply do:
> 
> NODEJS_ARM_FP = $(BR2_GCC_TARGET_FLOAT_ABI)

Nice, I one-liner :-) Didn't know about BR2_GCC_TARGET_FLOAT_ABI, but
it's exactly what we need. I submit a second version soon.

Best regards
J?rg

      reply	other threads:[~2015-01-12 20:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-11 21:04 [Buildroot] [PATCH 1/1] package/nodejs: fix hard float error Jörg Krause
2015-01-12 11:33 ` Thomas Petazzoni
2015-01-12 20:42   ` Jörg Krause [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=1421095338.1971.1.camel@posteo.de \
    --to=jkrause@posteo.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