zsh-users
 help / color / mirror / code / Atom feed
From: Borsenkow Andrej <Andrej.Borsenkow@mow.siemens.ru>
To: "'Ackersviller, Paul:'" <packersv@ppco.com>, zsh-users@sunsite.dk
Subject: RE: 4.0.4 configuration on AIX 5.1
Date: Wed, 10 Apr 2002 10:22:24 +0400	[thread overview]
Message-ID: <000401c1e058$15c88050$1fc1f2a3@mow.siemens.ru> (raw)
In-Reply-To: <8A6886DD01F4D511A0FC00508BBB3FC101229DC4@phxntx04.mkt.tosco.com>

> 
> I'm running into some trouble building zsh on AIX 5.1 due to the code
in
> Src/utils.c and Src/Modules/cap.c inside #ifdef HAVE_CAP_GET_PROC.
> There are two strange things I notice about this system.  First,
there's a
> <sys/capabilities.h> that seems to replace <sys/capability.h>, but it
won't
> work to include this instead because it typedefs cap_t as void *,
while not
> having a prototype for cap_get_proc().
> 

autoconf 2.5x has standard tests for declaration (AC_CHECK_DECL). I am
not sure if autoconf-2.13 includes them. If not I am afraid adding extra
tests won't do for 4.0.x (too much change).

> This system also has no libcap library, although there is a
cap_get_proc
> directly in the C library (which I assume configure is finding).
However
> I'm unable to find documentation on it, nor can I find a prototype for
it
> anywhere in the system headers.
> 
> Anyway, I can compile zsh by taking the HAVE_CAP_GET_PROC
> definition out of config.h and building in Src/.  Does anyone think
the
> configure script should be able to handle this system, or is it too
broken?
> 

You could also remove cap nodule from modules.list. I guess it should go
into Etc/MACHINES then. 

Or you could add explicit tests to zsh/cap for AIX 5.1 to skip building
it on this system. It is ugly but it is better that nothing.

-andrej


      reply	other threads:[~2002-04-10  6:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-09 23:37 Ackersviller, Paul:
2002-04-10  6:22 ` Borsenkow Andrej [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='000401c1e058$15c88050$1fc1f2a3@mow.siemens.ru' \
    --to=andrej.borsenkow@mow.siemens.ru \
    --cc=packersv@ppco.com \
    --cc=zsh-users@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).