problems with regular expressions on OpenBSD/sparc

problems with regular expressions on OpenBSD/sparc

[David Lebel]

Hello,

I have some problems with zsh 4.0.x on OpenBSD/sparc but not on
OpenBSD/i386.  The problem is simple, the regular expression code
doesn't seem to work on sparc:

sparc:

  zsh% ls *
  zsh: no matches found: *

i386:

  zsh% ls *
  file1  file2  file3

What part of zsh is specifically called when doing * evaluation ? 

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 //

Re: problems with regular expressions on OpenBSD/sparc

[Bart Schaefer]

On Jul 7,  9:19am, David Lebel wrote:
} Subject: problems with regular expressions on OpenBSD/sparc
}
} sparc:
} 
}   zsh% ls *
}   zsh: no matches found: *

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?

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

Re: problems with regular expressions on OpenBSD/sparc

[David Lebel]

Quoting Bart Schaefer (schaefer@candle.brasslantern.com):
> What does
> 
>     grep DIR config.h
> 
> show you?

for OpenBSD/sparc:

---cut---
 STACK_DIRECTION > 0 => grows toward higher addresses
 STACK_DIRECTION < 0 => grows toward lower addresses
 STACK_DIRECTION = 0 => direction of growth unknown
/* #undef STACK_DIRECTION */
#define HAVE_STRUCT_DIRENT_D_INO 1
/* #undef HAVE_STRUCT_DIRENT_D_STAT */
/* #undef HAVE_STRUCT_DIRECT_D_INO */
/* #undef HAVE_STRUCT_DIRECT_D_STAT */
/* #undef MAILDIR_SUPPORT */
#define HAVE_FCHDIR 1
#define HAVE_DIRENT_H 1
/* #undef HAVE_NDIR_H */
/* #undef HAVE_SYS_DIR_H */
/* #undef HAVE_SYS_NDIR_H */
---cut---

For OpenBSD/i386:

---cut---
 STACK_DIRECTION > 0 => grows toward higher addresses
 STACK_DIRECTION < 0 => grows toward lower addresses
 STACK_DIRECTION = 0 => direction of growth unknown
/* #undef STACK_DIRECTION */
#define HAVE_STRUCT_DIRENT_D_INO 1
/* #undef HAVE_STRUCT_DIRENT_D_STAT */
/* #undef HAVE_STRUCT_DIRECT_D_INO */
/* #undef HAVE_STRUCT_DIRECT_D_STAT */
/* #undef MAILDIR_SUPPORT */
#define HAVE_FCHDIR 1
#define HAVE_DIRENT_H 1
/* #undef HAVE_NDIR_H */
/* #undef HAVE_SYS_DIR_H */
/* #undef HAVE_SYS_NDIR_H */
---cut---

Looks the same to me.

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 //

Re: problems with regular expressions on OpenBSD/sparc

[David Lebel]

Quoting Bart Schaefer (schaefer@candle.brasslantern.com):
> 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 //

Re: problems with regular expressions on OpenBSD/sparc

[Andrej Borsenkow]

On Sat, 7 Jul 2001, David Lebel wrote:

>
> I should also point out that this too doesn't work:
>
> VAR=foobar
>
> case $VAR in
>   foo*)
>     echo "got foo'ed"
>     ;;
> esac
>

As the very wild guess - have you tried --disable-lfs?

-andrej

Re: problems with regular expressions on OpenBSD/sparc

[David Lebel]

Quoting Andrej Borsenkow (Andrej.Borsenkow@mow.siemens.ru):
> As the very wild guess - have you tried --disable-lfs?

Just did, and still the same.

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 //