[hercules-390] Build from source

[[e-mail] [hercules-390]]

I am attempting to build Hercules Hyperion, latest from github, from source.


I am running in the following environment.



Linux version 3.10.0-327.36.2.el7.x86_64 (***@x86-034.build.eng.bos.redhat.com) (gcc version 4.8.5 20150623 (Red Hat 4.8.5-4) (GCC) ) #1 SMP Tue Sep 27 16:01:21 EDT 2016


I've run ./util/bldlvlck and get the following


[***@phoenix hyperion-master]# ./util/bldlvlck
This utility will check the level of various utilities needed to build
hercules. Checking is done against versions that are KNOWN to work.
This doesn't mean a build will NOT succeed with older versions
of the utilities, but will give a hint as to what package may need
an upgrade if the build ever fails with some odd reason.




OK autoconf requires 2.64, found 2.69


OK automake requires 1.9, found 1.13.4


OK flex requires 2.5, found 2.5.37


OK gawk requires 3.0, found 4.0.2


OK gcc requires 3, found 4.8.5


OK grep requires 1, found 2.20


OK m4 requires 1.4.6, found 1.4.16


OK make requires 3.79, found 3.82


OK perl requires 5.6, found 5.16.3



OK sed requires 3.02, found 4.2.2


Next, I ran sh ./autogen.sh


[***@phoenix hyperion-master]# sh ./autogen.sh
Note: if you do not see a 'All processing successfully completed.'
message when this script completes, then something went wrong and
you should examine the output to try and determine what it was that
went wrong.


aclocal... OK. (25% done)
autoheader... OK. (50% done)
automake... OK. (75% done)
autoconf... OK. (100% done)


All processing successfully completed.


You may now run ./configure in order to create a custom Makefile
that is suitable for your platform and environment.


And finally ./config which fails, any help or suggestions?



[***@phoenix hyperion-master]# ./configure

checking for a BSD-compatible install... /bin/install -c
checking whether build environment is sane... yes
/home/ibmsys1/hyperion-master/autoconf/missing: Unknown `--is-lightweight' option
Try `/home/ibmsys1/hyperion-master/autoconf/missing --help' for more information
configure: WARNING: 'missing' script is too old or missing
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking whether make supports nested variables... (cached) yes
checking whether to enable maintainer-specific portions of Makefiles... no
checking build system type... x86_64-unknown-linux-gnu
checking host system type... x86_64-unknown-linux-gnu
checking target system type... x86_64-unknown-linux-gnu
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking for style of include used by make... GNU
checking dependency style of gcc... gcc3
configure: Detected GCC equivalent level for gcc : 4.8.5
checking if this is GCC with broken '-O3' option... no
checking for a sed that does not truncate output... /bin/sed
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for ld used by gcc... /bin/ld
checking if the linker (/bin/ld) is GNU ld... yes
checking for /bin/ld option to reload object files... -r
checking for BSD-compatible nm... /bin/nm -B
checking whether ln -s works... yes
checking how to recognise dependent libraries... pass_all
checking how to run the C preprocessor... gcc -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking dlfcn.h usability... yes
checking dlfcn.h presence... yes
checking for dlfcn.h... yes
checking for g++... no
checking for c++... no
checking for gpp... no
checking for aCC... no
checking for CC... no
checking for cxx... no
checking for cc++... no
checking for cl.exe... no
checking for FCC... no
checking for KCC... no
checking for RCC... no
checking for xlC_r... no
checking for xlC... no
checking whether we are using the GNU C++ compiler... no
checking whether g++ accepts -g... no
checking dependency style of g++... none
checking how to run the C++ preprocessor... /lib/cpp
configure: error: in `/home/ibmsys1/hyperion-master':
configure: error: C++ preprocessor "/lib/cpp" fails sanity check
See `config.log' for more details

[[e-mail] [hercules-390]]

Post by ***@netscape.com [hercules-390]
configure: error: C++ preprocessor "/lib/cpp" fails sanity check
See `config.log' for more details

it happens usually when somebody forgets to install c++
is it a new Linux installation ?

[[e-mail] [hercules-390]]

yes

[[e-mail] [hercules-390]]

Wow, installed it and now it works. I would have thought the ./util/bldlvlck would have pointed that out.

[Ivan Warren [e-mail] [hercules-390]]

Post by ***@netscape.com [hercules-390]
Wow, installed it and now it works. I would have thought the
./util/bldlvlck
would have pointed that out.

True...

But this a 10+ year old issue. There is actually no C++ (it is C only)
code in hercules, but there are some external build component that
thinks (most probably autolib) it needs a C++ compiler.

./util/bldlvlck is a very "rough" script that checks for most obvious
options, but some things cannot be caught (for example bldlvlck assumes
gcc even if you are using clang/llvm) because it is very dependent on
your build environment.

So if you are using gcc, just install g++ for your distro, and you
should be good.

--Ivan


[Non-text portions of this message have been removed]

[[e-mail] [hercules-390]]

Ivan, I normally don't install from source, so I'm not too familiar with the process. Again, thanks for the info.