#974 rpmbuild fails when specifying -with perl_modules
When trying to build an rpm package on RedHat 8.0
using the option -with perl_modules results in an error
during the "make" part:
Config summary:
-------------------------------------------------------
--
Net-SNMP configuration summary:
-------------------------------------------------------
--
Net-SNMP Version: 5.1
Building for: linux
Network transport support: Callback Unix TCP UDP
SNMPv3 Security Modules: usm
Agent MIB code: mibII ucd_snmp snmpv3mibs
notification target agent_mibs agentx agent_mibs
utilities host disman/event-mib smux
SNMP Perl modules: enabled
Embedded perl support: disabled
Authentication support: MD5 SHA1
Encryption support: DES
-------------------------------------------------------
--
if test "x/usr/bin/perl" != "x" ; then \
/usr/bin/perl -p -e 's%^#!.*/perl.*%#!/usr/bin/perl%;
s#/usr/local/share#/usr/share#g;
s#/usr/local/etc/snmp##g' ./traptoemail >
traptoemail.made; \
else \
touch traptoemail.made; \
fi
make[1]: Leaving directory `/usr/src/redhat/BUILD/net-
snmp-5.1/local'
making all in /usr/src/redhat/BUILD/net-snmp-5.1/mibs
make[1]: Entering directory `/usr/src/redhat/BUILD/net-
snmp-5.1/mibs'
make[1]: Leaving directory `/usr/src/redhat/BUILD/net-
snmp-5.1/mibs'
making all in /usr/src/redhat/BUILD/net-snmp-5.1/local
make[1]: Entering directory `/usr/src/redhat/BUILD/net-
snmp-5.1/local'
make[1]: Leaving directory `/usr/src/redhat/BUILD/net-
snmp-5.1/local'
chmod a+x net-snmp-config
touch net-snmp-config-x
/bin/sh: -c: line 1: unexpected EOF while looking for
matching `''
/bin/sh: -c: line 2: syntax error: unexpected end of file
make: *** [perlmakefiles] Error 2
error: Bad exit status from /var/tmp/rpm-tmp.44354 (%
build)
Logged In: YES
user_id=88893
Sorry for the delay in following up on this.
I've just tried configuring the current code tree to
include the Perl modules (non-embedded) and
everything compiled fine.
Can you please try with the latest release code,
and see if the problem still occurs.
Logged In: YES
user_id=88893
The submitter of this bug has failed to respond to questions from
the maintainers about it, so this bug has been marked as closed
due to lack of a response within a reasonable period of time.