Opened 12 years ago

Closed 12 years ago

#31576 closed defect (invalid)

texlive-xetex and freetype

Reported by: jbolden1517@… Owned by: drkp (Dan Ports)
Priority: Normal Milestone:
Component: ports Version: 2.0.3
Keywords: Cc: ryandesign (Ryan Carsten Schmidt)
Port: texlive-bin

Description

texlive-xetex (currently @23080) has a dependency of freetype lib 14. The version dependency is set to low in the port. The actual dependency is a chain and is set in texlive-bin port.

Change History (8)

comment:1 Changed 12 years ago by drkp (Dan Ports)

Keywords: texlive removed
Owner: changed from macports-tickets@… to dports@…

I didn't follow this. What do you mean?

comment:2 in reply to:  1 ; Changed 12 years ago by jbolden1517@…

Replying to dports@…:

I didn't follow this. What do you mean?

texlive-xetex installs xetex. The current version of xetex has a dependency on freetype lib (/opt/local/lib/libfreetype.6.dylib) version 14. freetype is a dependency for texlive-bin which is a dependency for texlive-xetex. However the version in texlive-bin is set low enough that when you try to run xetex it can error with a version to low:

 /opt/local/lib/libfreetype.6.dylib
  Referenced from: /opt/local/bin/xelatex
  Reason: Incompatible library version: xelatex requires version 14.0.0 or later, but libfreetype.6.dylib provides version 13.0.0

So I suspect the freetype dependency in the texlive-bin port should be changed to require a later version.

comment:3 Changed 12 years ago by drkp (Dan Ports)

Cc: ryandesign@… added

(FYI, the binary for xetex is actually built by texlive-bin; texlive-xetex just installs a symlink. But that's not really relevant to the problem...)

It sounds like the problem is with your freetype port. libfreetype.6.dylib should be installed with compatibility version 14.0.0. Is your freetype port out of date? You might try reinstalling it.

comment:4 Changed 12 years ago by ryandesign (Ryan Carsten Schmidt)

You didn't provide any info about your system, but it sounds a lot like xelatex was originally built with MacPorts freetype (which provides libfreetype.6.dylib library version 14), but now for some reason xelatex is trying to use Mac OS X's freetype in /usr/X11/lib (which provides libfreetype.6.dylib library version 13 which is too old). One common reason why this would happen is if you originally installed MacPorts and freetype for a different architecture, for example on Leopard or earlier, and then migrated to Snow Leopard or later, and didn't then reinstall all ports as shown in the migration instructions.

comment:5 in reply to:  2 ; Changed 12 years ago by ryandesign (Ryan Carsten Schmidt)

Replying to jbolden1517@…:

So I suspect the freetype dependency in the texlive-bin port should be changed to require a later version.

MacPorts does not have the capability to specify the version of a dependency.

comment:6 in reply to:  5 ; Changed 12 years ago by jbolden1517@…

Replying to ryandesign@…:

Replying to jbolden1517@…:

So I suspect the freetype dependency in the texlive-bin port should be changed to require a later version.

MacPorts does not have the capability to specify the version of a dependency.

Oh, didn't know that. Are you sure? Because I certainly have installed stuff and chains of other stuff got updated?

Anyway I'm good. Before I submitted the bug I did a port update. Just wanted to pass this along since it is subtle.

comment:7 in reply to:  6 Changed 12 years ago by ryandesign (Ryan Carsten Schmidt)

Replying to jbolden1517@…:

Replying to ryandesign@…:

MacPorts does not have the capability to specify the version of a dependency.

Oh, didn't know that. Are you sure?

Yes. MacPorts can only install the currently available version of a port. To install older versions, you must follow the manual wiki:howto/InstallingOlderPort procedure.

Because I certainly have installed stuff and chains of other stuff got updated?

Yes, MacPorts updates dependencies first, in the correct order, if they're outdated.

Anyway I'm good. Before I submitted the bug I did a port update. Just wanted to pass this along since it is subtle.

So wait, you've already resolved the problem you reported in this ticket? By updating outdated ports? If so, then there is no bug here.

comment:8 Changed 12 years ago by drkp (Dan Ports)

Resolution: invalid
Status: newclosed
Note: See TracTickets for help on using tickets.