configure of gedit (with the vala use flag, but manually running ./configure --enable-vala=yes) says ...
checking whether to forbid deprecated symbols... no
checking for itstool... itstool
checking for xmllint... xmllint
checking for gobject-introspection... yes
checking for pkg-config... (cached) /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
configure: error: vapigen >= 0.25.1 not found
Taro gedit-3.14.0 # vapigen-0.2
vapigen-0.22 vapigen-0.24 vapigen-0.26
OK, here is the section of ./configure that is failing. Notice all the tests that don't have variables in them.
esac
if test "x" = "x"; then :
vapigen_pkg_name=vapigen
else
vapigen_pkg_name=vapigen-
fi
if test "x0.25.1" = "x"; then :
vapigen_pkg="$vapigen_pkg_name"
else
vapigen_pkg="$vapigen_pkg_name >= 0.25.1"
fi
Is this a bug in the ebuild? If so, how did it get unmasked? Or is there no unit testing to make sure each USE flag works?
Question
uudruid74
configure of gedit (with the vala use flag, but manually running ./configure --enable-vala=yes) says ...
OK, here is the section of ./configure that is failing. Notice all the tests that don't have variables in them.
Is this a bug in the ebuild? If so, how did it get unmasked? Or is there no unit testing to make sure each USE flag works?
Link to comment
Share on other sites
8 answers to this question
Recommended Posts