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

New Dart Editor build 0.6.5.0_r25017, error on debian 7.0 #11880

Closed
DartBot opened this issue Jul 17, 2013 · 19 comments
Closed

New Dart Editor build 0.6.5.0_r25017, error on debian 7.0 #11880

DartBot opened this issue Jul 17, 2013 · 19 comments
Assignees
Labels
area-infrastructure closed-not-planned Closed as we don't intend to take action on the reported issue

Comments

@DartBot
Copy link

DartBot commented Jul 17, 2013

This issue was originally filed by joo.ts...@gmail.com


What steps will reproduce the problem?

  1. Pub update

What is the expected output? What do you see instead?

Pub update failed, [1] /home/joo/opt/eclipse/dart-sdk/bin/dart: /lib/x86_64-linux-gnu/libc.so.6: version GLIBC_2.15' not found (required by /home/joo/opt/eclipse/dart-sdk/bin/dart) /home/joo/opt/eclipse/dart-sdk/bin/dart: /lib/x86_64-linux-gnu/libc.so.6: versionGLIBC_2.14' not found (required by /home/joo/opt/eclipse/dart-sdk/bin/dart)

@iposva-google
Copy link
Contributor

Added Area-Build, Triaged labels.

@mkustermann
Copy link
Member

Set owner to @ricowind.

@DartBot
Copy link
Author

DartBot commented Jul 26, 2013

This comment was originally written by joo...@gmail.com


?

@ricowind
Copy link
Contributor

This is due to a mismatch in libc versions (we basically moved to Ubuntu Precise, compiling against glibc versions newer than what is on stock ubuntu). We are currently evaluating what to do about this.

@DartBot
Copy link
Author

DartBot commented Jul 29, 2013

This comment was originally written by joo.ts...@gmail.com


My current project is used in the company's ERP.
As far as i know can not be used after the DART SDK0.6.5 on DEBIAN, REDHAT, CENTOS current stable version.
I can not accept.

@DartBot
Copy link
Author

DartBot commented Jul 29, 2013

This comment was originally written by ricow@chromium.org


It is very easy to build the runtime yourself, see:
https://code.google.com/p/dart/wiki/Building

As I said, we are evaluating how to solve this for the long run

@DartBot
Copy link
Author

DartBot commented Aug 2, 2013

This comment was originally written by joo.tsao...@gmail.com


Honestly, I do not want to compile it yourself.
I am very curious, google developers only one test machine?

@DartBot
Copy link
Author

DartBot commented Aug 14, 2013

This comment was originally written by sestegr...@gmail.com


In the meantime, you could use a quick'n dirty solution that consists of importing Ubuntu 12.04 LTS libraries into Dart SDK. See https://github.com/sestegra/patch-dartsdk-linux

@DartBot
Copy link
Author

DartBot commented Aug 21, 2013

This comment was originally written by gl...@gmail.com


I understand that Dart is still in beta but such actions from Dart's team makes me wonder whenever or not Dart should be taken seriously in its current state and all together. Is Ubuntu dominating the user-base to such an extend where the rest of the users are irrelevant? I gave the build instructions a try and will do so again but in all honesty i find the documentation confusing and all over the place, it might be that i am not just as experienced as i should (although i had to build things from source in the past) but still, things suddenly got way more complicated from the usual "Help -> About Dart Editor -> Update".

@DartBot
Copy link
Author

DartBot commented Sep 15, 2013

This comment was originally written by gael.crov...@gmail.com


Hi,
Do you have an equivalent patch for a 32bits Debian ?
Thanks a lot

@DartBot
Copy link
Author

DartBot commented Sep 15, 2013

This comment was originally written by sesteg...@gmail.com


32 bits version added

@DartBot
Copy link
Author

DartBot commented Oct 22, 2013

This comment was originally written by bio...@gmail.com


Hi -- just trying to see if I could get the dart executable to run against some scripts (the really simple hello_world from the tutorials), and got the same error.
I haven't really got time to go into installing everything from scratch right now, although I might try later.
Has there been any movement on this problem?

@anders-sandholm
Copy link
Contributor

Removed Area-Build label.
Added Area-Infrastructure label.

@DartBot
Copy link
Author

DartBot commented Jan 11, 2014

This comment was originally written by cong...@mathphoenix.com


the problem not fix even for 1.0.0_r30798 (STABLE), please fix it

@DartBot
Copy link
Author

DartBot commented Mar 1, 2014

This comment was originally written by cong...@mathphoenix.com


It's too danger to just upgrade system libc.

2014-03-01 10:54 GMT+08:00 <dart@googlecode.com>:

@DartBot
Copy link
Author

DartBot commented Mar 3, 2014

This comment was originally written by ben.plo...@gmail.com


So I deleted my previous comment (#­16) because I ran into some other troubles. However, I did come across great instructions on how to make dart build on debian here: https://code.google.com/p/dart/wiki/BuildingOnDebian (There are similar instructions for redhat/fedora/centos here: https://code.google.com/p/dart/wiki/BuildingOnCentOS).

These steps worked for me and were far less painful than trying to use a bleeding edge version of GLIBC. I'm copying them with small tweaks below. The whole process took me maybe 20 minutes, most of which was watching compilation output.

$ sudo apt-get -y update
$ sudo apt-get -y install subversion make g++ openjdk-6-jdk

$ svn co http://src.chromium.org/svn/trunk/tools/depot_tools
$ export PATH=$PATH:pwd/depot_tools

replace 1.2 with whatever branch you wish to build

$ gclient config http://dart.googlecode.com/svn/branches/1.2/deps/all.deps
$ gclient sync
$ gclient runhooks

$ cd dart

If you want to build the entire dark SDK, use this command

$ tools/build.py --mode=release --arch=x64 create_sdk

If you only want the dart executable, run this instead:

$ tools/build.py --mode=release --arch=x64 runtime

the dart executable is now at out/ReleaseX64/dart - you can do a smoke test by printing the version

$ dart/out/ReleaseX64/dart --version

>> Dart VM version: 1.2.0 (Mon Mar 3 03:06:20 2014) on "linux_x64"

@DartBot
Copy link
Author

DartBot commented Mar 3, 2014

This comment was originally written by glfaf...@gmail.com


@ben(#­18), you are still missing an important piece though, the dartium browser. You will have to download and compile that as well and that is close to impossible.

In the process of compiling Dartium/Chromium the toolchain fetches various libraries needed for the build, unfortunately those libraries are also compiled against a newer version of libc thus the build will fail. Now you could go ahead and try figuring out which libraries are those, download and compile them, put them in the right place and so on (you end up having to write a custom build script pretty much), what you end up doing is wasting time and lots of hard disk space !

I cant stress this enough, the best course of action for anyone currently in Debian that wants to write Dart code is to use a virtual machine: Either install Debian and update the libc version or if you wanna be safer install Ubuntu (that's what Dart's build-bot uses, you wont have any version mismatches now or in the future)

@DartBot
Copy link
Author

DartBot commented Dec 12, 2014

This comment was originally written by Jan.Mo...@gmail.com


Similar issues in CentOS 6.5, Dart Editor works fine, Dartium Browser and dart2j fails on GlibC errors. See: https://stackoverflow.com/questions/27442019/dart-on-centos-6-5

@ricowind
Copy link
Contributor

ricowind commented Jun 2, 2015

Added WontFix label.

@kevmoo kevmoo added closed-not-planned Closed as we don't intend to take action on the reported issue and removed priority-unassigned labels Mar 1, 2016
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-infrastructure closed-not-planned Closed as we don't intend to take action on the reported issue
Projects
None yet
Development

No branches or pull requests

6 participants