Support OpenBSD - generating dev_bundle #29
Labels
Comments
|
Make python available for env
Install packages via
|
|
|
resize /tmp or change place for build bundle check free space (df) befor generate_dev_bundle |
|
You ought to add node: pkg_add node |
Hmm, anybody may use meteor with a system installed version of nodejs. But the stable releases from meteor are delivered with a standard builtin dev_tools_bundle that contains nodejs. I did a number of work to be able to build and provide that "same regular stable release of node" with the dev_bundles from our bintray repos. I guess it makes it much easier in case of errors during development to know, that not the runtime engine is maybe the reason because it differs. I will add a not to the hints section about using the OS dependent nodejs release. Thanks for feedback |
|
add info about |
|
write some guide how to run a meteor app in production To use in a production it is necessary to suggest the procedure of deploy on *BSD analogously as here on Ubuntu1, especially Step Four. Ref is comment from @Anabar at meteor forum |
|
The above instructions seem to be somewhat outdated. Several things have changed since OpenBSD 5.7, which appears to be the latest version "almost supported" by MeteorJS. I'm attempting to create dev_bundle on a 64-bit CURRENT branch of OpenBSD, version number being 6.0 at the moment. After lots (and lots) of trials, errors and debugging, I managed to overcome all other obstacles (including some version(s) of cc1plus not supporting the -std=gnu++0x option) but I can't get past the "File name too long for ustar" issue. Here's what I've done this far: I've made Python available for env by issuing I've installed the necessary packages using pkg_add: I have NOT replaced the command I did NOT install [email protected] since Since current version of Meteor appears to be using version 3.1.3 of sqlite3, I did When trying to run ./scripts/generate-dev-bundle.sh, a problem came up that had to do with cc1plus not recognizing the command line option "-std=gnu++0x": I found a total of FOUR different verions of cc1plus in my OpenBSD box. These two support the std=gnu++0x option: These two DO NOT support the std=gnu++0x option: So I did a dirty little hack, replacing cc1plus version 4.2.1 with 4.9.3: Almost there! At this point I'm able to compile everything. The only remaining problem is that pax/tar can not handle too long path/file names. Everything goes fine until the bundling phase, where some paths are too long for pax/tar: When trying to run meteor, it complains about ansi-regex module missing: If I'm not completely mistaken, there's no "good" way around the above final issue other than somehow hacking the paths to be shorter. I did try replacing OpenBSD's native tar with Gnu tar (gtar), but that didn't work out either; it resulted in some endless loop somewhere between compiling sqlite3 and the bundling phase. Any thoughts on how to proceed from here? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Following tasks has to be done in addition to FreeBSD so that meteor can build the dev_bundle
cp -ain node-gyp intocp -pPRnpm install [email protected]. If sqlite3 is build after NAN then the build crashes.Use enough memory on the server
The text was updated successfully, but these errors were encountered: