Your approach works for pure-Perl modules but just copying a GD.pm won't work here as actually it is a wrapper for a shared library saved under architecture-dependent directory. It will be named GD.so and you will definitely need it as well. But beware: things are not going to be easy, 99% chance GD.so taken from your workstation won't work on the hosting server.
The reason is that «Linux» is a very broad description of what OS does your workstation and hosting server use. You may note that they are quite different (e.g., Perl version), even the architecture may differ. If you are using 32-bit system and they use 64-bit on the server — the reason is obvious, for example.
Another trouble is shared libraries. The set of them on your workstation and hosting server is different, and GD.so linked against your set may not work on the server — some libraries may be missing and some may have incompatible versions. It is (or, to be more precise, I see no reason why it shouldn't be) possible to build GD.so so that it doesn't use any external libraries but the memory footprint of it will be horrible, and also it will need some knowledge of Linux internals to do so. Another option is to obtain a build environment compatible with OS used on hosting server, build GD.so there and use it. However if your hosting server lacks, e.g., libfontconfig.so — you are still in trouble.
So, in short: rather then trying to use a binary module all by yourself just ask hosting guys politely to install the module for you, and if they refuse — look for another hosting provider.
In reply to Re: GD on Mediacraft
by jmacloue
in thread GD on Mediacraft
by jobsworth
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |