This appears to be the part showing the issue, way down in that full CPAN build output. Rather weird, though...

configure: creating ./config.status
config.status: creating Makefile
rm: cannot remove `Makefile': Is a directory
config.status: creating spamc.h
rm: cannot remove `spamc.h': Is a directory
config.status: creating config.h
rm: cannot remove `config.h': Is a directory
make -f spamc/Makefile spamc/spamc
make[1]: Entering directory `/home/CPAN-ishtar-build-cache/build/
 Mail-SpamAssassin-3.3.2-UN08UX'
make[1]: *** spamc/Makefile: Is a directory.  Stop.

I included the entire output, so you could see that it just failed in a weird way -- and be able to check or verify if there was anything prior to that that looked output of place.

Giving you the last few lines 'context free', you might have wondered if there'd been any strange messages before that.

Oh, some additional comments/thoughts.

I'll start by saying I don't know why this happens, but I've seen the 
symptom before, and seen others complain of it -- it isn't spamassassin specific, but I've seen at least one or two configure scripts with code added by the developer to check for this 'bug'[?]  

I don't know if it is because of some difference in expected versions.  It used to happen to me alot, but haven't encountered on any 3rd party product builds
for a few years now, so I thought it had been fixed. 

I don't know exactly how configure works, but is there something 'from' the "configure" package that you include in the build of squid?

If so, it could be that that 'blob', is from an older version of configure that
had the problem on 'some systems' (don't know what triggers the problem, but it used to be triggered alot on my systems -- a few years ago, then went away), but whatever, - maybe that 'blob' is from the buggy version of config?  (I'm shooting in the dark, you understand --- trying to be helpful! ;-)).

The symptom of the bug -- and I just checked the cpan build dir for this, is that it is targeting file 'X', but for some reason, X is in X/out -- i.e.
instead of Makefile, I'll find the real makefile in Makefile/out.

Sometimes it is possible to fix by hand if it is only 1 configure and 1 makefile, but for ones with multiple makefiles and subdirs, it can get hairy to fix by hand.  

Hope that helps....if there's anything else I tell you to enable you to fix it, let me know!...

(In reply to comment #2)

Linda, I didn't complain about you providing the full output. :)  I just copied the relevant bit into a comment, where it is much more convenient for others to read -- and searchable in bugzilla.

ah, no prob, been submitting so many bugs in different products lately, and most of the places I submit them, they want to complain about *something*....

I first tried to past the bug text into the report, but it said it was too large...  eh!  whatever

Meant this to be a 3.4.0 blocker

FYI, Cpan has rc6 uploaded as a DEVELOPER release

http://search.cpan.org/~kmcgrail/Mail-SpamAssassin-3.4.0-rc6-TRIAL/

Please test and let us know if this is resolved.

Considering resolved.

(In reply to Kevin A. McGrail from comment #7)
> FYI, Cpan has rc6 uploaded as a DEVELOPER release
> 
> http://search.cpan.org/~kmcgrail/Mail-SpamAssassin-3.4.0-rc6-TRIAL/
> 
> Please test and let us know if this is resolved.

---------
11.4 stopped being supported over a year ago, so I doubt anyone would
have such a machine around to test this on.