On Oct 30, 2005, at 5:20 PM, John Horner wrote:
I'd love to be able to use the matching Perl module, 6.1.7 -- how
would I do that?
Beats me. You might be able to find a copy in an antiques shop. ;-)
CPAN has precisely two versions, 5.5.7 and 6.2.4. I might be better
off getting the ImageMagick library to match the library rather
than the other way around.
"Better off" is putting it mildly. Matching versions is a requirement
- that's why the library includes a copy of the module.
They're compiler and linker flags. The upper-case letters add to the
include search path (-I) and the library search path (-L). The lower
case -l tells the linker to link against a library.
Could you please, in the spirit of "teach a man to fish", show me
what you would do to those LIB and INC settings in order to have
the Makefile work correctly?
You're focusing on a symptom instead of the cause. The question is
why is Makefile.PL incorrect in the first place - I downloaded a copy
from CPAN and looked. Makefile.PL does *not* contain those @FOO@
placeholder strings you mentioned earlier. Makefile.PL.in *does*
contain them.
My advice - Forget about trying to fix Makefile.PL by hand, and
delete the binary package. I'm sure the author meant well, but it's
turning into more trouble than it's worth. After all, the point of
the package is supposed to be to make your life easier, not more
difficult.
First, use Fink or DarwinPorts to install the graphics libraries you
care about - libjpeg, libgif, libpng, libtiff, whatever. Then go to
the <http://www.imagemagick.org> site, download the latest source
package, unpack and configure it with the following:
./configure CPPFLAGS=-I/sw/include LDFLAGS=-L/sw/lib
If you're using DarwinPorts instead of Fink, use /opt/local instead
of /sw in the above.
Check the output of this command to make sure all went well. In
particular, check the last block of output to make sure you're
getting support for the formats you want. If everything is well,
build and install:
make
sudo make install
This will install the Perl module as part of the process, and since
it's bundled with the library they're guaranteed to match in both
version and configuration. This hassle of obtaining them separately
and getting them to work together is precisely the reason that a copy
of the Perl module is included with the library and built at the same
time.
sherm--
Cocoa programming in Perl: http://camelbones.sourceforge.net
Hire me! My resume: http://www.dot-app.org
