Re: Please help find dependency

> > What kind of issues are likely?
> > 
> 
> pls check the -dev list (link on the site/wiki as well as the sf.net
> standard pages).
> On x86_64 you might want to give GerH version a try - look in ML or
> on the wiki/coolthings for URL to Ger Hobbelt's site.

Got it from the mailing list archives, thanks. I'm trying "BlameJason".
It compiles without any obviously significant errors. Make offers
megatest, but that's clearly not available. (Meaning that I tried it
and, after it failed, I noticed that megatest.sh did not exist.) When I
dummy it up, it hangs on the "Bit-Entropy Toroid classifier", which is
probably why megatest wasn't in the original tarball.

> > So I've got a good little test bed - 900 inbound
> > mails a day until things pick up at the end of summer, and nobody
> > loses money if it goes down. 
> 
> a machine hooked to the 'net most of the time, might become source of
> money for some and of troubles for others, if it's taken via
> injection of malicious code. Such machines are aka 'zombies'.
> Path to such successful injection is usually a buggy user
> (behaviour), buggy code (esp. in critical data path), or both.

Right. Crashing the machine is acceptable. Hanging out the "Welcome"
sign for 733t $p33k1n' krackerz isn't. 

> > I also got lucky and found an RPM for the static TRE
> 
> btw, unless you know you want a static build, for normal install you
> may want to change the Makefile flags for the usual shared
> build/install.

The makefile included in "Newest Slightly Unstable Mainline" asked for
the --enable-static flag to be set on the TRE build. I installed both
libraries so configure on GerH's fork should be able to find the one it
wants.

> > development libraries. Mega test failed, "make: *** [megatest] Error
> > 126", but otherwise compile proceeded without any other hitches. 
> 
> pls upload megatest log, eg on http://pastebin.com/ if you don't have 
> your own writeable webspace.

It was just a permissions issue. If I'd noticed the log file, I
wouldn't have even mentioned it.

> We've also a vim/elvis syntax file but somehow it slipped off the
> mailine src. Check it out here
> http://crm114.cvs.sourceforge.net/*checkout*/crm114/people/paolo/wsy/vim_elvis.syn?revision=1.1.2.2
> it's unmaintained afaikt - want to update it? then you might want
> also to check with orig author first, he might have newer version.

Sweet! I just set up a Trac installation this week. If the original
author doesn't have a web space for it, I'll include it in my CRM
projects once I get to that point.

Chris


-------------------------------------------------------------------------
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at http://www.sourceforge.net/community/cca08