I tried to emerge the new (thanks, btw) ebuild for miro, and the compile (in fact, configure) fails because it searches ming, and can't found it. This is quite strange because ming 0.3.0-r1 is installed on my system. Reproducible: Always Steps to Reproduce: 1. emerge miro >>> Emerging (1 of 1) media-video/miro-2.5.3 * miro-2.5.3.tar.gz RMD160 SHA1 SHA256 size ;-) ... [ ok ] * checking ebuild checksums ;-) ... [ ok ] * checking auxfile checksums ;-) ... [ ok ] * checking miscfile checksums ;-) ... [ ok ] >>> Unpacking source... >>> Unpacking miro-2.5.3.tar.gz to /var/tmp/portage/media-video/miro-2.5.3/work >>> Source unpacked in /var/tmp/portage/media-video/miro-2.5.3/work >>> Preparing source in /var/tmp/portage/media-video/miro-2.5.3/work/miro-2.5.3/platform/gtk-x11 ... * Applying miro-2.5.3-fix-locale.patch ... [ ok ] * Applying miro-2.5.3-fix-debug.patch ... [ ok ] * Applying miro-2.5.3-disable-xine-hack.patch ... [ ok ] * Applying miro-2.5.3-dont-install-test-files.patch ... [ ok ] * Applying miro-2.5.3-remove-unittest-option.patch ... [ ok ] >>> Source prepared. >>> Configuring source in /var/tmp/portage/media-video/miro-2.5.3/work/miro-2.5.3/platform/gtk-x11 ... >>> Source configured. >>> Compiling source in /var/tmp/portage/media-video/miro-2.5.3/work/miro-2.5.3/platform/gtk-x11 ... python setup.py build /usr/lib/python2.6/site-packages/Pyrex/Compiler/Errors.py:17: DeprecationWarning: BaseException.message has been deprecated as of Python 2.6 self.message = message Using boost_python-mt libtorrent-rasterbar (0.13 or later) and python bindings are installed--using system version. Package config error: pkg-config --list-all outputted the following error: Package ming was not found in the pkg-config search path. Perhaps you should add the directory containing `ming.pc' to the PKG_CONFIG_PATH environment variable Package 'ming', required by 'Autotrace', not found * * ERROR: media-video/miro-2.5.3 failed. * Call stack: * ebuild.sh, line 49: Called src_compile * environment, line 3229: Called distutils_src_compile * environment, line 724: Called die * The specific snippet of code: * ${python} setup.py "${DISTUTILS_GLOBAL_OPTIONS[@]}" build "$@" || die "Building failed"; * The die message: * Building failed * * If you need support, post the topmost build error, and the call stack if relevant. * A complete build log is located at '/var/tmp/portage/media-video/miro-2.5.3/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/media-video/miro-2.5.3/temp/environment'. * >>> Failed to emerge media-video/miro-2.5.3, Log file: >>> '/var/tmp/portage/media-video/miro-2.5.3/temp/build.log' * Messages for package media-video/miro-2.5.3: * * ERROR: media-video/miro-2.5.3 failed. * Call stack: * ebuild.sh, line 49: Called src_compile * environment, line 3229: Called distutils_src_compile * environment, line 724: Called die * The specific snippet of code: * ${python} setup.py "${DISTUTILS_GLOBAL_OPTIONS[@]}" build "$@" || die "Building failed"; * The die message: * Building failed * * If you need support, post the topmost build error, and the call stack if relevant. * A complete build log is located at '/var/tmp/portage/media-video/miro-2.5.3/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/media-video/miro-2.5.3/temp/environment'. *
Actually, it's not linked to miro and miro doesn't need ming. It's because miro is running 'pkg-config --list-all' and it looks like you have a problem with pkg-config. I had the same issue (not with ming but something else). Run 'pkg-config --list-all > /dev/null' in a terminal. You will see only the errors. Then, you can fix them by removing the .pc files for example if the package isn't installed anymore. I've opened a bug upstream (see $URL) so they can use a better solution than running 'pkg-config --list-all' but you will understand it's not really a bug as it's an issue with your system. I'm going to mark the bug as resolved but do not hesitate to add a comment or send me an email if you need more information.
I tried this, but : # pkg-config --list-all > /dev/null Package ming was not found in the pkg-config search path. Perhaps you should add the directory containing `ming.pc' to the PKG_CONFIG_PATH environment variable Package 'ming', required by 'Autotrace', not found So I don't know what to do, since ming.pc is not on my system (as ming does not install this file).
(In reply to comment #2) > I tried this, but : > > # pkg-config --list-all > /dev/null > Package ming was not found in the pkg-config search path. > Perhaps you should add the directory containing `ming.pc' > to the PKG_CONFIG_PATH environment variable > Package 'ming', required by 'Autotrace', not found > > So I don't know what to do, since ming.pc is not on my system (as ming does not > install this file). > "Package 'ming', required by 'Autotrace', not found" Do you have media-gfx/autotrace installed ? Because autotrace needs ming. Probably linked...
Installed because lilypond is installed : # equery depends ming [ Searching for packages depending on ming... ] media-gfx/autotrace-0.31.1-r3 (>=media-libs/ming-0.3.0) # equery depends autotrace [ Searching for packages depending on autotrace... ] app-text/mftrace-1.2.13 (>=media-gfx/autotrace-0.30) # equery depends mftrace [ Searching for packages depending on mftrace... ] media-sound/lilypond-2.12.2 (>=app-text/mftrace-1.2.9) equery depends lilypond [ Searching for packages depending on lilypond... ] (no output) All of those packages are stable versions. I will try to unmerge all, emerge miro then lilypond.
Wow. Something was not clean on my system : emerge -av lilypond These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild N ] media-gfx/potrace-1.8 USE="-metric" 340 kB [ebuild N ] app-text/mftrace-1.2.13 USE="truetype" 0 kB [ebuild N ] media-sound/lilypond-2.12.2 USE="-debug -emacs -profile" 0 kB Nor ming nor autotrace anymore. That's ok for me. Should I close this bug ? Wondering if I need to open a bug for mftrace ...
(In reply to comment #5) > Wow. > Something was not clean on my system : > > emerge -av lilypond > > These are the packages that would be merged, in order: > > Calculating dependencies... done! > [ebuild N ] media-gfx/potrace-1.8 USE="-metric" 340 kB > [ebuild N ] app-text/mftrace-1.2.13 USE="truetype" 0 kB > [ebuild N ] media-sound/lilypond-2.12.2 USE="-debug -emacs -profile" 0 kB > > Nor ming nor autotrace anymore. > That's ok for me. > > Should I close this bug ? Wondering if I need to open a bug for mftrace ... > This bug is already marked as "resolved". It doesn't sound like there is an issue with mftrace but more like something went bad with your system.
