Opened 12 years ago

Closed 12 years ago

Last modified 12 years ago

#20812 closed defect (invalid)

libcdio libs fail when accessed by pycdio

Reported by: wolfson@… Owned by: macports-tickets@…
Priority: Normal Milestone:
Component: ports Version: 1.7.1
Keywords: Cc:
Port: libcdio

Description

I assume this is actually a problem just with libcdio, but I haven't tried to use them except w/ pycdio:

import cdio

Traceback (most recent call last):

File "<stdin>", line 1, in <module> File "cdio.py", line 23, in <module>

import pycdio

File "pycdio.py", line 14, in <module>

import _pycdio

ImportError: dlopen(./_pycdio.so, 2): Symbol not found: _CFConstantStringClassReference

Referenced from: /opt/local/lib/libcdio.10.dylib Expected in: dynamic lookup

The second-to-last line is what makes me think this is a libcdio problem, not a pycdio problem. However, I can run cd-info!

Change History (5)

comment:1 Changed 12 years ago by jmroot (Joshua Root)

Port: libcdio added

How are you running pycdio? There doesn't appear to be a port for it.

comment:2 Changed 12 years ago by wolfson@…

Using easy_install. There's a swig wrapper. I was able to build & use it successfully earlier, but I believe it was a previous version (hd has been wiped so I had to update; plus I was using fink back then).

comment:3 Changed 12 years ago by wolfson@…

Nevermind---I got the same errors using libtagedit and the python interface to that, so it's obviously not a problem confined to libcdio.

comment:4 Changed 12 years ago by tobypeterson

Resolution: invalid
Status: newclosed

Actually, the issue appears to be that pycdio is linking against libcdio without also linking against CoreFoundation. Not a libcdio issue afaict.

comment:5 Changed 12 years ago by tobypeterson

In other words - if pycdio (and whatever libtagedit interface) is added to MacPorts, they will need to be fixed to link correctly. Probably as simple as adding -framework CoreFoundation to flags.

Note: See TracTickets for help on using tickets.