Installing GDP++

[Irubataru]

I recently tried installing QDP++ on a Linux machine I work on and encountered a couple of issues on the way. I eventually managed to solve them, but wanted to hear if I am doing something wrong or if the install is broken in its current form. Here is what I did:

First I ran the configure command which resulted in 4 warnings, all along the line:
=== configuring in other_libs/qio ([path])
configure: WARNING: no configuration information is in other_libs/qio

If I the proceed with the make process anyway, this will result in compilation errors as it doesn't find the header files that should be located in these submodules. Also tried running the autogen script, but that didn't help.

So I then tried to pull down the submodules myself with a simple
git submodule update --init --recursive

But got access errors because the submodules was included in the old style of
git@github.com:usqcd-software/qio.git

So I went in and changed them all to the current form
https://github.com/usqcd-software/qio.git

Finally the submodules pulled, I had to run the autogen script again, then it configured and buildt properly.

So my question is simply, am I doing something wrong? I assume it was never meant to be this complicated.

[bjoo]

Hi Jonas,
I believe your issue stems from a couple of recent changes, which may be causing as many issues as they are fixing.
The short story of it, is that we’ve stopped checking in certain ‘derived’ results of the autoconf/automake process
(configure, Makefile.in etc) as they always seem to wreak havoc with versioning and aclocal and things on local systems.

The downside is that now every time you pull a copy, these need to be regenerated.

I suggest cloning with:

git clone —recursive git@github.com:usqcd-software/qdpxx.git

Please note the —recursive option, will pull the main code and the submodules all in a single step.

Once the clone is complete you should regenerate those files, by

cd qdpxx;
autoreconf -i

This works similarly in Chroma by the way, clone and then rebuild the files.
In my own scripts I just include this step automatically.

Hopefully thereafter, you should have no trouble building.
A couple of other tips:

Use a recent compiler like gcc-4.8.2, or g++-4.8.2

Use the —std=c++11 on CXXFLAGS
and —std=gnu99 on CFLAGS

when working with the GNU compiler.

I hope this helps,
Best,
Balint

On Feb 20, 2015, at 5:06 AM, Jonas Rylund Glesaaen notifications@github.com wrote:

I recently tried installing QDP++ on a Linux machine I work on and encountered a couple of issues on the way. I eventually managed to solve them, but wanted to hear if I am doing something wrong or if the install is broken in its current form. Here is what I did:

First I ran the configure command which resulted in 4 warnings, all along the line:
=== configuring in other_libs/qio ([path])
configure: WARNING: no configuration information is in other_libs/qio

If I the proceed with the make process anyway, this will result in compilation errors as it doesn't find the header files that should be located in these submodules. Also tried running the autogen script, but that didn't help.

So I then tried to pull down the submodules myself with a simple
git submodule update --init --recursive

But got access errors because the submodules was included in the old style of
git@github.com:usqcd-software/qio.git

So I went in and changed them all to the current form
https://github.com/usqcd-software/qio.git

Finally the submodules pulled, I had to run the autogen script again, then it configured and buildt properly.

So my question is simply, am I doing something wrong? I assume it was never meant to be this complicated.

—
Reply to this email directly or view it on GitHub.

---

Dr Balint Joo High Performance Computational Scientist
Jefferson Lab
12000 Jefferson Ave, Suite 3, MS 12B2, Room F217,
Newport News, VA 23606, USA
Tel: +1-757-269-5339, Fax: +1-757-269-5427

email: bjoo@jlab.org

[grokqcd]

On Feb 20, 2015, at 8:31 AM, Balint Joo notifications@github.com wrote:

cd qdpxx;
autoreconf -i

Balint,
FYI, in every repo, there is also an autogen.sh script that does autoreconf -f (it’s the -f that’s more important). The “-i” seems to cause more problems, depending on the autoconf version.

    Robert