Opened 11 years ago

Closed 11 years ago

Last modified 11 years ago

#41993 closed defect (duplicate)

mplayer & mplayer-devel build without fontconfig/freetype/libass support

Reported by: jchauvel@… Owned by: macports-tickets@…
Priority: Normal Milestone:
Component: ports Version: 2.2.1
Keywords: Cc: acho@…, jeremyhu (Jeremy Huddleston Sequoia), jchauvel@…
Port: mplayer-devel

Description

None of this ports take into account the +osd variant while configuring mplayer. There appears to be a false negative bug while detecting fontconfig, I believe this has to do with the fontconfig port installing all of its headers on ${prefix}/include/fontconfig2 instead of ${prefix}/include/fontconfig.

Even when force enabling fontconfig, freetype and libass the linker failed due to not being able to find libass symbols, although I managed to build mplayer successfully after including the -lass flag.

Attachments (2)

config.log (287.2 KB) - added by jchauvel@… 11 years ago.
main.log (742.3 KB) - added by jchauvel@… 11 years ago.

Download all attachments as: .zip

Change History (7)

comment:1 Changed 11 years ago by jchauvel@…

Cc: jchauvel@… added

Cc Me!

comment:2 Changed 11 years ago by jchauvel@…

My mistake! freetype2 was the conflicting directory, not fontconfig2.

Last edited 11 years ago by jchauvel@… (previous) (diff)

comment:3 Changed 11 years ago by jchauvel@…

The freetype/fontconfig part seems duplicate of #41746 and #39307

Last edited 11 years ago by jchauvel@… (previous) (diff)

Changed 11 years ago by jchauvel@…

Attachment: config.log added

Changed 11 years ago by jchauvel@…

Attachment: main.log added

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

Cc: openmaintainer@… removed
Keywords: mplayer mplayer-dev fontconfig freetype libass removed
Priority: HighNormal
Resolution: duplicate
Status: newclosed

Duplicate of #41746.

comment:5 in reply to:  4 Changed 11 years ago by jchauvel@…

Replying to ryandesign@…:

Duplicate of #41746.

So it seems, but what about the libass issue?

Note: See TracTickets for help on using tickets.