The ABINIT Users Mailing List ( CLOSED )

[Anurag Chaudhry <anuragchaudhry@yahoo.co.uk>]

Dear Dr Pouillon, Beuken,

Your suggestions worked.  I tried both of them independently and could compile the code successfully.

Thanks!

Anurag

---

From: Jean-Michel Beuken <jean-michel.beuken@uclouvain.be>
To: forum@abinit.org
Sent: Monday, 22 December, 2008 4:39:45
Subject: Re: [abinit-forum] install error on Mac OS X 10.5.6

Anurag,

you can try with a wrapper...

in your home, create a dir "bin"

cd bin

vi  mkdir   (and put these lines)


#!/bin/bash
if [ "$1" = "--version" ]; then
cat <<EOF
mkdir (GNU coreutils) 6.10
Copyright (C) 2008 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Written by David MacKenzie.
EOF
else
    /bin/mkdir $@
fi

:w


chmod 750 mkdir

export PATH=~/bin:$PATH

and retry ./configure...

good luck and tell me if it's working...  (no tested...)

regards...

jmb

Hello Dr. Beuken,

Thank you for replying to my question.

Unfortunately I do not have root privileges on the system so I cannot install the GNU coreutils.  Has someone "patched" this behavior for Mac OS X ?  

I have seen someone install the same version of ABINIT (5.6.3) on a linux cluster and it just works fine.

 regards,

Anurag

---

From: Jean-Michel Beuken <jean-michel.beuken@uclouvain.be>
To: forum@abinit.org
Sent: Saturday, 20 December, 2008 23:46:58
Subject: Re: [abinit-forum] install error on Mac OS X 10.5.6

Hello Anurag,

I am trying to install ABINIT 5.6.3 on a Intel Mac running OS X 10.5.6.  I have intel fortran 10.1 compilers (+ MKL 10.0) on it.

config/gnu/install-sh -c -d tmp/lib

make[4]: config/gnu/install-sh: Command not found

the problem is because of possible bug of autotools...

the autotools tries to find a GNU "mkdir" command...
the /bin/mkdir for MacOS X 10.5 is not accepted because the test is to restrictif  : only tets : "mkdir --version" rather to test the feature of the /bin/mkdir !   ( the native "mkdir" can  meanwhile make "mkdir -p"... )
then, as the configure doens't found a "good" mkdir command, it uses the "config/gnu/install-sh" but with a "relatif" path !?! (this is the possible bug...)

the workaround is to install  (by fink or MacPort) the coreutils package...

but the "mkdir" installed is named "/opt/local/bin/gmkdir" : then don't forget to make a symbolic link (gmkdir -> mkdir)  and add the /opt/local/bin in your PATH

regards

jmb