laverdet / node-fibers

Fiber/coroutine support for v8 and node.
MIT License
3.56k stars 224 forks source link

Dockerfile build failed on fibers.cc #439

Open DinoRavasi opened 4 years ago

DinoRavasi commented 4 years ago

Ciao. I've installed syncronized with fibers as dependency. Locally works fine.

When i push my project on cloud server i receive this error :

============================================= Git checkout finished

S2I process starting

Coping files from /tmp/builder/bb3b0e63-9eb4-404c-8faa-fcbfe97312b5

docker pull quay-enterprise-quay-enterprise.quay-enterprise-d-307161-c3d6e5e87e1b5b53c8cbab7b29828047-0001.us-south.containers.appdomain.cloud/ubi8/nodejs-12:latest Getting image source signatures Copying blob sha256:58e1deb9693dfb1704ccce2f1cf0e4d663ac77098a7a0f699708a71549cbd924 Copying blob sha256:1d3caaab0e6b8f6421152e3e992b9af724fb775da1fbc232ce24b02d5a910efd Copying blob sha256:78afc5364ad2c981e4a4919f535aaefef9ac2f990837be01c766764e025b1f31 Copying blob sha256:aa41501e6e69a046f2a4f9a9fec52c122e09431a8455b24cc923934121f28467 Copying blob sha256:5ac1bc78931d075c646f8504d7a39707e21aa267e5d496bcb735d233d96d6004 Copying config sha256:6fbd181943ff13ce41e5ef385388879a3d90b45fdff48b2baf0aede44a593e1b Writing manifest to image destination Storing signatures

S2I image inspect completed

S2I process - building container

Dockerfile build failed - exit status 1 -> ../src/fibers.cc:68:2: error: 'Handle' does not name a type; did you mean 'rand_r'? Handle NewLatin1String(Isolate isolate, const char string) { ^~ rand_r ../src/fibers.cc:72:2: error: 'Handle' does not name a type; did you mean 'rand_r'? Handle NewLatin1Symbol(Isolate isolate, const char string) { ^~ rand_r ../src/fibers.cc:94:2: error: 'Handle' does not name a type; did you mean 'rand_r'? Handle NewInstance(Isolate* isolate, Local fn, int argc, Local argv[]) { ^~

the s2i image in question runs on RedHat UBI8

can you help ?

Thanks.

Dino