Open svdhoog opened 7 years ago
Hi svdhoog, I am also a novice user of libmboard. I need to install if for FLAME. I faced the same issue during libmboard configuration. The trick is to make the autogen.sh file executable using "chmod u+x autogen.sh" command.
The error that I used to get was like this: /libmboard-master$ sh ./autogen.sh ./autogen.sh: 12: ./autogen.sh: cannot create autogen.log: Permission denied ./autogen.sh: 14: ./autogen.sh: Syntax error: "(" unexpected
However, after making it executable, it executes well only that there is another error message for README.in not being found!
Now, I need to look for why is this happening! Any help from anybody.
Thanks in advance.
Sandeep
Can you tell us what is the output of: $ sudo sh ./configure
the configure file has not been created by autogen.sh.
I think it has something to do with the error:
configure.ac:23: installing './compile' configure.ac:29: installing './config.guess' configure.ac:29: installing './config.sub' configure.ac:10: installing './install-sh' configure.ac:10: installing './missing' Makefile.am: installing './INSTALL' Makefile.am: installing './COPYING' using GNU General Public License v3 file Makefile.am: Consider adding the COPYING file to the version control system Makefile.am: for your code, to avoid questions about which license your project uses configure.ac:215: error: required file 'README.in' not found src/parallel/Makefile.am: installing './depcomp'
However, if I just create an empty "README.in" file by "touch README.in" everything works perfect. I get an "configure" file which runs fine.
$ sudo ./autogen.sh [sudo] password for sandeep: Running libtoolize ... DONE Running aclocal ... DONE Running autoheader ... DONE Running automake ... DONE Running autoconf ... DONE Overwriting 'COPYING' file ... DONE sandeep@:~/Downloads/libmboard-master$
And, the trailing portion is
Looks good. But I have no idea whether everything is actually fine or not.
Best.
So, In summary, may be the authors/coders should change the README.txt or INSTALL.txt accordingly. Because, after using these two additional commands/steps, the installation is very smooth, without errors. These commands are:
1) chmod u+x autogen.sh 2) touch README.in
Finally, generate the configure file by simply running the 'autogen.sh' with 'sudo'.
1) sudo ./autogen.sh 2) ./configure 3) make 4) sudo make install
And, that is all.
Documents should be updated for this. @hosantosh Apologies for the delay we have had some issues with notifications.
No problem, mondus. But I found that installing FLAME is trickier than other softwares like NetLogo. So, I believe FLAME developers should also try to make the installation as simple as possible and without any glitches whatsoever.
@hosantosh Agreed. We have moved development to a completely open system now so if you have any improved install scripts you can submit these as pull requests. Otherwise we will use issues to track feature requests.
great.. and thanks.
As of 5fd34e8 following the updated instructions in the readme works correctly on Ubuntu 16.04.5
https://github.com/FLAME-HPC/libmboard/blob/master/README.md#installation
./autogen.sh
./configure
make
sudo make install
Given this has been resolved, can the issue be closed?
In fact, I would propose to do a minor version release for libmboard 0.3.2 that includes this fix. We are having similar problems with a FLAME model and using TravisCI, see here: https://github.com/ETACE/eurace_unibi/pull/8
The readme file states that the configuration can be run as follows:
[root@stfc]# ./configure
But on a freshly installed Ubuntu we had to run this to get it working:sudo sh ./configure
Running with bash throws an error, because the configure file needs sh as shell:sudo bash ./configure