mediatomb: build fails if mongodb is installed

[yorkshirespud@…]

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?

[mf2k (Frank Schima)]

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

[ryandesign (Ryan Carsten Schmidt)]

Cc Me!

[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.

[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

[elvadrias@…]

Cc Me!

[skoczko@…]

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

[skoczko@…]

/_opt_local_var_macports_sources_rsync.macports.org_release_ports_net_mediatomb/mediatomb/

[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).

[skoczko@…]

Cc Me!

[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.

[nilstec_inc@…]

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

[nilstec_inc@…]

Cc Me!

[dbevans (David B. Evans)]

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

[dbevans (David B. Evans)]

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

[ryandesign (Ryan Carsten Schmidt)]

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.