Incoming javascript and wasm packages
Hello everyone, I am looking at adding a few packages to Factory soon. To start with: * binaryen <https://build.opensuse.org/request/show/853081> * quickjs <https://build.opensuse.org/package/show/devel:tools:compiler/quickjs> The quickjs compiler is now in devel. The more common use case for quickjs <https://bellard.org/quickjs/> seems to be embedding it yourself. However, it now includes a number of CLI apps, so I created a small package. By the way thanks for reviewing the submission Pluskalm and Andreas! Sharing a learning about optflags: passing the optflags can be tricky, and even trickier still is validating that it was passed correctly. For this, I found it helpful to check the build log. If the defaults are getting passed, you should see FORTIFY_SOURCE=2 getting passed around quite a bit. Also, I am having a look at building: * deno <https://build.opensuse.org/package/show/home:avindra/deno#comment-1368472> * emscripten <https://build.opensuse.org/package/show/home:avindra/emscripten> If anyone has a good idea of why the deno build is getting killed and if there is a workaround, please let me know. Thanks, avindra goolcharan
Hi, Am Freitag, 4. Dezember 2020, 22:14:15 CET schrieb Avindra Goolcharan: ....
Also, I am having a look at building:
* deno <https://build.opensuse.org/package/show/home:avindra/deno#comment-1368472> * emscripten <https://build.opensuse.org/package/show/home:avindra/emscripten>
If anyone has a good idea of why the deno build is getting killed and if there is a workaround, please let me know.
looks like it runs out of memory. You should add a _contraints file to your setup, and include something like <?xml version="1.0" encoding="UTF-8"?> <constraints> <hardware> <disk> <size unit="G">13</size> </disk> <memory> <size unit="M">3000</size> </memory> <memoryperjob> <size unit="M">1000</size> </memoryperjob> </hardware> </constraints> -> start small and increase memory if this still happens HTH Axel
Thanks Axel for the _constraints tip re: OOM. Happy new year to everyone, and to follow up on this topic: I have staged the seed of a new repo for JavaScript here: https://build.opensuse.org/project/show/home:avindra:devel:languages:javascr... I would suggest calling it *devel:languages:javascript* to line up with existing language projects but open to other ideas. I suggest taking esbuild, deno and hermes to Factory, and any other packages people want to see. avindra goolcharan On Sun, Dec 6, 2020 at 7:00 AM Axel Braun <axel.braun@gmx.de> wrote:
Hi,
Am Freitag, 4. Dezember 2020, 22:14:15 CET schrieb Avindra Goolcharan:
....
Also, I am having a look at building:
* deno < https://build.opensuse.org/package/show/home:avindra/deno#comment-1368472> * emscripten <https://build.opensuse.org/package/show/home:avindra/emscripten>
If anyone has a good idea of why the deno build is getting killed and if there is a workaround, please let me know.
looks like it runs out of memory. You should add a _contraints file to your setup, and include something like
<?xml version="1.0" encoding="UTF-8"?> <constraints> <hardware> <disk> <size unit="G">13</size> </disk> <memory> <size unit="M">3000</size> </memory> <memoryperjob> <size unit="M">1000</size> </memoryperjob> </hardware> </constraints>
-> start small and increase memory if this still happens
HTH Axel _______________________________________________ openSUSE Factory mailing list -- factory@lists.opensuse.org To unsubscribe, email factory-leave@lists.opensuse.org List Netiquette: https://en.opensuse.org/openSUSE:Mailing_list_netiquette List Archives: https://lists.opensuse.org/archives/list/factory@lists.opensuse.org
On 05/01/2021 00.40, Avindra Goolcharan wrote:
Thanks Axel for the _constraints tip re: OOM.
Happy new year to everyone, and to follow up on this topic:
I have staged the seed of a new repo for JavaScript here:
https://build.opensuse.org/project/show/home:avindra:devel:languages:javascr... <https://build.opensuse.org/project/show/home:avindra:devel:languages:javascript>
I would suggest calling it *devel:languages:javascript* to line up with existing language projects but open to other ideas.
To me, devel:languages:javascript makes sense. devel:languages:nodejs is only slightly related. I appreciate your work towards packaging emscripten. I once used it to compile webperl[1] and it was not exactly straightforward. [1] http://www.zq1.de/webperl/regex_tester.html
On 1/4/2021 16:40, Avindra Goolcharan wrote:
Thanks Axel for the _constraints tip re: OOM.
Happy new year to everyone, and to follow up on this topic:
I have staged the seed of a new repo for JavaScript here:
https://build.opensuse.org/project/show/home:avindra:devel:languages:javascr...
I would suggest calling it *devel:languages:javascript* to line up with existing language projects but open to other ideas.
Is "devel:languages:js" a possibility for brevity's sake? -- Jason Craig
js would be fine by me! More info I've gathered on hermes which is fairly new: The hermes engine itself has a connection with React Native. There is a section on this in the RN docs: https://reactnative.dev/docs/hermes More interesting than React however is that it uses an IR: https://hermesengine.dev/docs/ir The IR reminds me of llvm. I wonder how far off we are from building JS with clang ;) avindra goolcharan On Wed, Jan 6, 2021 at 12:16 PM Jason Craig <os-dev@jacraig.com> wrote:
On 1/4/2021 16:40, Avindra Goolcharan wrote:
Thanks Axel for the _constraints tip re: OOM.
Happy new year to everyone, and to follow up on this topic:
I have staged the seed of a new repo for JavaScript here:
https://build.opensuse.org/project/show/home:avindra:devel:languages:javascr...
I would suggest calling it *devel:languages:javascript* to line up with existing language projects but open to other ideas.
Is "devel:languages:js" a possibility for brevity's sake?
-- Jason Craig
Am 07.01.21 um 08:55 schrieb Avindra Goolcharan:
js would be fine by me!
More info I've gathered on hermes which is fairly new:
The hermes engine itself has a connection with React Native. There is a section on this in the RN docs:
https://reactnative.dev/docs/hermes <https://reactnative.dev/docs/hermes>
More interesting than React however is that it uses an IR:
https://hermesengine.dev/docs/ir <https://hermesengine.dev/docs/ir>
The IR reminds me of llvm. I wonder how far off we are from building JS with clang ;)
Both are SSA-based, but this one seems to have optional types whereas in LLVM types aren't optional. So this doesn't seem trivial to me, to put it mildly. It's generally hard to compile dynamically typed (like JavaScript) code into a statically typed language (like C++ or LLVM IR). When you can't derive a static type you'll at least need a type switch and in the worst case you'll have to look up symbols at runtime. Also note that Clang is an (Objective-)C/C++ compiler frontend, so that would certainly not be involved. Best regards, Aaron
Thanks for the insight. I guess translating the code that uses the very general "number" type might be a challenge too. avindra goolcharan On Thu, Jan 7, 2021 at 6:21 PM Aaron Puchert <aaronpuchert@alice-dsl.net> wrote:
Am 07.01.21 um 08:55 schrieb Avindra Goolcharan:
js would be fine by me!
More info I've gathered on hermes which is fairly new:
The hermes engine itself has a connection with React Native. There is a section on this in the RN docs:
https://reactnative.dev/docs/hermes <https://reactnative.dev/docs/hermes
More interesting than React however is that it uses an IR:
https://hermesengine.dev/docs/ir <https://hermesengine.dev/docs/ir>
The IR reminds me of llvm. I wonder how far off we are from building JS with clang ;)
Both are SSA-based, but this one seems to have optional types whereas in LLVM types aren't optional. So this doesn't seem trivial to me, to put it mildly. It's generally hard to compile dynamically typed (like JavaScript) code into a statically typed language (like C++ or LLVM IR). When you can't derive a static type you'll at least need a type switch and in the worst case you'll have to look up symbols at runtime.
Also note that Clang is an (Objective-)C/C++ compiler frontend, so that would certainly not be involved.
Best regards, Aaron
On 1/7/21 3:45 AM, Jason Craig wrote:
On 1/4/2021 16:40, Avindra Goolcharan wrote:
Thanks Axel for the _constraints tip re: OOM.
Happy new year to everyone, and to follow up on this topic:
I have staged the seed of a new repo for JavaScript here:
https://build.opensuse.org/project/show/home:avindra:devel:languages:javascr...
I would suggest calling it *devel:languages:javascript* to line up with existing language projects but open to other ideas.
Is "devel:languages:js" a possibility for brevity's sake?
Its slightly less consistent with what we have you can always abbreviate it when talking about it, for example on the python list most people just write d:l:p instead of devel:lanaguages:python -- Simon Lees (Simotek) http://simotek.net Emergency Update Team keybase.io/simotek SUSE Linux Adelaide Australia, UTC+10:30 GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B
On 1/7/2021 16:29, Simon Lees wrote:
On 1/7/21 3:45 AM, Jason Craig wrote:
On 1/4/2021 16:40, Avindra Goolcharan wrote:
Thanks Axel for the _constraints tip re: OOM.
Happy new year to everyone, and to follow up on this topic:
I have staged the seed of a new repo for JavaScript here:
https://build.opensuse.org/project/show/home:avindra:devel:languages:javascr...
I would suggest calling it *devel:languages:javascript* to line up with existing language projects but open to other ideas.
Is "devel:languages:js" a possibility for brevity's sake?
Its slightly less consistent with what we have you can always abbreviate it when talking about it, for example on the python list most people just write d:l:p instead of devel:lanaguages:python
Fair enough. It was a suggestion, I'm OK with what the community finds best. -- Jason Craig
participants (6)
-
Aaron Puchert -
Avindra Goolcharan -
Axel Braun -
Bernhard M. Wiedemann -
Jason Craig -
Simon Lees