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
Create an Ubuntu Trusty based docker image to build mesa with LLVM 3.3 #15
Comments
jasuarez
added a commit
that referenced
this issue
May 4, 2017
Unfortunately, LLVM 3.3 is not packaged for Ubuntu Xenial. And porting from old Ubuntu Trusty is causing lot of troubles. So we were just building LLVM 3.3 from scratch. But this takes time. Fortunately, we can package that manually-built version directly using checkinstall. This commit just uses LLVM 3.3 from a package created with checkinstall. It contains the same version as if it were build manually. This fixes issue #15.
Instead of following what title suggests, I've compiled LLVM 3.3 from source tarball, but used |
jasuarez
added a commit
that referenced
this issue
May 4, 2017
Unfortunately, LLVM 3.3 is not packaged for Ubuntu Xenial. And porting from old Ubuntu Trusty is causing lot of troubles. So we were just building LLVM 3.3 from scratch. But this takes time. Fortunately, we can package that manually-built version directly using checkinstall. This commit just uses LLVM 3.3 from a package created with checkinstall. It contains the same version as if it were build manually. This fixes issue #15.
jasuarez
added a commit
that referenced
this issue
May 4, 2017
Unfortunately, LLVM 3.3 is not packaged for Ubuntu Xenial. And porting from old Ubuntu Trusty is causing lot of troubles. So we were just building LLVM 3.3 from scratch. But this takes time. Fortunately, we can package that manually-built version directly using checkinstall. This commit just uses LLVM 3.3 from a package created with checkinstall. It contains the same version as if it were build manually. This fixes issue #15.
jasuarez
added a commit
that referenced
this issue
May 8, 2017
Unfortunately, LLVM 3.3 is not packaged for Ubuntu Xenial. And porting from old Ubuntu Trusty is causing lot of troubles. So we were just building LLVM 3.3 from scratch. But this takes time. Fortunately, we can package that manually-built version directly using checkinstall. This commit just uses LLVM 3.3 from a package created with checkinstall. It contains the same version as if it were build manually. This fixes issue #15.
jasuarez
added a commit
that referenced
this issue
May 8, 2017
Unfortunately, LLVM 3.3 is not packaged for Ubuntu Xenial. And porting from old Ubuntu Trusty is causing lot of troubles. So we were just building LLVM 3.3 from scratch. But this takes time. Fortunately, we can package that manually-built version directly using checkinstall. This commit just uses LLVM 3.3 from a package created with checkinstall. It contains the same version as if it were build manually. This fixes issue #15.
jasuarez
added a commit
that referenced
this issue
May 8, 2017
Unfortunately, LLVM 3.3 is not packaged for Ubuntu Xenial. And porting from old Ubuntu Trusty is causing lot of troubles. So we were just building LLVM 3.3 from scratch. But this takes time. Fortunately, we can package that manually-built version directly using checkinstall. This commit just uses LLVM 3.3 from a package created with checkinstall. It contains the same version as if it were build manually. This fixes issue #15.
jasuarez
added a commit
that referenced
this issue
May 9, 2017
Unfortunately, LLVM 3.3 is not packaged for Ubuntu Xenial. And porting from old Ubuntu Trusty is causing lot of troubles. So we were just building LLVM 3.3 from scratch. But this takes time. Fortunately, we can package that manually-built version directly using checkinstall. This commit just uses LLVM 3.3 from a package created with checkinstall. It contains the same version as if it were build manually. This fixes issue #15.
Fixed. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
No description provided.
The text was updated successfully, but these errors were encountered: