Thanks for the replies.
nikanh: I installed the new slack9 on a seperate drive, totally new. Then I installed mod_perl 1.26, and let it build apache 1.3.20, then ApacheDBI-0.88, all from source. All compiled with no errors. The gimp was installed by the slackware install. I did nothing to it.
I'm aware that I could move/soft link stuff and get it to work, probably. The idea here is to try to fix a possible error in the Slackware-current tree so everybody else don't have to go through it all, over and over again. Either I did something weird that I'm unaware of, or there is a problem with perl 5.8 and how it reports it's @INC to external apps.
I aggree that it looks like it's using an old perl or something. Don't know why apache and gimp show different stuff in @INC.
If nobody has any suggestions, I'll wipe the whole works, download it all, and re-install just to make sure I didn't do anything.dumb.
newpenguin:
It's not really Slackware 9.0. It's the Slackware-Current tree from
ftp://ftp.slackware.com/pub/slackware-current that will become Slackware 9.0, someday. I used ncftp and had it get the entire dir. Brace yourself for a long download. There's a lot there. Maybe someday we can get rsync access and make keeping up eaiser.
When you got it, have a look at the README in the isolinux dir and do what it says. Works great.
!
.
