Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

use Perl Log In

Log In

[ Create a new account ]

Matts (1087)

Matts
  (email not shown publicly)

I work for MessageLabs [messagelabs.com] in Toronto, ON, Canada. I write spam filters, MTA software, high performance network software, string matching algorithms, and other cool stuff mostly in Perl and C.

Journal of Matts (1087)

Sunday June 27, 2004
05:25 AM

Automake suite

[ #19529 ]

I've been working quite a bit with a C library recently. The original version of this library uses automake (i.e. the "./configure" stuff you see on all unix tools these days). Automake is the equivalent of ExtUtils;:MakeMaker for C tools.

Unfortunately automake is a big blob of scripting tools thrown together with a mix of shell scripts, m4 macros, perl code, and makefiles. It's really hard to debug.

The problem I'm facing now is that the library fails to work on Mac OS X. The reason appears to be that the .la file (that tells the library loader which files to look for - usually .so files) points to libfoo.so, but no .so file gets created. Add to that the library extension on OS X is .dylib (which also doesn't get created) and I'm in a world of pain.

Luckily there's someone at work who knows how all this stuff hangs together. But without him I'd be utterly lost.

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • > Unfortunately automake is a big blob of scripting tools thrown together with a mix of shell scripts, m4 macros, perl code, and makefiles. It's really hard to debug.

    automake and its brethren are a horror of Lovecraftian proportions. Ia! Ia! Ia!