Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: problems with regular expressions on OpenBSD/sparc
- X-seq: zsh-workers 15299
- From: David Lebel <lebel@xxxxxxxxx>
- To: Bart Schaefer <schaefer@xxxxxxxxxxxxxxxxxxxxxxx>
- Subject: Re: problems with regular expressions on OpenBSD/sparc
- Date: Sat, 7 Jul 2001 12:39:08 -0400
- Cc: zsh-workers@xxxxxxxxxx
- In-reply-to: <1010707160002.ZM14524@xxxxxxxxxxxxxxxxxxxxxxx>; from schaefer@xxxxxxxxxxxxxxxxxxxxxxx on Sat, Jul 07, 2001 at 04:00:01PM +0000
- Mailing-list: contact zsh-workers-help@xxxxxxxxxx; run by ezmlm
- Organization: None whatsover.
- References: <20010707091954.K8090@xxxxxxxxx> <1010707160002.ZM14524@xxxxxxxxxxxxxxxxxxxxxxx>
Quoting Bart Schaefer (schaefer@xxxxxxxxxxxxxxxxxxxxxxx):
> This usually means something's wrong with the way `struct dirent' or the
> equivalent is being interpreted when zsh is reading file names from a
> directory. I've seen this happen on Solaris because both SysV and BSD
> style directory routines are available and you can get the wrong one
> depending on which C compiler is first in your $PATH, but I'm surprised
> it's happened on OpenBSD.
>
> What does
>
> grep DIR config.h
>
> show you?
I should also point out that this too doesn't work:
VAR=foobar
case $VAR in
foo*)
echo "got foo'ed"
;;
esac
on i386 gives:
got foo'ed
whereas on sparc, it gives nothing.
Ciao,
...David
--
// david lebel <lebel@{lebel.org,nobiaze.com,openbsd.org}> //
// http://www.lebel.org/ http://www.nobiaze.com/ //
// pgp: 3633 6999 D47E 73ED 099F 4341 08A4 8E48 EF56 61D1 //
Messages sorted by:
Reverse Date,
Date,
Thread,
Author