New Ticket     Tickets     Wiki     Browse Source     Timeline     Roadmap     Ticket Reports     Search

Ticket #25877 (closed defect: worksforme)

Opened 3 years ago

Last modified 2 years ago

opendx: undefined symbols _DestroyConstitute

Reported by: jxzhu@… Owned by: gwright@…
Priority: Normal Milestone:
Component: ports Version: 1.9.1
Keywords: Cc:
Port: opendx

Description (last modified by ryandesign@…) (diff)

I have tried several times to install opendx through MacPorts on Mac OSX Leopard (10.5.8), but have been unsuccessful. I did the following steps:

sudo port selfupdate 
sudo port install opendx 

and got the following errors ---

% sudo port install opendx
Password:
--->  Computing dependencies for opendx
--->  Building opendx
Error: Target org.macports.build returned: shell command failed
Log for opendx is at: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_ports_science_opendx/main.log
Error: Status 1 encountered during processing.
To report a bug, see <http://guide.macports.org/#project.tickets>

The log file is attached here.

I have also tried uninstalling all packages by executing the command

sudo port -f uninstall installed 

and repeated the above procedure. The error remains.

Having searched the tickets database, I could not get a clear answer.

Attachments

main.log (67.4 KB) - added by jxzhu@… 3 years ago.
main.log file

Change History

Changed 3 years ago by jxzhu@…

main.log file

comment:1 Changed 3 years ago by jxzhu@…

  1. Detailed error information is shown near the end of main.log file.
  2. The same failure occurs on both MacPro and MacBook (Leopard 10.5.8).

comment:2 follow-up: ↓ 5 Changed 3 years ago by ryandesign@…

  • Description modified (diff)
  • Summary changed from port install opendx failure to opendx: undefined symbols _DestroyConstitute
  • Priority changed from High to Normal
  • Owner changed from macports-tickets@… to gwright@…
  • Keywords opendx removed
  • Port set to opendx

Please remember to use WikiFormatting and to preview before submitting. Don't set the Priority field to High, but do fill in the Port field and Cc the port's maintainer.

comment:3 Changed 3 years ago by jxzhu@…

  • Cc jxzhu@… added

Cc Me!

comment:4 Changed 3 years ago by jxzhu@…

  • Cc jxzhu@… removed

Cc Me!

comment:5 in reply to: ↑ 2 ; follow-up: ↓ 6 Changed 3 years ago by jxzhu@…

Replying to ryandesign@…:

Please remember to use WikiFormatting and to preview before submitting. Don't set the Priority field to High, but do fill in the Port field and Cc the port's maintainer.

Thanks for the advice. How can I find out the email address of the port's maintainer?

comment:6 in reply to: ↑ 5 ; follow-up: ↓ 7 Changed 3 years ago by macsforever2000@…

Replying to jxzhu@…:

Thanks for the advice. How can I find out the email address of the port's maintainer?

port info will tell you for any given port. Try it:

port info opendx

comment:7 in reply to: ↑ 6 Changed 3 years ago by jxzhu@…

Replying to macsforever2000@…:

Replying to jxzhu@…:

Thanks for the advice. How can I find out the email address of the port's maintainer?

port info will tell you for any given port. Try it:

port info opendx

This command does serve the purpose. Thanks.

comment:8 Changed 3 years ago by ryandesign@…

Has duplicate #27291.

comment:9 follow-up: ↓ 10 Changed 3 years ago by jmr@…

According to this report, "A couple of months ago the API of imagemagick has changed and DestroyConstitute() was replaced by ConstituteComponentTerminus() ."

comment:10 in reply to: ↑ 9 Changed 3 years ago by sonnyrhim@…

Replying to jmr@…:

According to this report, "A couple of months ago the API of imagemagick has changed and DestroyConstitute() was replaced by ConstituteComponentTerminus() ."

I also found in other forum about API changes. Then, what is the solution for opendx in macport?

comment:11 Changed 2 years ago by jmr@…

  • Status changed from new to closed
  • Resolution set to worksforme

Can't reproduce; current version of libMagickCore.dylib does contain _DestroyConstitute.

Note: See TracTickets for help on using tickets.