Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 161496 - media-video/mkvtoolnix-1.8.1 ./configure fails on libpcre
Summary: media-video/mkvtoolnix-1.8.1 ./configure fails on libpcre
Status: RESOLVED DUPLICATE of bug 155965
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: New packages (show other bugs)
Hardware: AMD64 Linux
: High normal (vote)
Assignee: Gentoo Linux bug wranglers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-01-11 10:15 UTC by Thomas Capricelli
Modified: 2007-01-11 10:29 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Thomas Capricelli 2007-01-11 10:15:30 UTC 
configure fails with:

=========
checking for FLAC__stream_decoder_skip_single_frame in -lFLAC... yes
checking for pcre-config... /usr/bin/pcre-config
checking for libpcrecpp... no
configure: error: Could not find the PCRE C++ library

!!! Please attach the following file when filing a report to bugs.gentoo.org:
!!! /tmp/portage/media-video/mkvtoolnix-1.8.1/work/mkvtoolnix-1.8.1/config.log

!!! ERROR: media-video/mkvtoolnix-1.8.1 failed.
============

while i have dev-libs/libpcre correctly installed.
Looking in the config.log, i can read
/usr/include/pcre_stringpiece.h:50:30: error: bits/type_traits.h: No such file or directory

using locate i can see :
/usr/lib64/gcc/x86_64-pc-linux-gnu/3.4.4/include/g++-v3/bits/type_traits.h
/usr/lib64/gcc/x86_64-pc-linux-gnu/3.4.4/include/g++-v3/bits/cpp_type_traits.h
/usr/lib64/gcc/x86_64-pc-linux-gnu/4.0.3/include/g++-v4/bits/cpp_type_traits.h

and i'm using gcc 4.0.3

i dont really know how to fix this.. 

Reproducible: Always
Comment 1 Thomas Capricelli 2007-01-11 10:27:41 UTC 
note : re-emerging libpcre fixed it. I dont understand why.. but it does.
Comment 2 Jakub Moc (RETIRED) gentoo-dev 2007-01-11 10:29:48 UTC 

*** This bug has been marked as a duplicate of bug 155965 ***