openbsd-ports/net/libpcapnav/Makefile
ajacoutot ef5cb32a0f Stupid autohell is stupid...
The situation is this: even when we --disable-gtk-doc, if gtk-doc is
actually installed at configure stage, tools like gtkdoc-rebase will be
picked up and run during the install target. That is bad because the
gtk-doc package may have been removed by then, especially during dpb(1)
bulks (we explicitely disable support for it so why should it stay...).

So for now, let's add the following env to configure whenever we use
--disable-gtk-doc, until a bettersolution is found...
CONFIGURE_ENV +=ac_cv_path_GTKDOC_CHECK="" \
		ac_cv_path_GTKDOC_REBASE="" \
		ac_cv_path_GTKDOC_MKPDF=""
2012-09-21 14:48:05 +00:00

32 lines
826 B
Makefile

# $OpenBSD: Makefile,v 1.9 2012/09/21 14:48:06 ajacoutot Exp $
COMMENT= library for navigating to arbitrary packets in a trace file
DISTNAME= libpcapnav-0.8
REVISION= 1
SHARED_LIBS= pcapnav 1.0
CATEGORIES= net
MASTER_SITES= ${MASTER_SITE_SOURCEFORGE:=netdude/}
HOMEPAGE= http://netdude.sourceforge.net/doco/libpcapnav/
# BSD
PERMIT_PACKAGE_CDROM= Yes
PERMIT_PACKAGE_FTP= Yes
PERMIT_DISTFILES_CDROM= Yes
PERMIT_DISTFILES_FTP= Yes
WANTLIB= pcap
USE_LIBTOOL= Yes
CONFIGURE_STYLE= gnu
CONFIGURE_ARGS+= --disable-gtk-doc --with-html-dir=${PREFIX}/share/doc/libpcapnav
# If one of these tools is found at configure stage, it might be used,
# no matter whether we use --disable-gtk-doc or not.
CONFIGURE_ENV +=ac_cv_path_GTKDOC_CHECK="" \
ac_cv_path_GTKDOC_REBASE="" \
ac_cv_path_GTKDOC_MKPDF=""
.include <bsd.port.mk>