Summary: | media-gfx/freecad-0.12.5284-r3 fails at src_compile: error: ‘OuterShell’ is not a member of ‘BRepTools’ | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | izarf.mail |
Component: | Current packages | Assignee: | Michael Weber (RETIRED) <xmw> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | build log |
Description
izarf.mail
2013-09-03 17:15:55 UTC
For the moment one - attach full build log. Created attachment 357780 [details]
build log
(In reply to Rafał Mużyło from comment #1) > For the moment one - attach full build log. Why priority normal when issue is blocking CAD production? (In reply to izarf.mail from comment #3) > > Why priority normal when issue is blocking CAD production? Because. To elaborate: even upstream I doubt a build error would rate a blocker. In a distro alike to Gentoo, there are very few packages where build errors rate blockers. Anyway, it sufficed to scroll a few lines back. /var/tmp/portage/media-gfx/freecad-0.12.5284-r3/work/FreeCAD-0.12.5284/src/3rdParty/salomesmesh/src/StdMeshers/StdMeshers_RadialPrism_3D.cpp: In member function ‘virtual bool StdMeshers_RadialPrism_3D::Compute(SMESH_Mesh&, const TopoDS_Shape&)’: /var/tmp/portage/media-gfx/freecad-0.12.5284-r3/work/FreeCAD-0.12.5284/src/3rdParty/salomesmesh/src/StdMeshers/StdMeshers_RadialPrism_3D.cpp:164:29: error: ‘OuterShell’ is not a member of ‘BRepTools’ /var/tmp/portage/media-gfx/freecad-0.12.5284-r3/work/FreeCAD-0.12.5284/src/3rdParty/salomesmesh/src/StdMeshers/StdMeshers_RadialPrism_3D.cpp: In member function ‘virtual bool StdMeshers_RadialPrism_3D::Evaluate(SMESH_Mesh&, const TopoDS_Shape&, MapShapeNbElems&)’: /var/tmp/portage/media-gfx/freecad-0.12.5284-r3/work/FreeCAD-0.12.5284/src/3rdParty/salomesmesh/src/StdMeshers/StdMeshers_RadialPrism_3D.cpp:404:29: error: ‘OuterShell’ is not a member of ‘BRepTools’ *** This bug has been marked as a duplicate of bug 476610 *** |