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

openspace: 0.11.1 -> 0.14.0 #62300

wants to merge 1 commit into from

openspace: 0.11.1 -> 0.14.0 #62300

wants to merge 1 commit into from


Copy link

@timjrd timjrd commented May 31, 2019

Motivation for this change

Upgrading from OpenSpace 0.11.1 to 0.14.0, and cleaning up the package.

Things done
  • Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
  • Built on platform(s)
    • NixOS
    • macOS
    • other Linux distributions
  • Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
  • Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
  • Tested execution of all binary files (usually in ./result/bin/)
  • Determined the impact on package closure size (by running nix path-info -S before and after)
  • Assured whether relevant documentation is up to date
  • Fits

@timjrd timjrd force-pushed the openspace-0.14.0 branch from e867c6e to 92dcf3a Jun 2, 2019
Copy link

@mmahut mmahut commented Aug 12, 2019

@timjrd do you mind rebasing this?

Copy link
Contributor Author

@timjrd timjrd commented May 4, 2020

Hi :) I rebased this branch on my local copy, but I'm now unable to successfully compile the package, presumably due to an upgrade of freeimage. I'm facing the following error at the end of the build (linking stage):

ld: undefined reference to `std::__cxx11::basic_stringstream<char, std::char_traits<char>, std::allocator<char> >::basic_stringstream()@GLIBCXX_3.4.26'

I came across this thread, where it is suggested to set CXXFLAGS='-D_GLIBCXX_USE_CXX11_ABI=0'. I tried to enforce this flag by various means without any success.

Any clue?

Copy link
Contributor Author

@timjrd timjrd commented Oct 9, 2020

Closing this as it's largely outdated. I would rather re-package the latest version when I have some time.

@timjrd timjrd closed this Oct 9, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
Linked issues

Successfully merging this pull request may close these issues.

None yet

4 participants