From: Bernd Kuhls <bernd.kuhls@t-online.de>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3 1/2] spidermonkey185: New package.
Date: Mon, 03 Oct 2016 10:40:01 +0200 [thread overview]
Message-ID: <14i9cdxqle.ln2@ID-313208.user.individual.net> (raw)
In-Reply-To: 1467800649-22119-1-git-send-email-nicolas.cavallari@green-communications.fr
Hi,
Am Wed, 06 Jul 2016 12:24:08 +0200 schrieb Nicolas Cavallari:
> diff --git a/package/Config.in b/package/Config.in index
> 15271a2..fdc3194 100644 --- a/package/Config.in +++ b/package/Config.in
> @@ -1306,6 +1306,7 @@ endif
> source "package/qhull/Config.in"
> source "package/qlibc/Config.in"
> source "package/sphinxbase/Config.in"
> + source "package/spidermonkey185/Config.in"
> source "package/startup-notification/Config.in"
> source "package/tz/Config.in"
> source "package/tzdata/Config.in"
after the addition of shapelib
https://git.buildroot.net/buildroot/commit/package/Config.in?
id=2655d676f0151f6cfd36c42435cf84926c209e24
your patch does not apply anymore.
The package fails to compile using this toolchain:
http://autobuild.buildroot.net/toolchains/configs/br-x86-64-core2-
full.config
jsapi.cpp:361:63: error: cannot convert ?__va_list_tag**? to
?__va_list_tag (*)[1]? for argument ?5? to ?JSBool TryArgumentFormatter
(JSContext*, const char**, JSBool, jsval**, __va_list_tag (*)[1])?
JS_ADDRESSOF_VA_LIST(ap))) {
To solve the problem add
printf("#define HAVE_VA_LIST_AS_ARRAY \n");
in js/src/jscpucfg.cpp after line 76 according to
https://groups.google.com/forum/#!topic/jsdb/CnWRh11hRHQ
Regards, Bernd
next prev parent reply other threads:[~2016-10-03 8:40 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-19 15:59 [Buildroot] [RFC/PATCH next 1/2] spidermonkey185: New package Nicolas Cavallari
2016-05-19 15:59 ` [Buildroot] [RFC/PATCH next 2/2] couchdb: " Nicolas Cavallari
2016-05-19 22:41 ` Arnout Vandecappelle
2016-05-20 12:53 ` Thomas Petazzoni
2016-05-20 14:26 ` Nicolas Cavallari
2016-05-20 14:29 ` Thomas Petazzoni
2016-05-20 15:29 ` Bernd Kuhls
2016-06-09 14:46 ` Nicolas Cavallari
2016-06-09 14:46 ` [Buildroot] [PATCH 1/2 v2] spidermonkey185: " Nicolas Cavallari
2016-07-04 21:37 ` Maxime Hadjinlian
2016-07-05 9:46 ` Nicolas Cavallari
2016-07-05 11:03 ` Maxime Hadjinlian
2016-07-06 10:22 ` Nicolas Cavallari
2016-07-06 10:24 ` [Buildroot] [PATCH v3 1/2] " Nicolas Cavallari
2016-07-06 10:24 ` [Buildroot] [PATCH v3 2/2] couchdb: " Nicolas Cavallari
2016-10-03 8:43 ` Bernd Kuhls
2016-10-03 11:44 ` Jeroen Roovers
2016-10-03 12:58 ` Bernd Kuhls
2016-10-03 13:04 ` Jeroen Roovers
2016-10-03 12:06 ` Nicolas Cavallari
2016-10-03 8:40 ` Bernd Kuhls [this message]
2016-10-03 12:07 ` [Buildroot] [PATCH v3 1/2] spidermonkey185: " Nicolas Cavallari
2016-10-16 10:01 ` Thomas Petazzoni
2017-08-06 16:48 ` Bernd Kuhls
2016-06-09 14:46 ` [Buildroot] [PATCH 2/2 v2] couchdb: " Nicolas Cavallari
2016-05-19 23:09 ` [Buildroot] [RFC/PATCH next 1/2] spidermonkey185: " Arnout Vandecappelle
2016-05-20 13:59 ` Nicolas Cavallari
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=14i9cdxqle.ln2@ID-313208.user.individual.net \
--to=bernd.kuhls@t-online.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