Opened 12 years ago

Closed 12 years ago

#36771 closed defect (fixed)

mediatomb: build fails if mongodb is installed

Reported by: yorkshirespud@… Owned by: yattenator@…
Priority: Normal Milestone:
Component: ports Version: 2.1.2
Keywords: Cc: ryandesign (Ryan Carsten Schmidt), elvadrias@…, skoczko@…, nilstec_inc@…
Port: mediatomb

Description (last modified by mf2k (Frank Schima))

I have upgraded my Mac from Snow Leopard 10.6.2 to Mountain Lion 10.8.2, and have successfully followed the migration instructions and rebuilt all my ports from scratch.

Every single one of my ports has built, except for MediaTomb.

The first of several build errors is:

:info:build In file included from ../src/transcoding/transcode_ext_handler.cc:39:
:info:build /opt/local/include/server.h:12:3: error: #error this file is for mongo server programs not client lib

Any ideas?

Attachments (2)

main.log (88.4 KB) - added by yorkshirespud@… 12 years ago.
main.2.log (12.3 KB) - added by skoczko@… 12 years ago.
/_opt_local_var_macports_sources_rsync.macports.org_release_ports_net_mediatomb/mediatomb/

Download all attachments as: .zip

Change History (17)

Changed 12 years ago by yorkshirespud@…

Attachment: main.log added

comment:1 Changed 12 years ago by mf2k (Frank Schima)

Description: modified (diff)
Owner: changed from macports-tickets@… to yattenator@…
Port: mediatomb added

In the future, please use WikiFormatting, fill in the Port field and Cc the port maintainer(s).

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

Cc: ryandesign@… added

Cc Me!

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

ffmpeg was just updated to version 1.0; I would not be surprised if this version of mediatomb is not compatible with it.

comment:4 Changed 12 years ago by Pesthauch666@…

Yes, most likely ffmpeg 1.0 is the reason, why mediatomb fails to build. I've got the same problem with mediatomb and transcode as well. Even the already installed older version (0.12.1_5) of mediatomb throws errors since I installed ffmpeg 1.0:

dyld: lazy symbol binding failed: Symbol not found: _av_open_input_file
  Referenced from: /opt/local/bin/mediatomb
  Expected in: /opt/local/lib/libavformat.dylib

dyld: Symbol not found: _av_open_input_file
  Referenced from: /opt/local/bin/mediatomb
  Expected in: /opt/local/lib/libavformat.dylib
Last edited 12 years ago by ryandesign (Ryan Carsten Schmidt) (previous) (diff)

comment:5 Changed 12 years ago by elvadrias@…

Cc: elvadrias@… added

Cc Me!

comment:6 Changed 12 years ago by skoczko@…

The same issue is present on SL with ports 2.1.2. It looks like the problem is ffmpeg related.

Changed 12 years ago by skoczko@…

Attachment: main.2.log added

/_opt_local_var_macports_sources_rsync.macports.org_release_ports_net_mediatomb/mediatomb/

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

Summary: Mediatomb does not install on Mountain Lion 10.8.2mediatomb: build fails with latest ffmpeg

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

Actually there are two separate unrelated problems described in this ticket: the ffmpeg 1.0 incompatibility, and the "/opt/local/include/server.h:12:3: error: #error this file is for mongo server programs not client lib" error in the ticket description, which is a file naming conflict with the mongodb port (deactivate the mongodb port while building mediatomb to overcome this).

comment:9 Changed 12 years ago by skoczko@…

Cc: skoczko@… added

Cc Me!

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

The order of the include flags is wrong if an external header is being found instead of an identically-named internal one.

comment:11 Changed 12 years ago by nilstec_inc@…

Mediatomb fails to compile after upgrading to mountain lion. I described my error here: ticket:33735#comment:7.

comment:12 Changed 12 years ago by nilstec_inc@…

Cc: nilstec_inc@… added

Cc Me!

comment:13 Changed 12 years ago by dbevans (David B. Evans)

See #37457 for a solution to to the ffmpeg problem.

comment:14 Changed 12 years ago by dbevans (David B. Evans)

Summary: mediatomb: build fails with latest ffmpegmediatomb: build fails if mongodb is installed

Fix for ffmpeg problem committed in r101437, maintainer timeout. Build continues to fail if port mongodb is installed and active.

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

Resolution: fixed
Status: newclosed

Replying to jmr@…:

The order of the include flags is wrong if an external header is being found instead of an identically-named internal one.

Yes. Pending a proper solution to that, I've marked the port as "conflicts_build mongodb" in r102424.

Note: See TracTickets for help on using tickets.