Red Hat Bugzilla – Bug 591378
build_apache_snmp.sh fails with cannot run /bin/sh ./config.sub
Last modified: 2010-10-23 11:17:33 EDT
Description of problem:
Unable to build Apache SNMP Connector module from source provided with JON 2.3.1 on Fedora or SuSE Linux system due to an error configure spits out when attempting to execute config.sub in the snmp2.0 directory.
It appears that this is because config.sub and config.guess are missing. I was able to get around this issue by executing automake -a from the snmp2.0 directory to add the missing files.
I have only seen and tested this issue on SuSE Linux Enterprise 11 and Fedora 11.
We should see whether this is an issue on RHEL, if not then I suspect just a doc update should be sufficient here.
RHEL 5.5 needs a bunch of (additional) packages installed
but building the modules for apache 2.0 and 2.2 fails with missing includes ( -I options are not correctly set) and 1.3 fails with some other error.
As we are delivering binary versions, compiling from source is perhaps not that important.
The docs at http://rhq-project.org/display/JOPR2/Apache+2.x+SNMP+Config tell that automake is needed.
Hi to all,
anyone came to a solution?
I'm in a similar situation: Red Hat AS4, apache 2.0.52 and I need to compile because the binaries are linked to GLIBC_2.4 and on my system there is GLIBC_2.3.
Try the workaround mentioned in the description:
> It appears that this is because config.sub and config.guess
> are missing. I was able to get around this issue by executing
> automake -a from the snmp2.0 directory to add the missing
Basically, you will force automake to generate/add the missing files.
I solved following this post from RHQ Project: http://jira.rhq-project.org/browse/RHQ-1979
It was a Solaris environment bug but I tried and it worked.
r10793 adds a switch for Solaris that defaults to the RHEL behaviour
Confirmed that running automake works. After running it, I got:
[root@core-01 snmp2.0]# automake -a
configure.in: no proper invocation of AM_INIT_AUTOMAKE was found.
configure.in: You should verify that configure.in invokes AM_INIT_AUTOMAKE,
configure.in: that aclocal.m4 is present in the top-level directory,
configure.in: and that aclocal.m4 was recently regenerated (using aclocal).
configure.in:32: installing `./config.guess'
configure.in:32: installing `./config.sub'
automake: no `Makefile.am' found for any configure output
And then reattempting the build was successful.
However, per comment #1, do we need to have this documented somewhere?
Marking this verified.
Mass-closure of verified bugs against JON.