[Mimedefang] Upgrading 2.51 -> 2.56 embperl.c problem

[Matt Smith]

Hi all,

I'm currently running Mimedefang v2.51 on a Red Hat 9 system, with Perl
v5.8.0 without issue.

Today, I decided it was time to upgrade MD to the latest version, as it's
been a while between drinks.
The process so far involved upgrading MIME::Tools from 5.415 to 5.420 which
went well (with the exception of the Entity test 5 failure!), and to upgrade
IO::Stringy from 1.212 to 2.110 from CPAN.  After the upgrades of these
modules, the current MD version restarted and worked without a problem.

Now, when I went to make the new MD, i received the below message:
<snip>
gcc -g -O2 -Wall -Wstrict-prototypes  -D_REENTRANT -D_GNU_SOURCE -DTHREADS_H
AVE_PIDS -DDEBUGGING -fno-strict-aliasing -I/usr/local/include -D_LARGEFILE_
SOURCE -D_FILE_OFFSET_BITS=64 -I/usr/include/gdbm  -I/usr/lib/perl5/5.8.0/i3
86-linux-thread-multi/CORE  -pthread -D_POSIX_PTHREAD_SEMANTICS -DEMBED_PERL
 -DSAFE_EMBED_PERL -DPERL_PATH=\"/usr/bin/perl\" -DMIMEDEFANG_PL=\"/usr/loca
l/bin/mimedefang.pl\" -DRM=\"/bin/rm\" -DVERSION=\"2.56\" -DSPOOLDIR=\"/var/
spool/MIMEDefang\" -DQDIR=\"/var/spool/MD-Quarantine\" -DCONFDIR=\"/etc/mail
\"  -c -o embperl.o embperl.c
embperl.c:21: warning: function declaration isn't a prototype

<...snip>

The config.log shows the below, which to me seems to indicate that it's
detecting the ability to embed Perl OK.:
<snip>
configure:3796: checking if we can embed a Perl interpreter in C
configure:3832: gcc -o
conftest  -D_REENTRANT -D_GNU_SOURCE -DTHREADS_HAVE_PIDS -DDEBUGGING -fno-st
rict-aliasing -I/usr/local/includ
e -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -I/usr/include/gdbm  -I/usr/lib
/perl5/5.8.0/i386-linux-thread-multi/CORE  -g -O2  -rdyn
amic -Wl,-rpath,/usr/lib/perl5/5.8.0/i386-linux-thread-multi/CORE  -L/usr/lo
cal/lib /usr/lib/perl5/5.8.0/i386-linux-thread-multi/aut
o/DynaLoader/DynaLoader.a -L/usr/lib/perl5/5.8.0/i386-linux-thread-multi/COR
E -lperl -lnsl -ldl -lm -lpthread -lc -lcrypt -lutil  co
nftest.c -lperl  >&5
configure:3835: $? = 0
configure:3837: ./conftest
configure:3840: $? = 0
configure:3856: result: yes
configure:3872: checking if it is safe to destroy and recreate a Perl
interpreter
configure:3935: gcc -o
conftest  -D_REENTRANT -D_GNU_SOURCE -DTHREADS_HAVE_PIDS -DDEBUGGING -fno-st
rict-aliasing -I/usr/local/includ
e -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -I/usr/include/gdbm  -I/usr/lib
/perl5/5.8.0/i386-linux-thread-multi/CORE  -g -O2  -rdyn
amic -Wl,-rpath,/usr/lib/perl5/5.8.0/i386-linux-thread-multi/CORE  -L/usr/lo
cal/lib /usr/lib/perl5/5.8.0/i386-linux-thread-multi/aut
o/DynaLoader/DynaLoader.a -L/usr/lib/perl5/5.8.0/i386-linux-thread-multi/COR
E -lperl -lnsl -ldl -lm -lpthread -lc -lcrypt -lutil  co
nftest.c -lperl  >&5
configure:3938: $? = 0
configure:3940: ./conftest
configure:3943: $? = 0
configure:3959: result: yes
<...snip>


The current MD version is using embedded perl, and a diff between the
embperl.c file from source of that version, and this one shows no
difference.

I've checked about as much as my brain will let me for now, so am requesting
any enlightenment from the wonderful MD community!

Cheers,
Matt