This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-06-26
Channels
- # adventofcode (2)
- # beginners (69)
- # boot (37)
- # cider (6)
- # clara (31)
- # cljs-dev (75)
- # cljsrn (5)
- # clojure (72)
- # clojure-dev (7)
- # clojure-italy (11)
- # clojure-nl (8)
- # clojure-russia (2)
- # clojure-spec (56)
- # clojure-uk (54)
- # clojure-za (1)
- # clojurescript (156)
- # cursive (2)
- # datomic (34)
- # emacs (1)
- # fulcro (227)
- # hoplon (74)
- # jobs (1)
- # jobs-discuss (16)
- # leiningen (5)
- # lumo (17)
- # off-topic (9)
- # om (3)
- # onyx (10)
- # other-languages (1)
- # portkey (2)
- # re-frame (2)
- # reagent (36)
- # reitit (1)
- # remote-jobs (1)
- # ring-swagger (8)
- # shadow-cljs (85)
- # slack-help (2)
- # spacemacs (6)
- # specter (3)
- # sql (17)
- # test-check (15)
- # tools-deps (80)
Not sure if this is a Lumo issue but I'm not sure where to start with this... TravisCI builds of HoneySQL are failing with
/home/travis/.nvm/versions/node/v8.11.3/lib/node_modules/lumo-cljs/bin/lumo: /usr/lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.20' not found (required by /home/travis/.nvm/versions/node/v8.11.3/lib/node_modules/lumo-cljs/bin/lumo)
@seancorfield I think I addressed that with https://github.com/jkk/honeysql/commit/96e63dce28c9585759214ac3f3e5cdab9eab179e
However probably Travis bumped node
I actually don't know why I am installing nvm there actually
Will take a look tomorrow, should be an easy fix, afk now
Thanks.
@richiardiandrea Just FYI, I updated all the HoneySQL dependencies (in project.clj
) and that made no difference to the GLIBCXX error on Travis...
@seancorfield cool did not have time but bear with me 😉
@richiardiandrea https://travis-ci.org/jkk/honeysql/builds/397133758 -- I added the ppa:ubuntu-toolchain-r/test
and then updated and installed libstdc++6
... kinda brute force, but it works 🙂
uhm, yeah I will open a PR cleaning the mess up 🙂
it is probably due to the weird thing I am doing there with nvm
sorry about that!!
According to the Travis docs, nvm
should already be installed. So, is this a matter of using nvm
to install an earlier version of npm
? Or is it Lumo itself that needs to have an older version installed?
All the research I did on the error suggested that the only two solutions are: 1. rebuild you app on the host system (so it uses the older libstdc++) 2. upgrade the host (so it has the new libstdc++)
Lumo includes node so it is just expecting the right libstd to be in the system - in the previous lumo version we were ok - lumo 1.9.0 needs a higher version - I guess if we do npm install [email protected]
we settle it once and for all
And probably we can get rid of the nvm
line altogether