zsh-workers
 help / color / mirror / code / Atom feed
From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: Oliver Kiddle <opk@u.genie.co.uk>,
	Zsh workers <zsh-workers@sunsite.auc.dk>
Subject: Re: zparseopts (Re: PATCH: _urls and _rpm)
Date: Wed, 7 Jun 2000 05:55:58 +0000	[thread overview]
Message-ID: <1000607055558.ZM7727@candle.brasslantern.com> (raw)
In-Reply-To: <393CCB47.43BD74D7@u.genie.co.uk>

On Jun 6, 10:58am, Oliver Kiddle wrote:
} Subject: Re: zparseopts (Re: PATCH: _urls and _rpm)
}
} On the subject of my IRIX 5.3 compilation warnings, Bart Schaefer wrote:
} > What does line 111 of sys/types.h look like?
} 
} typedef unsigned long   ino_t;          /* <inode> type */
} 
} If you look back it my previous message (11755), you'll see that I had
} stuck a section of types.h in at the end.

Oops, I thought that was part of the diff and never even looked at it.

} after a preprocessor check for _MIPS_SZLONG == 32.

Where does _MIPS_SZLONG come from?

The test for ino_t passes this:

#include "confdefs.h"
#include <sys/types.h>
#if STDC_HEADERS
#include <stdlib.h>
#include <stddef.h>
#endif

through the preprocessor and then egreps to find ino_t.  From the snippet
you sent, the egrep should fail only if _MIPS_SZLONG is neither 32 nor 64.
Unless IRIX's egrep is broken, which is not impossible ...

-- 
Bart Schaefer                                 Brass Lantern Enterprises
http://www.well.com/user/barts              http://www.brasslantern.com

Zsh: http://www.zsh.org | PHPerl Project: http://phperl.sourceforge.net   


  reply	other threads:[~2000-06-07  5:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-06-05 22:09 PATCH: _urls and _rpm Oliver Kiddle
2000-06-06  3:48 ` Bart Schaefer
2000-06-06  4:08 ` zparseopts (Re: PATCH: _urls and _rpm) Bart Schaefer
2000-06-06  9:58   ` Oliver Kiddle
2000-06-07  5:55     ` Bart Schaefer [this message]
2000-06-06  7:15 Sven Wischnowsky

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=1000607055558.ZM7727@candle.brasslantern.com \
    --to=schaefer@candle.brasslantern.com \
    --cc=opk@u.genie.co.uk \
    --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).