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

Slic3r: 1.2.9 -> 1.3.0-dev #28958

Closed
wants to merge 4 commits into from
Closed

Slic3r: 1.2.9 -> 1.3.0-dev #28958

wants to merge 4 commits into from

Conversation

timor
Copy link
Member

@timor timor commented Sep 4, 2017

Motivation for this change

Update Slic3r to a recent version. Should also fix one item from #28643

Things done

Upated relevant perl packages, updated build instructions for a recent development build of version 1.3.0, which is suggested over the old version 1.2.9

cc @bjornfor, @the-kenny

  • Tested using sandboxing
    (nix.useSandbox on NixOS,
    or option build-use-sandbox in nix.conf
    on non-NixOS)
  • Built on platform(s)
    • NixOS
    • macOS
    • Linux
  • 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 nox --run "nox-review wip"
  • Tested execution of all binary files (usually in ./result/bin/)
  • Fits CONTRIBUTING.md.

@mention-bot
Copy link

@timor, thanks for your PR! By analyzing the history of the files in this pull request, we identified @bjornfor, @the-kenny and @bobvanderlinden to be potential reviewers.

@timor timor changed the title Slic3r: 1.29 -> 1.3.0-dev Slic3r: 1.2.9 -> 1.3.0-dev Sep 4, 2017
@timor
Copy link
Member Author

timor commented Sep 4, 2017

The CI build fails because of a dependency (Boost::Geometry::Utils) that cannot be built. This actually seems to be the same error that I had to fix in the Slic3r package, but I don't know how to fix it for Boost::Geometry::Utils.

The problem is that the final linking step of the perl xs stuff is performed with "ld" instead of "g++" or "gcc". I fixed it in this PR for slic3r by manually exporting LD="g++", but it seems to be a general problem.

The symptom is a compilation error with "undefined reference to __dso_handle".

Edit: This has been addressed in c24820d

export SLIC3R_NO_AUTO=true
export PERL5LIB="./xs/blib/arch/:./xs/blib/lib:$PERL5LIB"
export LD=g++
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would propose to change this line to:
export LD=$CXX
or
unset LD
both should work :)

@@ -11946,6 +11946,7 @@ let self = _self // overrides; _self = with self; {
description = "Networking constants and support functions";
license = with stdenv.lib.licenses; [ artistic1 gpl1Plus ];
};
doCheck = false;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please add a comment explaining why the tests have been disabled.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am not sure myself, it seems that this is a pretty old issue (see 70f0d79), but I am unable to track what happened to those ancient disabled tests. Is there still a mechanism to disable only selected tests?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nixpkgs doesn't have any "builtin" to do that. You have to fix it yourself.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

for python we can disable using py.test, maybe perl has a similar tool? Otherwise sometimes deleting or patching can solve it.

}:

stdenv.mkDerivation rec {
version = "1.2.9";
version = "1.3.0-dev";
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

IMHO nixpkgs should package the latest releases from upstream. Version 1.3.0-dev is not a release.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That is true. I asked upstream, and was told that a current version is recommended over release 1.2.9 for production use

@bjornfor bjornfor mentioned this pull request Sep 7, 2017
8 tasks
@globin
Copy link
Member

globin commented Sep 8, 2017

I've merged #28996 as that looks cleaner and wait for an upstream stable release for the changes here..

@bjornfor
Copy link
Contributor

bjornfor commented Sep 9, 2017

I picked "perl-ExtUtils-ParseXS: 3.24 -> 3.35" and "perl-ExtUtils-XSpp: 0.1700 -> 0.18" to master.

@Mic92
Copy link
Member

Mic92 commented Sep 12, 2017

Is pull request this now obsolete?

@timor
Copy link
Member Author

timor commented Sep 12, 2017

According to upstream, Slic3r 1.3.0 is due Q4 2017, shall I create a new pull request then?

@bjornfor
Copy link
Contributor

Yes.

@timor timor closed this Sep 12, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants