On 10/24/2018 05:44 PM, Ken Moffat via blfs-dev wrote:
On Thu, Oct 25, 2018 at 12:21:37AM +0200, Tim Tassonis via blfs-dev wrote:
Hi all


Just tried to build firefox 63.0 and got the folllowing error:


-12:10.16 /lgl-bld/firefox-63.0/js/src/vm/JSContext-inl.h:180:73: error: no
‘void JSContext::checkImpl_63(int, const Head&, const Tail& ...)’ member
function declared in class ‘JSContext’
12:10.16  JSContext::checkImpl(int argIndex, const Head& head, const
Tail&... tail)
12:10.16

I got a similar error in the same place:

/mnt/tmp/firefox/firefox-63.0/js/src/vm/JSContext-inl.h:180:1: error: no declaration matches ‘void JSContext::checkImpl_63(int, const Head&, const Tail& ...)’ 0:06.42 JSContext::checkImpl(int argIndex, const Head& head, const Tail&... tail)

I do have node-v9.11.2 installed.
Using gcc 8.2.

grepping for JSContext::checkImpl only finds a match in js/src/vm/JSContext-inl.h

I could find nothing similar to JSContext::checkImpl in /usr/include

  -- Bruce



I'm fully aware that this is my problem,  just thought maybe someone else
stumbled on this an knows a fix.

This is with gcc 7.3.0 and the system_graphite2_harfbuzz-1 patch, but
without node.js


As I think I said in the ticket, I get the same with gcc-7.3.0.
With a system from May using gcc-8.1 everything was fine so it seems
to be a gcc-7 problem.

No idea what distros will be doing.  Talking of problems, I'll also
mention that in _early_ betas I used clang/clang++ (saved space, but
not time), but that fell apart (looked like C++ scope problems, but
not fixed by playing with the possible switches.

So, for gcc-7.3.0 all I can do is recommend building 60.3.0esr with
the config we used to use for the 60 series and the later (60.2?)
system graphite patch (but not the ffmpeg patch, my old systems were
using ffmpeg-3.4.2).  Tested with current rustc, because I'd already
updated those old systems.

If there is a fix, that would be good.

ĸen


--
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Reply via email to