Open ivan-w opened 7 years ago
wrljet
commented
7 years ago Related:
autoconf/missing --version will show version 0.3 (if I remember correctly) which is very old.
The one from the current package is much newer: /usr/share/automake-1.14/missing --version
autogen will complain about the above (indirectly through 1Stop in my case).
Locally I fixed that by copying from /usr/share/automake-1.14/missing to autoconf/missing
-Bill
ivan-w
commented
7 years ago Unrelated...
But worth considering ;)
--Ivan
On 2/22/2017 6:57 PM, Bill Lewis wrote:
Related:
autoconf/missing --version will show version 0.3 (if I remember correctly) which is very old.
The one from the current package is much newer: /usr/share/automake-1.14/missing --version
autogen will complain about the above (indirectly through 1Stop in my case).
Locally I fixed that by copying from /usr/share/automake-1.14/missing to autoconf/missing
-Bill
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/hercules-390/hyperion/issues/198#issuecomment-281748928, or mute the thread https://github.com/notifications/unsubscribe-auth/ABjMW50v2IJHaV2C9A5jTSbhYAEtIfv6ks5rfHcCgaJpZM4MI-Q-.
mhoes
commented
7 years ago Related:
autoconf/missing --version will show version 0.3 (if I remember correctly) which is very old.
The one from the current package is much newer: /usr/share/automake-1.14/missing --version
autogen will complain about the above (indirectly through 1Stop in my case).
Locally I fixed that by copying from /usr/share/automake-1.14/missing to autoconf/missing
-Bill
While on this subject, this can also be resolved by doing this:
$ aclocal && libtoolize --force && autoreconf --force --install
In the Hyperion source directory.
However, last time I checked, this also requires the following changes (beforehand) in order for it to work (completely):
$ diff ./Makefile.am.org ./Makefile.am.new
8,10c8
< ACLOCAL_AMFLAGS = \
< -I autoconf \
< -I m4
---
> ACLOCAL_AMFLAGS = -I autoconf -I m4
1047c1045
< $(top_srcdir)/tests/runtest -p .libs -d $(top_srcdir)/tests
---
> $(top_srcdir)/tests/runtest -p ./crypto/.libs -d $(top_srcdir)/tests
$ diff ./tests/runtest.org ./tests/runtest.new
200c200,201
< modpath=.libs
---
> # modpath=.libs
> modpath=./crypto/.libs
When issuing autogen.sh I receive the follwing message : sh ./autogen.sh This script runs four utilities that the developers cannot be bothered to run for you. It finishes with instructions on how to configure Hyperion manually.
aclocal... autoheader... automake... autoconf...
Automuck processing comple.
You are in the "source" directory presently.
You need to
Create a "build" directory where object modules &c are stored. The default build directory is '../s390x/hyperion' in your present set-up, but you can use any name that is a nephew of the source directory; that is, one to the left and down one.
Change directory to the build directory.
Run configure in the source directory: ../../hyperion/configure
Run make in the build directory.
You can use the script "1Stop" to create all prequisites and do all of above list, including running this procedure.
1Stop accepts parameters for Hyperion configure.
1) : This script runs four utilities that the developers cannot be bothered to run for you. It finishes with instructions on how to configure Hyperion manually. May I enquire as to the meaning of this ?
1.1) Automuck processing comple. There is no requirement to disparage the autoconf/automake chain here. It doesn't help. What does "comple" mean ? 2) :
I understand a tool that helps integrating SoftFloat3a - But This is NOT helping !
However a tool to help integrate SoftFloat3a without all the bagage would be fine
But this looks like a script written by someone who has had one too many.