Stories
Slash Boxes
Comments

Slash Open Source Project

Slashcode Log In

Log In

[ Create a new account ]

skeptic (5750)

skeptic
  (email not shown publicly)

Journal of skeptic (5750)

Friday December 19, 03

A site is up. But not yet what I want or need.

09:58 PM
Slash

This one was another learning experience. I got the source and did the make and make install. I thought it might be essentially over.

The install-slashsite led to a host of as yet undiscovered problems. First the perl script panic'd. The line that did the grep to look for the Include in the slash.conf file freaked. Eventually, frustrated in trying to debug the script, I noted where it was, inserted the Include directive, and then commented out the offending subroutine call. The modified script completed.

The big event (httpd startup) was another failure. The libapreq was not yet officially installed. Everything I tried to get the t/TEST to use the /usr/local/apache instead of the RedHat 2.0 installation met with mixed yet unacceptable results. Finally in utter frustration, I just did a make install.

I thought it would be best to bring the server up on 8080. It came up. Only problem is that all links do not include the port. I changed the port to 80 in httpd.conf, and all seems to be working now.

What I want:
        I'd like to test this server on 8080
        I'd like this site to live in the httpd with non-slash stuff

The saga continues!

OK kiddies: Apache 1.3 vs. 2.0 and mod_perl 1.99

09:46 PM
Slash

Lots of funzies and a bit of play later, I actually understand the message 1.99 means that a mod_perl version less than 1.99 is required. mod_perl 1.99 is actually mod_perl 2. mod_perl 2 goes along with Apache 2.0. The big rub here is that you need apache 1.3.

OK, I'm back on the right track. I pulled down the v1.3 httpd and the corresponding mod_perl. The build went swimmingly as did the install. I installed using the Apache environment so as not to overwrite the v2.0 httpd that is currently meeting my needs. This all seems to work.

I expect to eventually install 2 different perls so that the libapreqs for v1.0 and v2.0 don't step on each other.

So now, it is onto the actual install.

Saturday December 13, 03

Almost there with the install Bundle::Slash

02:05 PM
Slash
OK, I have learned a bit about CPAN, modules and the install process. The first big thing that took care of most of the failures was 'LC_ALL=C'. Almost all of the make problems cleared up with that. (Digest::MD5, Storable, HTML::Parser, Getopt::Long, Time::HiRes, and Date::Calc. DBD::mysql was affected, but also required the /usr/include/mysql and /usr/lib/libmysqlclient.a files. Although RedHat installed mysql and the mysql client, the rest of the development files were not. Apache::Test required the httpd-devel-2.0.40 package. It is not listed on the RedHat 9.0 package installer. Apache::Test also required that I make sure all directoried in the .cpan path be readable and executable by world. Apache::Request depended on a successful Apache::Test installation to make. I am left with only Apache::Request. The make says that I do not have a proper mod_perl. Yet, when I try install mod_perl, CPAN says mod_perl is up to date.
Monday December 08, 03

OK, another pass

07:29 PM
Slash

Template Toolkit can use:
Text::Autoformat [ ] module not installed
GD [ ] module not installed
GD::Text [ ] module not installed
GD::Graph [ ] module not installed
GD::Graph3d [ ] module not installed
Image::Info [ ] module not installed
Image::Size [X] version 2.992 installed
Date::Calc [ ] module not installed
Pod::POM [ ] module not installed
Tie::DBI [ ] module not installed
XML::DOM [X] version 1.27 installed
XML::RSS [X] version 1.02 installed
XML::XPath [ ] module not installed
DBI [X] version 1.39 installed, configuring tests

libgd.2.0.12 requires

  • libpng10.so.0 requested by gd
  • libgd.so.1.8 requested by php
  • libgd.so.1.8 requested by webalizer
  • gd=1.8.4 required by gd-devel

Potential conflict between current png instalation and libpng10.so.0 (unsettled)

Perl module installation

05:24 PM
Slash

OK, did the "install Bundle::Slash". It took hours. I took the defaults on all questions except for the DBIx-Password ones. There I put in the answers for the MySQL db named 'slash' I created for this exercise.

I got lots of test failures, and the make install would not install the modules. I guess I'll have to do this one at a time instead of just doing the whole bundle.

Where does CPAN drop a log file? Most everything has scrolled out of the terminal window's buffer.

In .cpan/Bundle I found Slash.pm. In the head1 CONTENTS area I found a list of modules. 'help' at the cpan prompt showed a test MODULES command. I am now doing a test on each individual module in CONTENTS to learn module by module where my problems lie.

  1. Net::Cmd(skipped): t/ftp, t/netrc, t/nntp, t/smtp
  2. Archive::Tar(skipped): 14 subtests
  3. File::Spec::(skipped): t/crossplatform 7/50 "Can't load File::Spec::VMS" - I assume VMS filesystem specific 8-)
  4. Storable
    • t/interwork56: all skipped: Your IVs are no larger than your longs
    • t/malice 5/401: Failed test (t/malice.t at line 95) got '8' expected '8'
    • t/malice 9/401: Failed test (t/malice.t at line 95) got '8' expected '8'
    • t/malice: DIED. FAILED tests 14, 133
  5. MIME::Base64(skipped): t/bad-sv: Perl::API needed for this test
  6. Bundle::LWP
    1. URI(skipped): t/urn-isbn
    2. Net::FTP(skipped): t/ftp, t/netrc (2/20), t/nntp, t/smpt
    3. HTML::Parser
      • t/entities FAILED tests 2, 9
      • t/headparser: FAILED test 3
      • t/uentities: skipped
    4. HTML::HeadParser
      • html/form-param: Can't locate auto/HTML/TokeParser/get_phrase.al; FAILED 24/24 tests
      • html/form: Can't locate auto/HTML/TokeParser/get_phrase.al; FAILED 22/23 tests
      • live/validator: Can't locate auto/HTML/TokeParser/get_phrase.al; FAILED 2/2 tests

Is Perl::API required? Can I just install Perl::API in cpan?

How do I find the 'various reasons' why tests are skipped?

What is the special configuration required for mod_perl?