Opened 9 years ago

Closed 9 years ago

#48074 closed defect (fixed)

auto-multiple-choice: AMC-detect fails to build after update to opencv 3.0.0

Reported by: dbevans (David B. Evans) Owned by: nortcele
Priority: Normal Milestone:
Component: ports Version: 2.3.3
Keywords: Cc: ryandesign (Ryan Carsten Schmidt), stromnov (Andrey Stromnov)
Port: auto-multiple-choice

Description

After upgrade to opencv 3.0.0, build of auto-multiple-choice fails as follows

/usr/bin/clang -arch x86_64 -o AMC-detect AMC-detect.cc  -O2 -I/opt/local/include -I. -DNEEDS_GETLINE -L/opt/local/lib   -lstdc++ -lm -I/opt/local/include/opencv -lopencv_core -lopencv_highgui -lopencv_imgproc 
Undefined symbols for architecture x86_64:
  "_cvConvertImage", referenced from:
      calage(_IplImage*, _IplImage*, double, double, double, double, double, double*, double*, _IplImage**, int) in AMC-detect-a855fb.o
  "_cvLoadImage", referenced from:
      load_image(_IplImage**, char*, int, double, int) in AMC-detect-a855fb.o
      _main in AMC-detect-a855fb.o
  "_cvSaveImage", referenced from:
      mesure_case(_IplImage*, _IplImage*, int, int, int, int, int, double, int, double, double, double, double, linear_transform*, point*, _IplImage*, char*, int) in AMC-detect-a855fb.o
      _main in AMC-detect-a855fb.o
ld: symbol(s) not found for architecture x86_64

Log attached.

Attachments (1)

main.log (116.4 KB) - added by dbevans (David B. Evans) 9 years ago.
Build log showing failure when building with opencv 3.0.0

Download all attachments as: .zip

Change History (5)

Changed 9 years ago by dbevans (David B. Evans)

Attachment: main.log added

Build log showing failure when building with opencv 3.0.0

comment:1 Changed 9 years ago by nortcele

Question posted to the dev list.

There is a simple way to adapt this version of auto-multiple-choice to the new version of opencv. But this way makes auto-multiple-choice incompatible with previous version of opencv. Could I update auto-multiple-choice port despite this?

comment:2 Changed 9 years ago by dbevans (David B. Evans)

For the purposes of MacPorts alone, this would probably OK, since the 2.4 version is no longer available as a port. However, a more rigorous approach would be to test (perhaps using pkg-config) which version is installed and modify the code to behave according based on the result.

comment:3 Changed 9 years ago by nortcele

I think I made an error. I opened ticket #48102 with patches to solve the problem instead of adding the patches to this ticket.

comment:4 Changed 9 years ago by dbevans (David B. Evans)

Resolution: fixed
Status: newclosed

No problem. Fix committed in r137787. Thanks.

Note: See TracTickets for help on using tickets.