Page 1 of 1

Compiling 6.11.2

Posted: Mon Nov 21, 2011 5:50 pm
by aromero
After configure in my computer, I did just use the make to go through the compilation process but
after that and only few lines I am getting


make all-recursive
Making all in fallbacks
make fox
The build of fox has been disabled
touch: stamps/fox-install-stamp: No such file or directory
make[3]: *** [fox] Error 1

Is there any problem with the new build system in 6.11.2?

Thanks a lot!

Re: Compiling 6.11.2

Posted: Tue Nov 22, 2011 1:05 pm
by pouillon
There have been substantial build-system changes in 6.11.1. Although I've carefully checked my developments and they have been submitted to the test farm in my branch and the trunk, it is probable that some bugs are still there.

Could you give me more info on your configuration (architecture, compilers with versions, configure options, whether you use a builddir, config.log, ...)?

Could you also tell me whether the stamps/ subdirectory has been created in fallbacks/?

Re: Compiling 6.11.2

Posted: Tue Nov 22, 2011 2:16 pm
by aromero
Dear Yann

I am including here the config.log. I am compiling it in my mac ox 10.6.8, where I have been using Abinit for development for the
last few years. I have not changed anything in my configuration in the last few months and all previous Abinit versions did pass
the compilation, I was using gfortran..

Within the fallbacks I have

-rw-r--r-- 1 aldoromero staff 37310 Nov 21 10:45 Makefile
-rw-r--r-- 1 aldoromero staff 26525 Nov 21 10:45 config.log
-rwxr-xr-x 1 aldoromero staff 37117 Nov 21 10:45 config.status
-rw-r--r-- 1 aldoromero staff 4699 Nov 21 10:45 config.mk
-rw-r--r-- 1 aldoromero staff 43320 Nov 21 10:38 Makefile.in
drwxr-xr-x 7 aldoromero staff 238 Nov 21 10:38 autom4te.cache
-rwxr-xr-x 1 aldoromero staff 256619 Nov 21 10:38 configure
-rw-r--r-- 1 aldoromero staff 34768 Nov 21 10:38 aclocal.m4
-rw-r--r-- 1 aldoromero staff 18220 Nov 21 10:38 Makefile.am
drwxr-xr-x 12 aldoromero staff 408 Nov 21 10:25 patches
drwxr-xr-x 3 aldoromero staff 102 Nov 21 10:25 transient
-rw-r--r-- 1 aldoromero staff 0 Nov 21 10:24 AUTHORS
-rw-r--r-- 1 aldoromero staff 35147 Nov 21 10:24 COPYING
-rw-r--r-- 1 aldoromero staff 0 Nov 21 10:24 ChangeLog
-rw-r--r-- 1 aldoromero staff 15578 Nov 21 10:24 INSTALL
-rw-r--r-- 1 aldoromero staff 0 Nov 21 10:24 NEWS
-rw-r--r-- 1 aldoromero staff 0 Nov 21 10:24 README
-rwxr-xr-x 1 aldoromero staff 1633 Nov 21 10:24 autogen.sh
-rw-r--r-- 1 aldoromero staff 5288 Nov 21 10:24 config.mk.in
-rw-r--r-- 1 aldoromero staff 6301 Nov 21 10:24 configure.ac
-rwxr-xr-x 1 aldoromero staff 1482 Nov 21 10:24 wipeout.sh
drwxr-xr-x 7 aldoromero staff 238 Nov 21 10:24 config


No directory as the one you are referring to exist..


Thanks

Re: Compiling 6.11.2

Posted: Tue Nov 29, 2011 3:56 pm
by aromero
I did download the recent merge version of 6.11.2 and still I am unable to compile. I did create the stamps directory within the fallbacks but that did not help. When
I did so, I got the error


make all-recursive
Making all in fallbacks
make fox
The build of fox has been disabled
Checking build of fox fallback
test -e stamps/fox-install-stamp
make libxc
The build of libxc has been disabled
Checking build of libxc fallback
test -e stamps/libxc-install-stamp
make linalg
The build of linalg has been disabled
Checking build of linalg fallback
test -e stamps/linalg-install-stamp
make netcdf
cd sources && \
gzip -cd /Users/aldoromero/.abinit/tarballs/netcdf-4.1.1.tar.gz | tar xf -
/bin/sh: line 0: cd: sources: No such file or directory
make[3]: *** [stamps/netcdf-unfold-stamp] Error 1
make[2]: [all-local] Error 2 (ignored)
Checking build of netcdf fallback
test -e stamps/netcdf-install-stamp
make[2]: *** [all-local] Error 1
make[1]: *** [all-recursive] Error 1
make: *** [all] Error 2


Without creating the stamps directory, I am getting the same error than before.
Any ideas Yann?

Thanks in advance!

Re: Compiling 6.11.2

Posted: Tue Nov 29, 2011 4:34 pm
by pouillon
Let's concentrate on the fallbacks. You can go to the fallbacks/ subdir of Abinit and create a tmp/ build dir there. Just copy the config.mk file from ~abinit/your_builddir/fallbacks/ and run ../configure.

If the sources/, exports/, and stamps/ subdirs do not exist, retry with ../configure MKDIR_P="gmkdir -p" or something similar.

If they stil don't exist, create them manually in ~abinit/your_builddir/fallbacks/.

Please report what happens in any case, so that I know what I have to update / check in the fallbacks build system.

Re: Compiling 6.11.2

Posted: Tue Nov 29, 2011 6:34 pm
by aromero
Yann.

I did the makedist first, after I did create the tmp in the fallbacks directory, copy the config.mk from the fallbacks directory into this directory, then, I did
run configure (the three subdirectories you were talking about were created) and I did try to compile but it stops in the usual place for the xc that I have been
having problems always in my mac.

I did also use ../configure with_dft_flavor=none or
../configure with_dft_flavor=atompaw+wannier90

but in all cases, it stop by complaining a problem with the libxc.

It seems to me that it is not choosing any flavor then..

thanks again

Re: Compiling 6.11.2

Posted: Wed Nov 30, 2011 11:48 am
by pouillon
Then, the only thing I can think of is a misconfiguration in your development environment. But without physical access to the computer, it will be very difficult for me to pinpoint the issue.

Could you copy - including both STDOUT and STDERR (2>&1) - the contents of:
  • your config file;
  • the output of makemake (freshly run after a clean-source-tree);
  • the output of Abinit's configure (*not* the config.log);
in code blocks, so that I get a chance to grasp a hint about what's happening to you?

Re: Compiling 6.11.2

Posted: Wed Nov 30, 2011 2:26 pm
by aromero
Dear Yann

after
config/scripts/clean-source-tree

I did issue the makemake and the configure. I am including here both outputs (the screen outputs)

Thanks a lot

Re: Compiling 6.11.2  [SOLVED]

Posted: Wed Nov 30, 2011 3:37 pm
by pouillon
Sorry, I misunderstood your previous answer. After re-reading it, it seems that the problem is not in the build system at all. I could not identify any anomaly in the data you sent me. In any case, there are MacOS X computers in the test farm which are all fine with the current build system, and some developers use such computers as well, apparently without any problem.

Again, I'm pretty sure that the problem is coming from a misconfiguration of your computer, but I cannot tell you more without physically accessing the computer itself. In particular if you say that this is a recurrent problem that you've been having with several versions of Abinit. As long as you've not identified precisely what it is really about and its origin, there will be no solution. And in the present case, I'll be able to help only when the problem has been fully formulated.