Opened 7 years ago

Closed 7 years ago

#51814 closed defect (invalid)

digikam @4.9.0: error: no template named 'vector'; did you mean 'std::vector'?

Reported by: uwe22 Owned by: macports-tickets@…
Priority: Normal Milestone:
Component: ports Version: 2.3.4
Keywords: Cc: jgosmann (Jan Gosmann), cgilles (HumanDynamo)
Port: digikam


running OSX 10.11.5 trying to install Digikam with macports gets this error:

install digikam 
--->  Computing dependencies for digikam
--->  Building digikam
Error: for port digikam returned: command execution failed
Please see the log file for port digikam for details:
To report a bug, follow the instructions in the guide:
Error: Processing of port digikam failed

I am attaching the log file Please help

Attachments (1)

main.log (1.1 MB) - added by uwe22 7 years ago.

Download all attachments as: .zip

Change History (3)

Changed 7 years ago by uwe22

Attachment: main.log added


comment:1 Changed 7 years ago by mf2k (Frank Schima)

Priority: HighNormal

The Priority field is for use by Macports team members only.

comment:2 Changed 7 years ago by ryandesign (Ryan Schmidt)

Cc: jan@… caulier.gilles@… added
Port: digikam added
Resolution: invalid
Status: newclosed
Summary: digikam @4.9.0 (kde, kde4) fails to builddigikam @4.9.0: error: no template named 'vector'; did you mean 'std::vector'?

The log says:

:info:build /usr/local/include/opencv2/contrib/contrib.hpp:273:23: error: no template named 'vector'; did you mean 'std::vector'?
:info:build         Octree( const vector<Point3f>& points, int maxLevels = 10, int minPoints = 20 );
:info:build                       ^

This means you have a copy of opencv installed in /usr/local. We don't support installing software in /usr/local while using MacPorts, because of the likelihood of these kinds of conflicts. Please remove what you have installed in /usr/local.

Even after doing so, digikam won't build, however; we're tracking that problem in #48081. We need to update digikam to a newer version; an update is proposed in #47772.

Note: See TracTickets for help on using tickets.