Try running "which ls" and "which mkdir" in a terminal window to see where these two are located.
On Wednesday, December 3, 2003, at 08:57 AM, [EMAIL PROTECTED] wrote:
Martin:
Thanks for the thoughts and comments. Let me rephrase my question in a way
that, I hope, will be of benefit not just to myself, but to other readers: Is there a
general approach to solving segmentation fault issues?
Regarding "fink reinstall gettext"... no luck with that, either, as you can see:
The following package will be reinstalled:
gettext
/bin/mkdir -p /sw/src/gettext-0.10.40-17
gzip -dc /sw/src/gettext-0.10.40.tar.gz | /sw/bin/tar -xf -
patch -p1 </sw/fink/dists/unstable/main/finkinfo/base/gettext.patch
patching file configure
patching file ltmain.sh
./configure --prefix=/sw --infodir=/sw/share/info --mandir=/sw/share/man --with-included-gettext
creating cache ./config.cache
checking for a BSD compatible install... /sw/bin/install -c
checking whether build environment is sane... configure: error: ls -t appears to fail.� Make sure there is not a broken
alias in your environment
configure: error: newly created file is older than distributed files!
Check your system clock
### execution of ./configure failed, exit code 1
In a message dated 12/3/03 8:05:15 AM, [EMAIL PROTECTED] writes:
On 3 d�c. 2003, at 07:35, [EMAIL PROTECTED] wrote:
[]
> ./install.sh: line 36:�� 702 Segmentation fault����� mkdir -p
> "$basepath"
> ### execution of ./install.sh failed, exit code 139
> Failed: installing fink-0.17.1-1 failed
[]
> I am looking here for a general solution, rather than one which would
> involve special actions for each "problem" module. Can anyone offer
> thoughts or suggestions?
>
Indeed, a general solution to make all segmentation faults disappear
would be wunderful. Unfortunately, this is a dream. Each of these
errors has to be dealt with individually. In your case, this looks very
much like a problem with your specific system. If a basic command like
mkdir gives a segmentation fault, something very low level in your
system has to be wrong.
This can be, for example, an unusual shell instead of the standard one
for /bin/sh, or a mkdir binary that takes precedence over the one in
the system and doesn't work correctly, or some kernel extension
installed with a third-party application, an antivirus program, etc.
You might want to try "fink reinstall gettext", too.
--
Martin
