Scoop -- the swiss army chainsaw of content management
Front Page · Everything · News · Code · Help! · Wishlist · Project · Scoop Sites · Dev Notes · Latest CVS changes · Development Activities
Humbled Solaris Guru begs for guidance from the Scoop gods Docs
By on2raj , Section Help! []
Posted on Mon Sep 20, 2004 at 12:00:00 PM PST
I am trying to convert my site from a home-brewed ksh-based content management system to scoop.

Unfortunately, I'm having rather a rough time of it.

I'm using a default Solaris 9 build on a dual 300MHZ Ultra 2 and I'm a pretty advanced user (used to teach Solaris, do enterprise tech support), just not a programmer.

I'm having major problems with building mod_perl, I followed the instructions to the tee, but it appears as though perl keeps calling cc, which I don't have, to do the compiling, in stead of gcc, which everything else is using.

I've managed to edit the Configuration.pm file to cause it to call gcc, but then it bombs with "invalid parameter" errors.

And don't even get me started on the problems with CPAN.

Since the default solaris build comes with apache w/mod_perl I tried to skip this step, but I can't get CPAN to install the requisite perl modules.

I started going through and doing it by hand, but after the umpteenth unresolved dependency sent me back to the ftp site I got a little discouraged.

Does anybody have any insight as to how to get this running on Solaris 9? (Short of getting up to speed on perl and apache, etc)

< Censorship feature for autors | Pilot Project >

Menu
· create account
· faq
· search
· report bugs
· Scoop Administrators Guide
· Scoop Box Exchange

Login
Make a new account
Username:
Password:

Poll
What would you do?
· Wipe it and install NetBSD 0%
· Get a real OS, like NT 0%
· Set up a complete GNU development environment in which to work, recompiling perl, apache, mysql, et al, from scratch. 25%
· Take up knitting 25%
· Smoke a bowl and go hiking 25%
· Cry 0%
· Forget about scoop, KSH RULZ!!! 0%
· Pester the Scoop community till someone with a clue ponies up the skeeilz to save me. 0%
· Offer gmail invites 0%
· Pay somebody to do it. 25%

Votes: 4
Results | Other Polls

Related Links
· Scoop
· More on Docs
· Also by on2raj

Story Views
  36 Scoop users have viewed this story.

Display: Sort:
Humbled Solaris Guru begs for guidance from the Scoop gods | 2 comments (2 topical, 0 hidden)
What I did (5.00 / 1) (#1)
by schmolli on Mon Sep 20, 2004 at 06:46:58 PM PST

I'm pretty sure that these are my compile notes (solaris 8, gcc-3.2) I'd expect them to work on Solaris 9 with little or no tweaking. Before you go to the trouble of reading through my meanderings, I'll mention that it sounds like the source of most of your trouble comes from using the perl install that comes with the OS. You'll want to build your own with the same compiler you'll be using on mod_perl. (perl has a notion of how it was built, and it tries to keep using that notion for future building.) So before ripping your machine apart, you might just want to try a custom perl install.

Before installing apache/mod_perl, I installed gcc-3.2 (Solaris package from sunfreeware,) libexpat ($prefix=/usr/local), and perl ($prefix=/usr/local/perl-$VERSION). If you try to use the perl that comes with Solaris, you will have all kinds of problems. Don't do that. After you've got perl installed in /usr/local/perl-$VERSION, make some symlinks: /usr/local/perl@ -> perl-$VERSION /usr/local/bin/perl@ -> ../perl/bin/perl /usr/bin/perl@ -> /usr/local/bin/perl

You may want to consider that last symlink to be a little dangerous since you're messing around in OS territory, but it's what I do and it works fine for me. Note that if you do NOT replace /usr/bin/perl with a symlink to your new install, you will have to be very sure that when you're doing the apache build that you have /usr/local/bin in your PATH before /usr/bin

Lessee, I also had openssl and libmm installed in /usr/local (this is just for mod_ssl, though.)

# apache 1.3.31 with mod_ssl and mod_perl
export CPPFLAGS="-I/usr/local/include"
export LDFLAGS="-L/usr/local/lib -Wl,-R/usr/local/lib"
gzip -dc mod_perl-1.0-current.tar.gz | tar xf -
gzip -dc apache_1.3.31.tar.gz | tar xf -
gzip -dc mod_ssl-2.8.19-1.3.31.tar.gz | tar xf -

cd mod_ssl-2.8.19-1.3.31
./configure --with-apache=../apache_1.3.31 \
	--with-ssl=SYSTEM --with-mm=SYSTEM \
	--prefix=/usr/local/apache-1.3.31

cd ../mod_perl-1.29
perl Makefile.PL DO_HTTPD=1 USE_APACI=1 EVERYTHING=1 \
	SSL_BASE=/usr/local APACHE_PREFIX=/usr/local/apache-1.3.31 \
  
APACI_ARGS=--enable-suexec,--suexec-caller=httpd,--suexec-docroot=/home/htdocs,--server-uid=httpd,-
-
server-gid=httpd,--enable-module=most,--enable-shared=max

make
make test
make install

Next, I installed a prebuilt mysql from mysql.com in /usr/local. I wasn't too happy about that because I really wanted to build it from scratch with...uh...something that I don't remember off the top of my head, but it was a real bear to compile, so just went with the prebuilt package.

Last was the scoop install. I just ran the provided install script for my first time since it has the nifty CPAN thing. For subsequent scoop installs on that host, I did stuff manually, and that worked just fine.



Humbled Solaris Guru begs for guidance from the Scoop gods | 2 comments (2 topical, 0 hidden)
Display: Sort:

Hosted by ScoopHost.com Powered by Scoop
All trademarks and copyrights on this page are owned by their respective companies. Comments are owned by the Poster. The Rest © 1999 The Management

create account | faq | search