Bug 204699
| Summary: | graphics/blender: Assertion failed in llvm | ||
|---|---|---|---|
| Product: | Ports & Packages | Reporter: | O. Hartmann <ohartmann> |
| Component: | Individual Port(s) | Assignee: | freebsd-ports-bugs (Nobody) <ports-bugs> |
| Status: | Closed Overcome By Events | ||
| Severity: | Affects Some People | CC: | FreeBSD, lumiwa, tablooaraz |
| Priority: | --- | Keywords: | crash, needs-qa |
| Version: | Latest | Flags: | bugzilla:
maintainer-feedback?
(mva) |
| Hardware: | Any | ||
| OS: | Any | ||
|
Description
O. Hartmann
2015-11-20 11:52:24 UTC
Do you still run into that problem with blender 2.76b? Jawohl, I do. The problem seems to be the "cycles" renderer or any related option, like "cyclesosl", which includes devel/llvm34. Obviously, belnder gets confused with any llvm installed so far. I have llvm36 (due to X11/xorg/libclc) and llvm37 (pocl-0.12) and I try also to install full llvm via /etc/src.conf as far as possible (didn't experiment with the knobs due to time and performance constraints ...). Disabling CYCLES in the configuration solves the problem of the crashes, even in blender 2.76b. I haven't figured out whether disabling CYCLES renderer involves other required facilities so far, but at the first view, if someone doesn't use CYCLES, disabling cycles is a possible solution. I miss the network/cluster rendering at the moment, but this might be due to other issues. Kind regards, oh I had and I have the same problem on version 2.76b on my FreeBSD 10.2-RELEASE (amd64). If I buld with Cycles, blender does not start (see my report ID 199161). Have a good one. lumiwa (In reply to ohartman from comment #2) Do you think that if we build Blender with gcc the problem will be solved? I am using OSX for Blender and there are no problem (the same computer). Thank you. I have not ried building most recent blender from ports with gcc. The failure involves only if options CYCLES is given. It reels in devel/llvm34. I would rather stay with clang in favour over gcc and diable option cycles as long as the problem persists. (In reply to ohartman from comment #5) Thank you. I will wait to and stay with Blender for OSX because I use cycles render engine. Blender version 3.77a is in ports, build without problem with Synth but the problem with Cycles engine still exist. (In reply to lumiwa from comment #7) I forgot for blender Assertion failed: (findOption(Name) == Values.size() && "Option already exists!"), function addLiteralOption, file /construction/xports/devel/llvm37/work/llvm-3.7.1.src/include/llvm/Support/CommandLine.h, line 698. Abort (core dumped) (In reply to ohartman from comment #0) I have 11.0-RELEASE-p1 FreeBSD 11.0-RELEASE-p1 #0 r306420: Thu Sep 29 01:43:23 UTC 2016 root@releng2.nyi.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64 and I rebuild all ports and reinstalled the and I have the sam,e problem still and one error more: blender libGL error: failed to open drm device: Permission denied libGL error: failed to load driver: r600 Assertion failed: (findOption(Name) == Values.size() && "Option already exists!"), function addLiteralOption, file /construction/xports/devel/llvm37/work/llvm-3.7.1.src/include/llvm/Support/CommandLine.h, line 698. Abort (core dumped) Thank you. Maintainer reset The blender port has just been updated to 2.79 and I am now the maintainer. Do you still have any issues with the new version of blender? No my system, FreeBSD 11.1-RELEASE (amd64), use Synth to build ports, I do not have any problem (built with Cycles and Cycleosl enabled) and Blender woroks faster than before :). Thank you very much for the great work. Well, the update to a new Blender version fixed the problem for me. I lost this PR out of sight - the problem has been fixed before with the change towards LLVM/CLANG 5 in CURRENT. It shouldn't seem that we have to wait almost a year for fixing this ... Closing. MARKED AS SPAM |
