So, I had to do a little research on autoconf, but I'm back for more.
I used version 2.58 and recieved the following errors/skippages. I'm assuming a lack of fortran is the reason for the skipped gimmicks, but I am stumped by the rest.
Mr Welliver, thank you for your help in the last email for getting me one step further than I previously was.
## ------------- ## ## Test results. ## (from make check)... ## ------------- ##
ERROR: 172 tests were run, 4 failed unexpectedly.
Executables (autoheader, autoupdate...). 3: autom4te cache FAILED (tools.at:131) 4: autoconf --trace: user macros FAILED (tools.at:180) M4sugar. 13: [m4_warn] FAILED (m4sugar.at:59) 14: [m4_require: circular dependencies] FAILED (m4sugar.at:107)
40: Configuring subdirectories skipped (torture.at:562) 41: Deep Package skipped (torture.at:658) 66: GNU Fortran 77 skipped (fortran.at:33) 67: GNU Fortran skipped (fortran.at:61) Testing autoconf/fortran macros. 68: AC_F77_MAIN skipped (acfortran.at:12) 69: AC_F77_WRAPPERS skipped (acfortran.at:13) 70: AC_FC_MAIN skipped (acfortran.at:14) 71: AC_FC_WRAPPERS skipped (acfortran.at:15) 72: AC_PROG_F77_C_O skipped (acfortran.at:16) 73: AC_PROG_FC_C_O skipped (acfortran.at:17)
Also, autoconf documentation tells me that it should be installing pike to my bin, but it has yet to make it there. I can of course run pike from its home directory...but where's the fun in that?
Hope this email finds all who receive it well.
Linux Mint XFCE 32 bit OS
I’m not sure what is producing the results you sent, however the standard procedure for building and installing Pike goes something like this (once you’ve installed all of the prerequisite libraries and tools):
checkout Pike from git. in the root directory of the checkout (_not_ src):
make make install
The master makefile will take care of running all of the auto tools. If, for some reason, you need to pass arguments to autoconf, you can do this (as an example):
make CONFIGUREARGS=“—help”
Best,
Bill
On Mar 28, 2015, at 1:21 PM, robert papadopoulos rgp100@humboldt.edu wrote:
So, I had to do a little research on autoconf, but I'm back for more.
I used version 2.58 and recieved the following errors/skippages. I'm assuming a lack of fortran is the reason for the skipped gimmicks, but I am stumped by the rest.
Mr Welliver, thank you for your help in the last email for getting me one step further than I previously was.
## ------------- ## ## Test results. ## (from make check)... ## ------------- ##
ERROR: 172 tests were run, 4 failed unexpectedly.
Executables (autoheader, autoupdate...). 3: autom4te cache FAILED (tools.at:131) 4: autoconf --trace: user macros FAILED (tools.at:180) M4sugar. 13: [m4_warn] FAILED (m4sugar.at:59) 14: [m4_require: circular dependencies] FAILED (m4sugar.at:107)
40: Configuring subdirectories skipped (torture.at:562) 41: Deep Package skipped (torture.at:658) 66: GNU Fortran 77 skipped (fortran.at:33) 67: GNU Fortran skipped (fortran.at:61) Testing autoconf/fortran macros. 68: AC_F77_MAIN skipped (acfortran.at:12) 69: AC_F77_WRAPPERS skipped (acfortran.at:13) 70: AC_FC_MAIN skipped (acfortran.at:14) 71: AC_FC_WRAPPERS skipped (acfortran.at:15) 72: AC_PROG_F77_C_O skipped (acfortran.at:16) 73: AC_PROG_FC_C_O skipped (acfortran.at:17)
Also, autoconf documentation tells me that it should be installing pike to my bin, but it has yet to make it there. I can of course run pike from its home directory...but where's the fun in that?
Hope this email finds all who receive it well.
Linux Mint XFCE 32 bit OS
pike-devel@lists.lysator.liu.se
-
H. William Welliver III -
robert papadopoulos