Autogen hangs on Ubuntu 13.10 about somoclu

[peterwittek]

This is really odd, especially since I tried it in Ubuntu and it worked.

There are no Makefile.am files, because automake cannot use two different compilers, which is exactly what we need if we compile the code with CUDA support. In general, this should not cause a problem.

As an interim solution, could you try the version on MLOSS?

http://mloss.org/revision/download/1485/

This has the configure script already generated, so you do not need autotools at all.

Bear in mind that version 1.2 on MLOSS has some serious bugs, and a new version will be released next week.

On Fri, 28 Mar 2014 08:04:17 -0700
Bernardo Simoes [email protected] wrote:

Hi,
After running ./autogen.sh, it hangs with the following errors:

configure.ac: error: no proper invocation of AM_INIT_AUTOMAKE was found.
configure.ac: You should verify that configure.ac invokes AM_INIT_AUTOMAKE,
configure.ac: that aclocal.m4 is present in the top-level directory,
configure.ac: and that aclocal.m4 was recently regenerated (using aclocal)
automake: error: no 'Makefile.am' found for any configure output

Doing a little bit of research I found that AM_INIT_AUTOMAKE, is a flag that sets automake to output some warnings: http://www.gnu.org/software/automake/manual/automake.html#Hello-World
Setting it to:

AM_INIT_AUTOMAKE([-Wall -Werror foreign])

Solves the first error.

Now, the second error persists... I dont have lot skills on the c, c++ area... Any ideas how to solve this?
The automake version on the system is 1.13.3

---

Reply to this email directly or view it on GitHub:
#2

[xgdgsc]

I also have 13.10 with the same automake version. I just cloned the repo freshly and ran the ./autogen.sh without any error. Please make sure you have all files and folders under the root directory.

[bernardo-cs]

@xgdgsc and @peterwittek I've just solved the error... After your input, just presumed the problem should definitely be on my part.. So got out of zsh and used bash instead.. Everything is working 💃

Any idea why this might have happened though?

[peterwittek]

This is a shot in the dark, but I suspect a misbehaving environment variable. Which one, I have no idea.