Try SDK version 1.21. Another way is to completely avoid emscipten by installing "faust2" branch (that has the direct faust ==> asm.js backed)
Stéphane Le 11 oct. 2014 à 23:27, Thomas CIPIERRE <[email protected]> a écrit : > Hi Stéphane, > > I do understand. That must be some crazy stuff to keep up with everything. > Thanks for the work you have already done. > I'm currently using emcc 1.25.0 ( with clang 3.3 ), but I have build it from > source so I don't know if I can tell git to switch to an older version… > However, the SDK seems indeed easier for that purpose, I'll take a look. > Which version do you recommand ? > > Thanks for your help. Cheers > > 2014-10-11 21:38 GMT+02:00 Stéphane Letz <[email protected]>: > What version of emscripten area you using? (there is this know problem with > latest version you may have to install an older version of the emscripten > SDK…) > > Stéphane > > > Le 11 oct. 2014 à 14:23, Thomas CIPIERRE <[email protected]> a écrit > : > > > Hi Yann, > > > > Thanks a lot for your quick answer, as always ! > > I did not think about this and that was a very good lead… Indeed I messed > > up with the planetccrma repo installing faust2pd while adding faust. I did > > not think sudoers could link to a different version but I ended with a > > Version 0.9.68 on faust -v and a Version 0.9.46 on sudo faust -v… I removed > > the faust package and sudo version now goes back to Version 0.9.68. > > > > However new troubles have emerged : > > > > [faust/examples]$ sudo faust2webaudioasm noise.dsp > > > > /opt/git/emscripten/tools/eliminator/node_modules/uglify-js/lib/parse-js.js:272 > > throw new JS_Parse_Error(message, line, col, pos); > > ^ > > TypeError: object is not a function > > at new JS_Parse_Error > > (/opt/git/emscripten/tools/eliminator/node_modules/uglify-js/lib/parse-js.js:261:21) > > at js_error > > (/opt/git/emscripten/tools/eliminator/node_modules/uglify-js/lib/parse-js.js:272:15) > > at croak > > (/opt/git/emscripten/tools/eliminator/node_modules/uglify-js/lib/parse-js.js:742:17) > > at token_error > > (/opt/git/emscripten/tools/eliminator/node_modules/uglify-js/lib/parse-js.js:749:17) > > at unexpected > > (/opt/git/emscripten/tools/eliminator/node_modules/uglify-js/lib/parse-js.js:755:17) > > at block_ > > (/opt/git/emscripten/tools/eliminator/node_modules/uglify-js/lib/parse-js.js:998:40) > > at > > /opt/git/emscripten/tools/eliminator/node_modules/uglify-js/lib/parse-js.js:978:43 > > at > > /opt/git/emscripten/tools/eliminator/node_modules/uglify-js/lib/parse-js.js:982:29 > > at > > /opt/git/emscripten/tools/eliminator/node_modules/uglify-js/lib/parse-js.js:1112:43 > > at maybe_unary > > (/opt/git/emscripten/tools/eliminator/node_modules/uglify-js/lib/parse-js.js:1209:27) > > noise.html; > > > > Thanks again. Cheers > > > > 2014-10-11 7:53 GMT+02:00 Yann Orlarey <[email protected]>: > > Hi Thomas, > > > > Which version of Faust are you running ? The -i option was introduced a > > while ago. It inlines, in the generated cpp code, includes such as > > 'faust/gui/JSONUI.h' > > > > Cheers > > > > Yann > > > > > > Le 11/10/2014 04:03, Thomas CIPIERRE a écrit : > >> Dear Faust users, > >> > >> I have switched to Fedora 20 on my laptop and I am finally stuck trying to > >> compile some faust2webaudioasm code. Everything had gone fine, from > >> playing with the repos ( that planetccrma stuff is really interesting! ), > >> to manually and flawlessly building emscripten thanks to their good wiki, > >> and finally building Faust and FaustWorks from git (master branch) with > >> everything compiling under jack, whether with gtk or qt, until I got this > >> error : > >> > >> [faust/examples]$ sudo faust2webaudioasm noise.dsp > >> faust: unrecognized option "-i" > >> noise.cpp:37:10: fatal error: 'faust/gui/JSONUI.h' file not found > >> #include "faust/gui/JSONUI.h" > >> ^ > >> 1 error generated. > >> ERROR root: compiler frontend failed to generate LLVM bitcode, halting > >> noise.html; > >> > >> In case you are wondering, the noise.html only has some HTTP/CSS > >> architecture, but no UI nor DSP of course. Coming from Ubuntu, I have > >> struggled a bit to manage $PATH and some configuration files for both > >> user's and sudoer's commands to work properly, and I am quite sure it has > >> something to do with linking that library to sudoers, all the more that > >> the very JSON.h is already in /usr/local/include/faust/gui/. But I have > >> tried all I could, or maybe my brain is just feeling the weight of hours, > >> so anyone who could help is welcome. > >> > >> Thanks for reading, hoping that might help anyone else, and wishing you > >> all the best. > >> > >> -- > >> Thomas CIPIERRE > >> > >> > >> ------------------------------------------------------------------------------ > >> Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer > >> Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports > >> Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper > >> Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer > >> > >> http://p.sf.net/sfu/Zoho > >> > >> > >> _______________________________________________ > >> Faudiostream-users mailing list > >> > >> [email protected] > >> https://lists.sourceforge.net/lists/listinfo/faudiostream-users > > > > > > ------------------------------------------------------------------------------ > > Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer > > Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports > > Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper > > Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer > > http://p.sf.net/sfu/Zoho > > _______________________________________________ > > Faudiostream-users mailing list > > [email protected] > > https://lists.sourceforge.net/lists/listinfo/faudiostream-users > > > > > > > > > > -- > > Thomas CIPIERRE > > ------------------------------------------------------------------------------ > > Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer > > Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports > > Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper > > Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer > > http://p.sf.net/sfu/Zoho_______________________________________________ > > Faudiostream-users mailing list > > [email protected] > > https://lists.sourceforge.net/lists/listinfo/faudiostream-users > > > > > > -- > Thomas CIPIERRE ------------------------------------------------------------------------------ Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://p.sf.net/sfu/Zoho _______________________________________________ Faudiostream-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/faudiostream-users
