[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Config.status on OS X
From: |
Sebastian Hagedorn |
Subject: |
Re: Config.status on OS X |
Date: |
Sat, 16 Jun 2001 19:44:24 +0200 |
OK,
from what we've learned I draw the following conclusions:
- the issue has got nothing to do with Mac OS X in itself, only with the
fact that Apple doesn't supply a 'sh' but instead a 'zsh' which sh is
symlinked to
- 'emulate sh' does not help
- the line "CDPATH=" from configure may be necessary to stop 'cd' from
being verbose with bash, but it's causing the opposite with zsh! Without
that line the script works, but setting it - even to the empty string -
causes zsh to print out the cwd
- adding the line "unset CDPATH" works
So, *if* adding the unset command doesn't break anything, I guess the
solution would be to add this line to the configure script.
Regarding autoconf: OS X comes with version 2.13. From what I've read
version 2.50 wouldn't have made a difference in this situation...
Greetings, Sebastian
--
Sebastian Hagedorn
Ehrenfeldgürtel 156, 50823 Köln, Germany
http://www.spinfo.uni-koeln.de/~hgd/
This mail was proudly sent using Mac OS X
- Re: Config.status on OS X,
Sebastian Hagedorn <=
- Re: Config.status on OS X, Akim Demaille, 2001/06/18
- Re: Config.status on OS X, Sebastian Hagedorn, 2001/06/19
- Re: Config.status on OS X, Akim Demaille, 2001/06/19
- Re: Config.status on OS X, Sebastian Hagedorn, 2001/06/20
- Re: Config.status on OS X, Werner Koch, 2001/06/20
- Re: Config.status on OS X, Akim Demaille, 2001/06/20
- Re: Config.status on OS X, Werner Koch, 2001/06/20
- Re: Config.status on OS X, Akim Demaille, 2001/06/20
- Re: Config.status on OS X, Paul Eggert, 2001/06/20
- Re: Config.status on OS X, Sebastian Hagedorn, 2001/06/20