Here's the final fix to this problem -- the trick was that the Makefile
was trying to compile spamc with the same flags that perl itself was
compiled with, which is overkill (particularly the libs stuff). So I've
removed the libs bits. This is checked into CVS now.
--- Makefile.PL 31 Jan 2002 23:46:34 -0000 1.22
+++ Makefile.PL 13 Feb 2002 16:54:31 -0000
@@ -110,7 +110,7 @@
spamd/spamc: spamd/spamc.c
$(CFCC) $(CFCCFLAGS) $(CFOPTIMIZE) spamd/spamc.c \
- -o $@ $(CFLDFLAGS) $(CFLIBS)
+ -o $@
inst_cfs: $(LOCAL_RULES_DIR) $(DEF_RULES_DIR)
$(DEF_RULES_DIR)/user_prefs.template $(LOCAL_RULES_DIR)/local.cf
migrate_cfs
for file in $(RULES) ; do \
On Tue, 2002-02-12 at 23:04, Erik van der Meulen wrote:
> On Tue, Feb 12, 2002 at 15:11:59 -0800, Craig Hughes wrote:
>
> > You can hand edit the Makefile after perl Makefile.PL, but a
> > probably better solution would be to find why MakeMaker on your machine
> > is trying to link libndbm in. Could you add a line to the Makefile.PL
> > in the spamc build rule to just echo all those $(CFCCFLAG) etc paramters
> > in a way where we can tell which one is which? Then we can try to track
> > down which one is inserting the bogus libs.
>
> I am afraid I need instructions a little more elaborate. Sorry about
> that. If I just insert 'echo $(CFCCFLAG)' into the Makefile.PL (tried
> various places) and do 'perl Makefile.pl' and 'make', I get all sorts of
> errors.
>
> Feeling a little dumb here, but RTFM on Perl is out of my reach...
>
> --
> Erik van der Meulen <[EMAIL PROTECTED]>
>
>
_______________________________________________
Spamassassin-talk mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
