patchelf config fails on darwin

[cekees]

[patchelf] automake: thread 0: Sources ending in .test$(EXEEXT) become .log
[patchelf] automake: thread 0: creating tests/Makefile.in
[patchelf] ./configure: line 4: .: filename argument required
[patchelf] .: usage: . filename [arguments]

The autoreconf step is generating a configure script with a line containing only '.' with no filename argument.

[certik]

Seems similar to these problems:

http://lists.gnu.org/archive/html/autoconf/2010-06/msg00007.html
http://hmijailblog.blogspot.com/2011_07_01_archive.html

which are caused by incorrect configure.ac script. In our case the script is just:

https://github.com/NixOS/patchelf/blob/master/configure.ac

So something probably doesn't work on Mac.

The question then is also how to handle packages that are only needed on one platform. @dagss, any ideas?

[cekees]

I think this is sort of the next issue to address as we try to build on new
systems. As soon as we move to the clusters we'll need to stop building
lapack, blas, and mpi. I'm also beginning to wonder if we shouldn't just
build our own gfortran on darwin.

We could branch the stack in git, but I think I would rather keep multiple
packages.yml alongside one another or use an override mechanism.

On Thu, Jun 20, 2013 at 2:32 PM, Ondřej Čertík [email protected]:

Seems similar to these problems:

http://lists.gnu.org/archive/html/autoconf/2010-06/msg00007.html
http://hmijailblog.blogspot.com/2011_07_01_archive.html

which are caused by incorrect configure.ac script. In our case the script
is just:

https://github.com/NixOS/patchelf/blob/master/configure.ac

So something probably doesn't work on Mac.

The question then is also how to handle packages that are only needed on
one platform. @dagss https://github.com/dagss, any ideas?

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/82#issuecomment-19777627
.

[certik]

See #86 for compilers and #87 for Lapack + MPI.

[dagss]

Well, that's more or less what I'm supposed to work on in the remaining 3 DoD weeks. But as I said in that email to Fernando time is tight and I probably can't finish anything before September.

So question is what to do now...

It'd be very easy to have multiple packages.yml, "import" them explicitly from config.yml (add a new import section listing filenames relative to location of config.yml...) and merge them in builder/builder.py. There should basically be one config.yml per platform anyway.

It wouldn't be very difficult to design an override system so that one config.yml could import another one and then override it, either. It's just merging Python dicts and lists the right way. So that you can have your own config-certik.yml that imports and overrides config-linux.yml, say.

@certik, I've fallen way behind again, if there's anything else that needs my attention just drop me a short note and I might get to answer it tonight (but no promises).