From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-workers@sunsite.dk (Zsh hackers list)
Subject: Re: jobs not listing all commands
Date: Wed, 18 Feb 2004 17:47:08 +0000 [thread overview]
Message-ID: <1040218174708.ZM13219@candle.brasslantern.com> (raw)
In-Reply-To: <25456.1077099894@csr.com>
On Feb 18, 10:24am, Peter Stephenson wrote:
}
} It's probably a case of missing headers. It wouldn't link, or would fail
} to load with an error message, if you didn't have the functions; there's
} no obvious way it could hang. In RedHat 9 and Solaris 8 the headers are
} in stdlib.h (and they're certainly to hand in the other two Linux systems
} I tried at home).
Aha. They're in <stdlib.h> but they're inside #ifdef __USE_XOPEN ... which
is defined by <features.h> only when _XOPEN_SOURCE is defined ... which is
meant to be defined directly by the user, or is defined when _GNU_SOURCE is
defined.
} I'm not sure how to test for this. Maybe it would be enough to try
} compiling and linking a programme with grantpt etc., since I think
} configure is sensitive to compiler warnings.
While a missing-header test is probably appropriate, in this case I think
the issue is whether zsh wants to define _XOPEN_SOURCE, and if not, then
it shouldn't use /dev/ptmx even when the device exists.
next prev parent reply other threads:[~2004-02-18 17:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-17 7:58 Felix Rosencrantz
2004-02-17 10:41 ` Peter Stephenson
2004-02-17 22:14 ` Bart Schaefer
2004-02-18 0:25 ` James Devenish
2004-02-18 0:41 ` Wayne Davison
2004-02-18 6:02 ` Bart Schaefer
2004-02-18 10:24 ` Peter Stephenson
2004-02-18 17:47 ` Bart Schaefer [this message]
2004-02-18 22:02 ` Peter Stephenson
2004-02-20 15:21 ` PATCH: ptmx part 2 Peter Stephenson
2004-02-19 15:22 ` jobs not listing all commands Felix Rosencrantz
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=1040218174708.ZM13219@candle.brasslantern.com \
--to=schaefer@brasslantern.com \
--cc=zsh-workers@sunsite.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).