node-packer icon indicating copy to clipboard operation
node-packer copied to clipboard

detect simultaneous runs of nodec

Open raguay opened this issue 7 years ago • 7 comments

Hi,

If you create the smallest script using the https://github.com/scottgonzalez/node-wordpress library to post a post to a WordPress site, it will not compile. It dies with this message:

clang: error: linker command failed with exit code 1 (use -v to see invocation) make[1]: *** [/private/var/folders/7m/t5j9b17x4n9gkml89tck1s4c0000gn/T/nodec/node/out/Release/mksnapshot] Error 1 rm de7168347652b3d5f6d7374947b15853a841ec81.intermediate make: *** [node] Error 2 Failed running ["make -j4"]

I've done a few other scripts that are just as small and they compile fine. But, add this library and call it it will not compile. The script runs fine using node, but if you browserify it, it no longer works. I bet that points to an issue with the library?

BTW: It took around an hour to try to compile it. That library must be very complicated.

raguay avatar May 12 '17 12:05 raguay

@raguay Sorry for the delayed reply. I failed to reproduce this error on my local machine. I tried the Found xxx posts example on the node-wordpress readme and it works fine both before compiling and after compiling.

Could you give me more of your error log? Something is hidden before the sentence "linker command failed with exit code". I need the error message of the linker in order to diagnose. Thanks.

image

image

pmq20 avatar May 16 '17 05:05 pmq20

Well, it's working now. Not sure what's different....other than I wasn't running another compile at the same time. Could using nodec in two different project cause a problem?

On Tue, May 16, 2017 at 12:08 PM, Minqi Pan [email protected] wrote:

@raguay https://github.com/raguay Sorry for the delayed reply. I failed to reproduce this error on my local machine. I tried the Found xxx posts example on the node-wordpress readme and it works fine both before compiling and after compiling. Could you give me more of your error log? Something is hidden before the sentence "linker command failed with exit code". I need the error message of the linker. Thanks.

[image: image] https://cloud.githubusercontent.com/assets/13315/26090601/99e340a0-3a38-11e7-9b8d-6edd679bcbb0.png

[image: image] https://cloud.githubusercontent.com/assets/13315/26090603/a233b398-3a38-11e7-922d-e7b8e76581d3.png

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/pmq20/node-compiler/issues/31#issuecomment-301676875, or mute the thread https://github.com/notifications/unsubscribe-auth/ACX0x-6Pajnuav8KRAjoSCIz1kqdt5Lvks5r6S9kgaJpZM4NZN1r .

raguay avatar May 16 '17 08:05 raguay

@raguay Probably. nodec is not designed to run simultaneously at the moment, as the compile process would reuse the same set of temporary object files, which is potentially problematic. Thanks for reporting!

pmq20 avatar May 17 '17 03:05 pmq20

Okay. Thanks.

On Wed, May 17, 2017 at 10:24 AM, Minqi Pan [email protected] wrote:

@raguay https://github.com/raguay Probably. nodec is not designed to run simultaneously for the moment, as the compile process would reuse the same set of temporary object files, which is potentially problematic. Thanks for reporting!

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/pmq20/node-compiler/issues/31#issuecomment-301974847, or mute the thread https://github.com/notifications/unsubscribe-auth/ACX0x8CUr3EnSL1010z6vmZ8iduxRu10ks5r6mhmgaJpZM4NZN1r .

raguay avatar May 17 '17 03:05 raguay

nodec should detect this and give a proper error message though. I'll add this to https://github.com/pmq20/node-compiler/blob/master/ROADMAP.md

pmq20 avatar May 17 '17 03:05 pmq20

@pmq20 Hello, I'm not sure about nodec's command. Can you help me? image

oneFlyingSnail avatar May 22 '17 08:05 oneFlyingSnail

@oneFlyingSnail You could try downloading https://sourceforge.net/projects/node-compiler/files/v0.9.6/nodec.exe/download and putting it inside C:\Windows to make it available every where.

pmq20 avatar May 22 '17 09:05 pmq20