zsh-workers
 help / color / mirror / code / Atom feed
From: Geoff Wing <gcw@pobox.com>
To: Bart Schaefer <schaefer@candle.brasslantern.com>
Cc: zsh-workers@sunsite.auc.dk
Subject: Re: zsh configuration
Date: Thu, 12 Aug 1999 09:50:45 +1000	[thread overview]
Message-ID: <19990812095045.A26972@primenet.com.au> (raw)
In-Reply-To: <990811163357.ZM2163@candle.brasslantern.com>; from Bart Schaefer on Wed, Aug 11, 1999 at 04:33:57PM +0000

Bart Schaefer wrote about Re: zsh configuration:
:On Aug 11,  3:37pm, Geoff Wing wrote:
:} Subject: Re: zsh configuration
:} Wim Yedema <yedema@natlab.research.philips.com> typed:
:} :#define HAVE_DLFCN_H 0
:} :#ifdef HAVE_DLFCN_H
:} :# include <dlfcn.h>
:} :#else
:} :# ifdef HAVE_DL_H
:} This looks perfectly OK to me.  <dlfcn.h> is used in preference to <dl.h>.
:} What's supposed to be wrong about it?

To get ``#define HAVE_DLFCN_H 0'' with the ``0'' there you would have to
have edited config.h and ignored the comment on the previous line:
	/* Define if you have the <dlfcn.h> header file.  */
because that generated lines are either ``#define ... 1'' or
``/* #undef ... */''.   ``#define ... 0'' is not generated.

:It should be
:/* #undef HAVE_DLFCN_H */

I wasn't automatically presuming that it was user error (the opposite of
``define'' being ``not define''; not ``define as some other value'') and was
allowing for the case where it may have been a valid point.

Regards,
-- 
Geoff Wing : <gcw@pobox.com>     Work URL: http://www.primenet.com.au/
Rxvt Stuff : <gcw@rxvt.org>      Ego URL : http://pobox.com/~gcw/
Zsh Stuff  : <gcw@zsh.org>       Phone   : (Australia) 0413 431 874


      reply	other threads:[~1999-08-11 23:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-08-11 12:14 Wim Yedema
1999-08-11 15:37 ` Geoff Wing
1999-08-11 16:33   ` Bart Schaefer
1999-08-11 23:50     ` Geoff Wing [this message]

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=19990812095045.A26972@primenet.com.au \
    --to=gcw@pobox.com \
    --cc=schaefer@candle.brasslantern.com \
    --cc=zsh-workers@sunsite.auc.dk \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

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).