tech@mandoc.bsd.lv
 help / color / mirror / Atom feed
From: Steffen Nurpmeso <steffen@sdaoden.eu>
To: Ingo Schwarze <schwarze@usta.de>
Cc: tech@mdocml.bsd.lv
Subject: Re: Fwd: Small fixes for ssh.1 and ssh_config.5, OpenSSH_7.2p2
Date: Thu, 31 Mar 2016 19:16:12 +0200	[thread overview]
Message-ID: <20160331171612.lDtx_6hBm%steffen@sdaoden.eu> (raw)
In-Reply-To: <20160331162411.GG22000@athene.usta.de>

Hallo Ingo.

Ingo Schwarze <schwarze@usta.de> wrote:
 |Steffen Nurpmeso wrote on Wed, Mar 30, 2016 at 11:26:28AM +0200:
 |>   --- a/configure
 |>   +++ b/configure
 |>   @@ -235,7 +235,7 @@ fi
 |>    
 |>    # --- ohash ---
 |>    if [ ${BUILD_DB} -eq 0 ]; then
 |>   -       HAVE_OHASH=1
 |>   +       HAVE_OHASH=0
 |>    elif ismanual ohash "${HAVE_OHASH}"; then
 |>:
 |>    elif [ -n "${DBLIB}" ]; then
 |
 |Don't do that.
 |
 |If automatic HAVE_OHASH detection doesn't work for you,
 |just put
 |
 |  HAVE_OHASH=0
 |
 |into
 |
 |  configure.local

That didn't work?  It was overwritten later on.
You fixed it?  No.

 |See INSTALL and configure.local.example for how the system works.

Yes i did (PAIN).  Even after finding out that some of the
variables exist multiple times and you have to uniq them first.
I made the great and compiled mandoc several times in the past
already.  ^_^
Ciao, Ingo.

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

  reply	other threads:[~2016-03-31 17:16 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-29 19:25 Steffen Nurpmeso
2016-03-29 19:44 ` Steffen Nurpmeso
2016-03-30  9:26   ` Steffen Nurpmeso
2016-03-31 16:24     ` Ingo Schwarze
2016-03-31 17:16       ` Steffen Nurpmeso [this message]
2016-03-31 16:20 ` Ingo Schwarze
2016-03-31 17:11   ` Steffen Nurpmeso
2016-03-31 17:38     ` Ingo Schwarze
2016-03-31 19:24       ` Steffen Nurpmeso
2016-03-31 20:04         ` hans
2016-04-01 12:46           ` Steffen Nurpmeso
2016-04-01 12:53             ` hans

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=20160331171612.lDtx_6hBm%steffen@sdaoden.eu \
    --to=steffen@sdaoden.eu \
    --cc=schwarze@usta.de \
    --cc=tech@mdocml.bsd.lv \
    /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
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).