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

pkg-fetch cannot be built for freebsd, time to switch from pkg-fetch for freebsd? #6

Open
srappan opened this issue Oct 11, 2019 · 9 comments
Labels
bug Something isn't working

Comments

@srappan
Copy link

srappan commented Oct 11, 2019

Unfortunatley, the project seems uninterested to support freebsd further, might be time to switch alternative for the pkg-fetch.

[email protected] start /root/UnicornFFMPEG
pkg . -o "bin/Plex Transcoder"

[email protected]
Fetching base Node.js binaries to PKG_CACHE_PATH
fetched-v10.15.3-freebsd-x64 [ ] 0%
Error! 404 Not Found
https://github.com/zeit/pkg-fetch/releases/download/v2.6/uploaded-v2.6-node-v10.15.3-freebsd-x64
Asset not found by direct link:
{"tag":"v2.6","name":"uploaded-v2.6-node-v10.15.3-freebsd-x64"}
Not found in GitHub releases:
{"tag":"v2.6","name":"uploaded-v2.6-node-v10.15.3-freebsd-x64"}
Building base binary from source:
built-v10.15.3-freebsd-x64
Cloning Node.js repository from GitHub...
git [====================] 100%
Checking out v10.15.3
Applying patches
Compiling Node.js from sources...
WARNING: failed to autodetect C++ compiler version (CXX=g++)
WARNING: failed to autodetect C compiler version (CC=gcc)
ERROR: No acceptable C compiler found!
Please make sure you have a C compiler installed on your system and/or
consider adjusting the CC environment variable if you installed
it in a non-standard prefix.
Error! Error: ./configure failed with code 1
at ChildProcess. (/root/UnicornFFMPEG/node_modules/pkg-fetch/lib-es5/spawn.js:68:23)
at ChildProcess.emit (events.js:198:13)
at maybeClose (internal/child_process.js:982:16)
at Process.ChildProcess._handle.onexit (internal/child_process.js:259:5)
npm ERR! code ELIFECYCLE
npm ERR! errno 2
npm ERR! [email protected] start: pkg . -o "bin/Plex Transcoder"
npm ERR! Exit status 2
npm ERR!
npm ERR! Failed at the [email protected] start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
1

Github Issues raised on pkg-fetch for this particular issue have gone unanswered

@Maxou44
Copy link
Member

Maxou44 commented Oct 11, 2019

Do you have ideas about pkg alternatives for freebsd?

@Maxou44
Copy link
Member

Maxou44 commented Oct 11, 2019

BTW it looks like a compilation issue on your side, try to install gcc / g++ / clang to build the package yourself

@srappan
Copy link
Author

srappan commented Oct 11, 2019

root@plex:~/UnicornFFMPEG # npm start

> [email protected] start /root/UnicornFFMPEG
> pkg . -o "bin/Plex Transcoder"

> [email protected]
> Fetching base Node.js binaries to PKG_CACHE_PATH
  fetched-v10.15.3-freebsd-x64 [                    ] 0%
> Error! 404 Not Found
  https://github.com/zeit/pkg-fetch/releases/download/v2.6/uploaded-v2.6-node-v10.15.3-freebsd-x64
> Asset not found by direct link:
  {"tag":"v2.6","name":"uploaded-v2.6-node-v10.15.3-freebsd-x64"}
> Not found in GitHub releases:
  {"tag":"v2.6","name":"uploaded-v2.6-node-v10.15.3-freebsd-x64"}
> Building base binary from source:
  built-v10.15.3-freebsd-x64
> Cloning Node.js repository from GitHub...
  git                          [====================] 100%
> Checking out v10.15.3
> Applying patches
> Compiling Node.js from sources...
  gmake                        [                    ] 0%

Unfortunately now it just stalls. Hasn't progressed for over an hour.

@Maxou44
Copy link
Member

Maxou44 commented Oct 11, 2019

Maybe use docker could be a great solution for you ? 🥺

@srappan
Copy link
Author

srappan commented Oct 11, 2019

Possibly, but I actually couldn't find the docker version anywhere 😅

@Maxou44
Copy link
Member

Maxou44 commented Oct 11, 2019

A "real" docker support is planned in the roadmap 😅

@srappan
Copy link
Author

srappan commented Oct 11, 2019

Ah thats probably why haha

@Maxou44
Copy link
Member

Maxou44 commented Oct 11, 2019

@srappan
Copy link
Author

srappan commented Oct 11, 2019

Thanks! i'll give it ago. I think i'll leave this issue open, just so people don't get stuck on compiling like I did and smashing their heads against their desk till they get a concussion haha

@Maxou44 Maxou44 added the bug Something isn't working label Nov 12, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants