On 01/09/2012 11:19 PM, Aron Xu wrote: > I believe here's some useful information in the log: > > checking libevocosm/evocosm.h usability... no > checking libevocosm/evocosm.h presence... yes > configure: WARNING: libevocosm/evocosm.h: present but cannot be compiled > configure: WARNING: libevocosm/evocosm.h: check for missing > prerequisite headers? > configure: WARNING: libevocosm/evocosm.h: see the Autoconf documentation > configure: WARNING: libevocosm/evocosm.h: section "Present But > Cannot Be Compiled" > configure: WARNING: libevocosm/evocosm.h: proceeding with the > preprocessor's result > configure: WARNING: libevocosm/evocosm.h: in the future, the compiler > will take precedence > configure: WARNING: ## ------------------------------------------ ## > configure: WARNING: ## Report this to the AC_PACKAGE_NAME lists. ## > configure: WARNING: ## ------------------------------------------ ## > checking for libevocosm/evocosm.h... yes > >
Thanks. I'm looking into this. Note that it is completely architecture-independent (i.e., that it was discovered with armhf is irrelevant -- it occurs on amd64 the same way. -- Ciao, al ---------------------------------------------------------------------- Al Stone Debian Developer E-mail: a...@ahs3.net http://www.debian.org a...@debian.org ---------------------------------------------------------------------- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
