On Jan 24, 2008 3:33 PM, Liam <[EMAIL PROTECTED]> wrote: > Tom Phoenix wrote:
> > It looks as if you need to fix the system damage, so that your OS is > > reasonably similar to the configuration that other people have used to > > build perl. Experts on your OS may be able to help, or you may be able > > to re-install the OS itself. > This is not my server, it is a webhosting server, so I have no way of > modifying those settings, or getting them to modify them. There HAS to > be another way. Keep in mind, that I am a subaccount of a webhosting > account, so I don't have that much permission. Your system administrators have that much permission; they would be installing perl for you, if this were a better world. Do you have really no way of asking the admins on your box for technical assistance? The picture I'm getting is of a hosting provider who doesn't supply perl, doesn't supply technical help for users who want perl, and has a botched OS that impedes building perl. Additionally, you don't even have an actual account, but some kind of "subaccount" that's worse off than the ordinary accounts, if that's even possible. Is that picture inaccurate, or are you looking for something better? Having said that, I imagine that if the only problem you're having during the build is that /home isn't world-readable, you can probably hack File::Glob (or whatever it is that's trying to read it) and build a perl that may have slightly reduced functionality (e.g., maybe your File::Glob won't be able to use tilde to refer to a user's home directory). It's not the road I'd choose, in part because I don't think that's going to be the last problem; but it could work for you. Good luck with it! --Tom Phoenix Stonehenge Perl Training -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] http://learn.perl.org/
