-
Notifications
You must be signed in to change notification settings - Fork 15.4k
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
Trying to build atom-shell on Debian Wheezy #735
Comments
You need to build the atom branch of libchromiumcontent, which included some atom-shell specific patches. |
When I build the atom branch of libchromiumcontent, I get errors about not finding references to GLIBC_2.14 and GLIBC_2.15 required by clang++ which is the original problem and why I'm trying to build on wheezy. I also tried checking out the last commit in the atom branch of libchromiumcontent before the date atom-shell 0.15.3 was released (8/6/2014). Libchromiumcontent builds successfully but I get the same errors as before when building atom-shell. The version of clang installed locally is 3.0-6.2 |
Building atom-shell requires clang 3.4 (I'll add this to the docs, sorry), and you may need to add clang's apt source to get clang 3.4. |
It appears that clang 3.4 is not compatible with wheezy because it requires a higher version of libc (2.15) than wheezy is built with (2.13). Does that mean that atom-shell can't be built on wheezy? Was there a point where it didn't require clang 3.4? |
Clang 3.4 is required because libchromiumcontent is configured to be built with prebuilt clang binaries whose version is 3.4. I'll change libchromiumcontent to be built with system clang, which should be able to fix this issue. |
Any updates on this? |
You may be able to hack: https://github.com/brightray/libchromiumcontent/blob/master/chromiumcontent/chromiumcontent.gypi There are a couple areas of interest (as far as clang goes)
and
Beyond that I suppose we'll have to wait for @zcbenz to comment. |
So I was able to build atom-shell 0.15.3 successfully on wheezy with a little hackery (but I'm getting some runtime errors). I checkout libchromiumcontent commit baf43b6 (the last one before atom-shell 0.15.3 was released) and then manually add the UrlRequestJob patch to the patches folder before building libchromiumcontent. The errors I get when I try to run atom-shell (with the default app or with our own app) are about the chromium sandbox and nss loading certs. Are the sandbox errors important? I saw that there is a patch to downgrade the severity of them.
|
Electron now links with static library version of libchromiumcontent, so three is no need to build libchromiumcontent separately for each distribution now. |
I've been trying to build atom-shell 0.15.3 on debian wheezy. I'm building libchromiumcontent from source successfully (though I need to figure out issues with the chrome_sandbox not running). But I can't get atom-shell to build against the libchromiumcontent that I have built.
Here's the build error I am seeing:
../../atom/browser/net/adapter_request_job.cc:42:21: error: 'ReadRawData' is a protected member of 'net::URLRequestJob'
Interestingly if I build atom-shell against the default libchromiumcontent that is downloaded, then copy my manually built libchromiumcontent and then build again, the build succeeds (it just links against the new version since the other build tasks are cached). I have to manually copy the libchromiumcontent.so file into the out/Release directory afterward but then I can run atom-shell (other than the sandbox issues in the renderer).
Here is more details from the build log when building both the debug and release configurations
And here's the build script I am runinng:
The text was updated successfully, but these errors were encountered: