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
missing libX11.so.6 #1566
Comments
Having run
What's the next step? |
For reference, here's
|
I have used “Search the contents of packages” at http://packages.ubuntu.com/ and discovered (through a trial-and-error process) the following commands which, if run before node-webkit, make it possible to run 32bit node-webkit on 64bit Travis CI Linux:
Here's an example of a Travis CI job that could run node-webkit 32bit successfully: |
@Mithgol pretty sure you can combine that all onto one line. |
Yes. But if Travis CI configuration changes (providing a different set of available packages) then one line would be harder to debug (it would stop the whole installation on the first unknown package it encountered). Having several lines means you may identify all lines that were successful and all lines that failed, even if failures are multiple. For example, in that log I could identify two missing packages at once (line 2106, line 2132) and remove them (TryGhost/node-sqlite3@9c555c3). If I were to remove them one-by-one, I'd have to spend at least ten more minutes between errors (as you may see in that log's header, Travis job's duration was 9 minutes 9 seconds). |
The purpose is to build and test node-sqlite3 for node-webkit on Travis CI (TryGhost/node-sqlite3#252).
For that purpose I download https://s3.amazonaws.com/node-webkit/v0.8.4/node-webkit-v0.8.4-linux-ia32.tar.gz and unpack it, and then run
nw
, but it says:(see that Travis CI log, line 1736).
On the same system, when I download https://s3.amazonaws.com/node-webkit/v0.8.4/node-webkit-v0.8.4-linux-x64.tar.gz and unpack it, and then run
nw
, it runs happily without errors.Does it mean that 32-bit node-webkit won't run on a 64-bit Linux system, or there's still hope?
The text was updated successfully, but these errors were encountered: