discuss@mandoc.bsd.lv
 help / color / mirror / Atom feed
From: hans <hans@stare.cz>
To: discuss@mdocml.bsd.lv
Subject: system without ohash.h has HAVE_OHASH
Date: Wed, 6 Apr 2016 16:16:14 +0200	[thread overview]
Message-ID: <20160406141614.GA73612@www.stare.cz> (raw)

Hi Ingo,

I am trying to compile mdocml (a fresh cvs checkout)
on a system withou ohash, namely CentOS 6.6.

Here is my configure.local

	PREFIX="${HOME}"
	HAVE_MANPATH=1
	BUILD_DB=0
	BUILD_CGI=0
	HAVE_OHASH=0

However, ./configure thinks HAVE_OHASH=1, because

	if [ ${BUILD_DB} -eq 0 ]; then
	        HAVE_OHASH=1

I believe that's broken:
"doesn't want the databases" -> we HAVE_OHASH
- but we don't.

The compilation fails with

  In file included from tag.c:30:
  mandoc_ohash.h:18:19: error: ohash.h: No such file or directory

Even the explicit HAVE_OHASH=0 does not fix it
- it gets overwritten by ./configure and config.h ends up with

  #define HAVE_OHASH 1

	Jan

--
 To unsubscribe send an email to discuss+unsubscribe@mdocml.bsd.lv

                 reply	other threads:[~2016-04-06 14:16 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20160406141614.GA73612@www.stare.cz \
    --to=hans@stare.cz \
    --cc=discuss@mdocml.bsd.lv \
    --subject='Re: system without ohash.h has HAVE_OHASH' \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).