On 9/20/07, Mark Ventimiglia <[EMAIL PROTECTED]> wrote: > I then grabbed the entire blib directory that I built and moved it to > my web server. It fails with the following
So, then I transplanted Larry's brain into the chipmunk.... No, that never works. You can't simply move compiled libraries between machines and expect them to work, unless the two machines are sufficiently identical. The right answer is to compile everything on the target machine. > The Perl script dies at line 12, which is the "use GD;" line. If I comment > this out, > the script runs fine. Really? How odd. Your script doesn't need GD? > however, the script died with a 500 error, and I get a "Premature end > of script headers" in the error log. It's dying even before your "fatalsToBrowser" could kick in. Try checking it from the command line or look in the server's error logs to find out its dying words. > The obvious answer would be to build this library on the web server > machine, but I don't have access to do that. I need to build the > library on a different machine and copy it over there. Can anyone give > me any hints as to how I can do that? The easiest way is probably to buy a pizza for the administrator of the web server. While the admin is distracted by the free pizza, you casually mention that you need to build some software. The admin builds software on that box all the time, and will probably offer to help you out. If that doesn't work, try again, but buy pizza _and_ beer. If you must build on another machine, it's got to be nearly identical. If you go that route, while the admin is distracted by the free pizza and beer, you casually ask for the complete specs of the machine, including what's installed where. (Borrow the backup tapes, if you can. If that doesn't work, try again, but bring more beer.) Get yourself an identical machine, build on that, copy to the server, and pray that it works. If it doesn't work, make the two machines a little more identical and try again. Repeat as needed, praying a little harder each time. In the end, if you can't build software on the machine on which you need to use software, your problem is not technical but bureaucratic. You'll spend ten times as much of your time, energy, and company's resources trying to get the job done. (And for what benefit?) If the people in charge are oblivious to this, you're working for Dilbert's Pointy-Haired Boss, and it's time to get out. Or, if you chose the web hosting company, it's time to choose one that better fits your needs. Hope this helps! --Tom Phoenix Stonehenge Perl Training -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] http://learn.perl.org/
