Re: compiling troubles on Solaris 8
>> As an aside, Solaris 8 comes with prebuilt versions of Apache >> and mod_perl, >does anyone familiar with HP-UX, AIX, or IRIX know whether this is true of >these platforms as well? >Whether they are DSO mod_perl or not would also be helpful. HP-UX doesn't consider Perl a supportable piece of software, nor Apache. Needless to say, it doesn't come prebuilt. The compiler that comes w/the os isn't ansii compliant and is only good for rebuilding the kernel (but hey, you can buy HP's ansii c compiler for only a few thousand dollars!). We ended up building a gnu development environment in order to build mod_Perl. We could not get it to work as a DSO :(. Once we got everything up and running, it's a decent enough platform. Regards, Dave Homsher
Re: compiling troubles on Solaris 8
Geoffrey Young wrote: > > As an aside, Solaris 8 comes with prebuilt versions of Apache > > and mod_perl, > > does anyone familiar with HP-UX, AIX, or IRIX know whether this is true of > these platforms as well? > > Whether they are DSO mod_perl or not would also be helpful. On Solaris it is built as a DSO. -- Alan Burlison Solaris Kernel Development, Sun Microsystems
RE: compiling troubles on Solaris 8
> -Original Message- > From: Alan Burlison [mailto:[EMAIL PROTECTED]] > Sent: Monday, August 06, 2001 4:54 AM > To: Ged Haywood > Cc: Bryan McGuire; Paul Phillips; [EMAIL PROTECTED] > Subject: Re: compiling troubles on Solaris 8 > [snip] > > As an aside, Solaris 8 comes with prebuilt versions of Apache > and mod_perl, does anyone familiar with HP-UX, AIX, or IRIX know whether this is true of these platforms as well? Whether they are DSO mod_perl or not would also be helpful. thanks --Geoff
Re: compiling troubles on Solaris 8
Ged Haywood wrote: > Well OK, read "What Compiler Should Be Used to Build mod_perl?" in the > "install" section of Stas' new book if you want to use different compilers > - but don't say I didn't warn you! :) By all means, please feel free to buy our compiler. Alan Burlison
Re: compiling troubles on Solaris 8
Hi there, On Mon, 6 Aug 2001, Alan Burlison wrote: > > Please note that the same compiler must be used to build Perl and mod_perl, > > Not so. gcc should work just fine. The problem is that when perl is > configured and built, it saves the compiler name and flags in Config.pm. Well OK, read "What Compiler Should Be Used to Build mod_perl?" in the "install" section of Stas' new book if you want to use different compilers - but don't say I didn't warn you! :) 73, Ged.
Re: compiling troubles on Solaris 8
> > > When I first started, it did not seem to be using gcc, so I renamed > > > /usr/ucb/cc to cc.default, and make /usr/ucb/cc a link to gcc. Please don't do that - switch it back and just make sure gcc is somewhere on your path. > Please note that the same compiler must be used to build Perl and mod_perl, Not so. gcc should work just fine. The problem is that when perl is configured and built, it saves the compiler name and flags in Config.pm. We build Solaris with the Workshop compilers, and therefore subsequent attempts to build modules (e.g. mod_perl) also try to use the same compiler. A workaround is to modify /usr/perl5/5.00503/sun4-solaris/Config.pm so it contains the correct information (flags etc) for gcc rather than Workshop. I've attached a sample Config.pm that should work with the copy of gcc that is shipped on the Solaris 8 companion cd. I suggest you move the standard Config.pm somewhere safe and use the attached file in its place. There are only 4 differences between it and the standard Config.pm. I'm working on something a little cleaner for Solaris 9, probably requiring you to set PERL5LIB to point perl to a gcc-ized version of Config.pm, rather than the standard one. As an aside, Solaris 8 comes with prebuilt versions of Apache and mod_perl, so unless you need the latest and greatest you might find it easiest to use the bundled versions - see 'man apache' for details. Alan Burlison Solaris Kernel Development, Sun Microsystems Config.pm.gz
Re: compiling troubles on Solaris 8
Hi guys, > On Sunday, August 5, 2001, at 04:05 PM, Paul Phillips wrote: > > > I am trying to build mod_perl 1.26 and Apache 1.3.20 on my Solaris 8 > > box. I have installed the additional CD with the developer tools > > including the gnu utilities and gcc. > > > > When I first started, it did not seem to be using gcc, so I renamed > > /usr/ucb/cc to cc.default, and make /usr/ucb/cc a link to gcc. Just a thought, what is the command your system is using to link? If it's not "gcc -something" you might run into trouble with just that one symlink. > > That seemed to get me further. However, I have reached a fatal error, > > On Sun, 5 Aug 2001, Bryan McGuire wrote: > > Sun wants to sell you it's Forte for C (formerly known as the Sun > Workshop compiler). There's a hundred reasons to use the sun compiler > over gcc, and one pretty big reason why you you don't want to use it. Please note that the same compiler must be used to build Perl and mod_perl, so if you used gcc to build your mod_perl then you'd better run perl -V to see what compiler built your Perl. Note that's "-V" and not "-v". Rebuild Perl if you have to. It's a little more long-winded than it is to build mod_perl but it's easy enough, especially if you accept all the defaults. (I don't know if accepting all the defaults will work for Sun/Sparc and I'd be pleased to know if it does.:) Building mod_perl is covered in the Guide: http://perl.apache.org/guide I would recommend getting the .pod source of the guide and using % cd guide_src (or whatever you call the directory that holds the source:) % grep -i compile * If the guide source is in more than one subdirectory and you're using GNU grep you can add the "r" switch to search recursively. If your version of grep doesn't have that switch then you'll need to be a little more creative. Of course you can substitute any other cleverly chosen word for the word "compile" above to look at any other topic. In the case above "compile" matches both the words "compile" and "compiler" and the -i switch for grep ignores case. Well OK, it wasn't all that clever... 73, Ged.
Re: compiling troubles on Solaris 8
Sun wants to sell you it's Forte for C (formerly known as the Sun Workshop compiler). There's a hundred reasons to use the sun compiler over gcc, and one pretty big reason why you you don't want to use it. If you can get it into your budget, by all means go for the real Sun compiler. It generates code that is highly optimized for sparc hardware, particularly if you are running multiple processors. If nothing else, request a time limited demo license from Sun so you can build mod_perl (and every other module you think you'll ever need off of CPAN). On Sunday, August 5, 2001, at 04:05 PM, Paul Phillips wrote: > Hello, > > I am trying to build mod_perl 1.26 and Apache 1.3.20 on my Solaris 8 > box. I have installed the additional CD with the developer tools > including the gnu utilities and gcc. > > When I first started, it did not seem to be using gcc, so I renamed > /usr/ucb/cc to cc.default, and make /usr/ucb/cc a link to gcc. > > That seemed to get me further. However, I have reached a fatal error, > and don't have a clue what this means. The error messages are quoted > below. > > I am trying to do the simplest build possible, following the INSTALL > instructions. So after unzipping and untarring apache and mod_perl, > from within the mod_perl distribution directory, I type > perl Makefile.PL > I confirm that I want it build from ../apache_1.3.20/src, and that I > want to store the new httpd in that directory. > > Then I type make. After a bit, I get this: > > mkdir ../blib/arch/auto/Apache/Leak > mkdir ../blib/lib/auto/Apache/Leak > cp Leak.pm ../blib/lib/Apache/Leak.pm > /bin/perl -I/usr/perl5/5.00503/sun4-solaris -I/usr/perl5/5.00503 > /usr/perl5/5.00 > 503/ExtUtils/xsubpp -typemap /usr/perl5/5.00503/ExtUtils/typemap > -typemap typem > ap Leak.xs >xstmp.c && mv xstmp.c Leak.c > cc -c -xO3 -xdepend -DVERSION=\"1.00\" -DXS_VERSION=\"1.00\" > -KPIC -I/usr > /perl5/5.00503/sun4-solaris/CORE -DSOLARIS2=280 -DUSE_EXPAT > -I/lib/expat-lite -D > NO_DL_NEEDED Leak.c > cc: unrecognized option `-KPIC' > cc: language depend not recognized > cc: Leak.c: linker input file unused since linking not done > Running Mkbootstrap for Apache::Leak () > chmod 644 Leak.bs > LD_RUN_PATH="" cc -o ../blib/arch/auto/Apache/Leak/Leak.so -G Leak.o > cc: Leak.o: No such file or directory > cc: No input files > *** Error code 1 > make: Fatal error: Command failed for target > `../blib/arch/auto/Apache/Leak/Leak > .so' > Current working directory /home/paul/mod_perl-1.26/Leak > *** Error code 1 > make: Fatal error: Command failed for target `subdirs' > > I have no idea what is wrong, or how to fix it, so I would appreciate > any help. > > thanks! > > ___ > Paul Phillips > Director of Orchestral Activities, Meadows School of the Arts > Southern Methodist University > > "You must sing every note you play, sing even through the rests!" > Arturo Toscanini >
compiling troubles on Solaris 8
Hello, I am trying to build mod_perl 1.26 and Apache 1.3.20 on my Solaris 8 box. I have installed the additional CD with the developer tools including the gnu utilities and gcc. When I first started, it did not seem to be using gcc, so I renamed /usr/ucb/cc to cc.default, and make /usr/ucb/cc a link to gcc. That seemed to get me further. However, I have reached a fatal error, and don't have a clue what this means. The error messages are quoted below. I am trying to do the simplest build possible, following the INSTALL instructions. So after unzipping and untarring apache and mod_perl, from within the mod_perl distribution directory, I type perl Makefile.PL I confirm that I want it build from ../apache_1.3.20/src, and that I want to store the new httpd in that directory. Then I type make. After a bit, I get this: mkdir ../blib/arch/auto/Apache/Leak mkdir ../blib/lib/auto/Apache/Leak cp Leak.pm ../blib/lib/Apache/Leak.pm /bin/perl -I/usr/perl5/5.00503/sun4-solaris -I/usr/perl5/5.00503 /usr/perl5/5.00 503/ExtUtils/xsubpp -typemap /usr/perl5/5.00503/ExtUtils/typemap -typemap typem ap Leak.xs >xstmp.c && mv xstmp.c Leak.c cc -c -xO3 -xdepend -DVERSION=\"1.00\" -DXS_VERSION=\"1.00\" -KPIC -I/usr /perl5/5.00503/sun4-solaris/CORE -DSOLARIS2=280 -DUSE_EXPAT -I/lib/expat-lite -D NO_DL_NEEDED Leak.c cc: unrecognized option `-KPIC' cc: language depend not recognized cc: Leak.c: linker input file unused since linking not done Running Mkbootstrap for Apache::Leak () chmod 644 Leak.bs LD_RUN_PATH="" cc -o ../blib/arch/auto/Apache/Leak/Leak.so -G Leak.o cc: Leak.o: No such file or directory cc: No input files *** Error code 1 make: Fatal error: Command failed for target `../blib/arch/auto/Apache/Leak/Leak .so' Current working directory /home/paul/mod_perl-1.26/Leak *** Error code 1 make: Fatal error: Command failed for target `subdirs' I have no idea what is wrong, or how to fix it, so I would appreciate any help. thanks! ___ Paul Phillips Director of Orchestral Activities, Meadows School of the Arts Southern Methodist University "You must sing every note you play, sing even through the rests!" Arturo Toscanini
