Can't locate Graphics/Magick.pm in @INC
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
graphicsmagick (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Hi
I have tried to install GraphicsMagick on a server and it doesn't work.
I did server installation on an older 32bit PC.
The version of Ubuntu is:
$ apt-cache policy graphicsmagick
graphicsmagick:
Installed: 1.3.12-1.1build1
Candidate: 1.3.12-1.1build1
Version table:
*** 1.3.12-1.1build1 0
500 http://
100 /var/lib/
A search for the package found:
$ sudo find / -name Magick.pm
[sudo] password for darren:
darren@alpha:~$ dpkg --get-selections | grep magick
graphicsmagick install
libgraphicsmagick3 install
I tried to compile check the following test script:
#!/usr/bin/perl
# =======
use warnings;
use strict;
use Graphics::Magick;
my $imageFile = "/var/images/
my $logoFile = '/home/
my $logo=Graphics:
$logo-
my $image=
$image-
my $webImage = $image-
$webImage-
$webImage-
undef $imageFile;
undef $logoFile;
undef $webImage;
exit 1;
$ perl -c compositeTest.pl
Can't locate Graphics/Magick.pm in @INC (@INC contains: /etc/perl /usr/local/lib
/perl/5.14.2 /usr/local/
BEGIN failed--compilation aborted at compositeTest.pl line 5.
A search for Magick.pm ($ sudo find / -name Magick.pm ) did not produce the results.
I have seen this bug on 2 servers. On the first I was building/developing the software.
I came across this bug and couldn't find a solution on Google or the Ubuntu forums.
I thought I might have mangled Perl.
I then built a 2nd server starting with a blank HD.
Prior to installing the Magick package, I did apt-get update then upgrade.
I have exactly the same error message on the fresh server installation.
I haven't done anything that might mangle Perl.
In short:
Installing the GraphicsMagick package was not successful.
I expected to be able to interface Perl scripts with the GraphicsMagick API.
I got exactly the same error message on two nearly identical server installations.
For clarification, the GraphicsMagick package installation appeared to be successful.
The first indication of a problem was when I checked the test script.