Bug 1014458
Summary: | Program does not start | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Dario Faggioli <raistlin> |
Component: | slic3r | Assignee: | Miro Hrončok <mhroncok> |
Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | 19 | CC: | mhroncok, paul, perl-devel |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2013-10-07 14:27:46 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Dario Faggioli
2013-10-02 06:10:19 UTC
Uaaa. The thing is, you need Math-Clipper 1.22, as it says. Should be fixed by `yum update perl-Math-Clipper`. I should have added >= 1.22 to requires, but I forgot and now I cannot, because slic3r fails to build in rawhide and Fedora 20. (In reply to Miro Hrončok from comment #1) > Uaaa. The thing is, you need Math-Clipper 1.22, as it says. > > Should be fixed by `yum update perl-Math-Clipper`. > Mmm... Does not look like so (or am I doing something wrong?): $ sudo yum install perl-Math-Clipper ... Package perl-Math-Clipper-1.22-4.fc19.x86_64 already installed and latest version Nothing to do $ yum info perl-Math-Clipper ... Installed Packages Name : perl-Math-Clipper Arch : x86_64 Version : 1.22 Release : 4.fc19 $ slic3r Math::Clipper version 1.22 required--this is only version 1.17 at /usr/share/perl5/vendor_perl/Slic3r/Geometry/Clipper.pm line 12. BEGIN failed--compilation aborted at /usr/share/perl5/vendor_perl/Slic3r/Geometry/Clipper.pm line 12. Compilation failed in require at /usr/share/perl5/vendor_perl/Slic3r/ExPolygon.pm line 11. BEGIN failed--compilation aborted at /usr/share/perl5/vendor_perl/Slic3r/ExPolygon.pm line 11. Compilation failed in require at /usr/share/perl5/vendor_perl/Slic3r.pm line 32. BEGIN failed--compilation aborted at /usr/share/perl5/vendor_perl/Slic3r.pm line 32. Compilation failed in require at /usr/bin/slic3r line 17. BEGIN failed--compilation aborted at /usr/bin/slic3r line 17. > I should have added >= 1.22 to requires, but I forgot and now I cannot, > because slic3r fails to build in rawhide and Fedora 20. > Yep, I noticed that on F19 too (talking about the .tar and the git, I haven't tried the SRPM). Thanks and Regards, Dario Perhaps you have another version of the Math::Clipper module installed as well as the perl-Math-Clipper rpm? What happens if you do: $ perl -MMath::Clipper -e 'print "$Math::Clipper::VERSION\n";' I get "1.22". Looks like I do: $ perl -MMath::Clipper -e 'print "$Math::Clipper::VERSION\n";' 1.17 Now the question is who installed that (I certainly did not, I know nothing about perl!). Perhaps a manual attempt to build Slic3r from sources some months ago? Also, is that normal that installing the perl-Math-Clipper rpm does not identify that and update it, or at least report it, or something like that (again, sorry, 0% perl here :-( )? I'll see if I can remove it, and if Slic3r turns back tu functioning after that... Thanks. This should find it for you: $ perl -MMath::Clipper -e 'print $INC{"Math/Clipper.pm"} . "\n"' /usr/lib64/perl5/vendor_perl/Math/Clipper.pm Installing / updating the perl-Math-Clipper rpm package would update an existing perl-Math-Clipper rpm package, but it can know nothing about any other versions you've installed by other means. (In reply to Paul Howarth from comment #5) > This should find it for you: > > $ perl -MMath::Clipper -e 'print $INC{"Math/Clipper.pm"} . "\n"' > /usr/lib64/perl5/vendor_perl/Math/Clipper.pm > I use some other way to achieve the same, but I think I did it, thanks. > Installing / updating the perl-Math-Clipper rpm package would update an > existing perl-Math-Clipper rpm package, but it can know nothing about any > other versions you've installed by other means. > Yes, it worked. Great. I think I can close the bug now... It probably wasn't a bug in the first place (sorry for that). |