Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Using nexe@beta on Manjaro Linux errors on checking compiled node binary #354

Closed
1 of 3 tasks
reinaldorauch opened this issue Jul 25, 2017 · 7 comments
Closed
1 of 3 tasks
Labels

Comments

@reinaldorauch
Copy link

This is a

  • Bug Report
  • Feature Request
  • Other

Steps to reproduce:

  • Create a folder, initialize it with npm init and use default settings.
  • Create a index.js file with this content:
    console.log("Hello World");
    
  • Install nexe@beta in project with npm i -D nexe@beta
  • Run npx nexe -i index.js -o index
  • Output would be:
✔ Using input file as the main module: index.js
✔ Node source extracted to: /home/reinaldoacr/projetos/nexe-test/.nexe/8.1.4
✔ Node binary compiled
⠋ Writing result to fileevents.js:182
      throw er; // Unhandled 'error' event
      ^

Error: ENOENT: no such file or directory, open '/home/reinaldoacr/projetos/nexe-test/.nexe/8.1.4/out/Release/node'




Please also provide:

  • Platform(OS/Version):
lsb_release -a
LSB Version:	n/a
Distributor ID:	ManjaroLinux
Description:	Manjaro Linux
Release:	17.0.2
Codename:	Gellivara
uname -a
Linux reinaldo-note-manjaro 4.9.38-1-MANJARO #1 SMP PREEMPT Sat Jul 15 12:04:06 UTC 2017 x86_64 GNU/Linux
  • Host Node Version: v8.1.4
  • Target Node Version: v8.1.4
  • Nexe version: 2.0.0-beta.2
  • Python Version: python 3.6.1, python2 2.7.13
@Tchoumi
Copy link

Tchoumi commented Jul 26, 2017

i think perhaps you should add the version of nexe you are using .some thing like that : nexe -i indexe.js -o logging.exe --version 8.0.0.

@calebboyd
Copy link
Member

Did you try setting -p? Since python is occupied by python 3?

@calebboyd
Copy link
Member

I might see if that can be detected...

@reinaldorauch
Copy link
Author

Yeah, used that and it didn't worked at all. It made the check if I was using python 3 instead python 2 and I had to switch to python2 to be able to get this. Sorry for the late reply.

@calebboyd
Copy link
Member

calebboyd commented Aug 3, 2017

I think this is just a classic node build problem. GYP doesn't always use $PYTHON...
You can probably fix it temporarily by doing the following in the session you're running nexe in.

mkdir -p ~/bin/
ln -s $(which python2) ~/bin/python
export PATH=~/bin/:$PATH

@calebboyd calebboyd added the bug label Aug 3, 2017
@reinaldorauch
Copy link
Author

Oh, I see, will try with that. Thanks :D

@calebboyd
Copy link
Member

I don't think its appropriate for nexe to create a symlink anywhere. So, Instead I'll just make a note of this in the readme

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants