Some debugging tips:
- do configure, make, make install by hand to see what's going on.
- have a look at what config.log (generated by configure) contains.
- ./configure --help gives you the configure parameters
Cheers,
Uli
Janssen Vanderhooft wrote:
> Hello,
>
> I am trying to install libavg on a fresh installation of Gentoo (a
> minimal installation under VirtualBox). After building all the
> dependencies, the configuration of libavg fails while checking for
> boost.thread. I'm new to Gentoo, but I want to use libavg on it to make
> some lean, interactive kiosks. I even tried prefixing ``emerge libavg''
> with ``EXTRA_ECONF="--with-boost-thread=mt"'' as suggested in the TODO
> comment in the ebuild file, but that just caused another error.
>
> I'm copying the end of my build.log below. Can anyone help be build
> libavg on Gentoo? Thanks in advance.
> -------------------------------------------------------------------------
> checking for python... /usr/bin/python
> checking for python version... 2.4
> checking for python platform... linux2
> checking for python script directory...
> ${prefix}/lib/python2.4/site-packages
> checking for python extension module directory...
> ${exec_prefix}/lib/python2.4/site-packages
> checking for headers required to compile python extensions... found
> checking for libpython2.4... found
> checking for main in -lboost_python... yes
> checking whether the compiler implements namespaces... yes
> checking whether the Boost::Thread library is available... yes
> checking for main in -lboost_thread... no
> configure: error: boost.thread not found. Aborting.
>
> !!! Please attach the following file when filing a report to
> bugs.gentoo.org:
> !!! /var/tmp/portage/media-libs/libavg-0.7.0/work/libavg-0.7.0/config.log
> *
> * ERROR: media-libs/libavg-0.7.0 failed.
> * Call stack:
> * ebuild.sh, line 1701: Called dyn_compile
> * ebuild.sh, line 1039: Called qa_call 'src_compile'
> * ebuild.sh, line 44: Called src_compile
> * libavg-0.7.0.ebuild, line 34: Called econf '--disable-dc1394'
> * ebuild.sh, line 638: Called die
> * The specific snippet of code:
> * die "econf failed"
> * The die message:
> * econf 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-libs/libavg-0.7.0/temp/build.log'.
> * This ebuild is from an overlay: '/usr/local/portage/'
> *
> -------------------------------------------------------------------------------
>
> _______________________________________________
> libavg-users mailing list
> [email protected]
> https://mail.datenhain.de/mailman/listinfo/libavg-users
>
--
Ulrich von Zadow | +49-172-7872715
Jabber: [EMAIL PROTECTED]
Skype: uzadow
_______________________________________________
libavg-users mailing list
[email protected]
https://mail.datenhain.de/mailman/listinfo/libavg-users
