Re: HTTP_REFERRER and Mod_perl

2001-01-15 Thread Jeremy A. Mates

On Mon, 15 Jan 2001, Stef Telford wrote:
   The problems arise when i try to use HTTP_REFERRER from
 the $ENV enviroment. All the other variables are set jst fine
 (HTTP_HOST,
 HTTP_ACCEPT, HTTPS) but no HTTP_REFERRER. What am I doing
 wrong to not 'obtain' this variable. it never shows up in the $ENV list.
 Is this an oversight of mod_perl (v1.24).

Probably because somebody at Netscape didn't spell check when creating the
aforementioned Header field:

HTTP_REFERER
 ^
A.k.a. the internet generation's hidden agenda against referrer's third r.

-- 
Jeremy Mates   http://www.sial.org/




Re: compiling modperl on alpha

2000-11-16 Thread Jeremy A. Mates

On Thu, 16 Nov 2000, Didier Godefroy wrote:
 I'm trying to compile mod_perl as a dso with apxs on Alpha/Tru64 unix and
 there is an error from the linker:
[snip]
 Can anyone give a clue?

Make sure the ld that is being called is the exact same one that was used
to build perl itself, e.g. by altering your PATH environment variable to
point to either the vendor default first (under /usr/bin) or perhaps to
the GNU ld that might have gotten installed somewhere under /freeware/bin
or /usr/local/bin.

ld flags are usually set during the compilation of perl using the
Configure script; you can run `perl -V` to show what the flags are on the
perl binary earliest in your PATH.  Changing the ld binary used or ld
flags generally involves a manual recompilation of all things perl. :-/

Also note that mod_perl as a DSO isn't recommended by the mod_perl
documentation...

-- 
Jeremy Mates
http://www.sial.org/




Re: compiling modperl on alpha

2000-11-16 Thread Jeremy A. Mates

On Thu, 16 Nov 2000, Didier Godefroy wrote:
 GNU ld isn't on either system and the error is the exact same on both,
 they seem to all this in common:

 -Wl,-rpath,/usr/local/lib/perl5/5.6.0/alpha-dec_osf/CORE'
[snip]
 dlsrc=dl_dlopen.xs, dlext=so, d_dlsymun=undef, ccdlflags='
 -Wl,-rpath,/usr/local/lib/perl5/5.6.0/alpha-dec_osf/CORE'
 cccdlflags=' ', lddlflags='-shared -expect_unresolved "*" -O4 -msym -std
 -s -L/usr/local/lib'

Hmmm... the Digitals I have share similar ccdlflags statements.  Did you
install perl 5.6.0 from scratch or via a package of some kind?  (If via
package, the people who built the package may have used a different ld or
had different environment settings from yours.)

You might be able to pass the flag ld appeared to be complaining about
with the following trick:

$ LDFLAGS="-_SYSTYPE_SVR4" command_that_fails

Which should work for Bourne-related shells.  The ld man page didn't
appear contain anything useful, so I'm guessing moreso than usual at this
point. :)

You could also try asking on the tru64-unix-managers list:

http://www.ornl.gov/cts/archives/mailing-lists/

mailto:[EMAIL PROTECTED]?body=subscribe

 What is the problem with doing that? I tried compiling it statically
 first, but I get other types of errors when running the tests, it
 always fails. The httpd is running but the tests won't, and the log
 doesn't say anything that helps to find out why. What other choices
 are there then?

If static fails, then you can probably get away with DSO if you keep the
httpd process memory usage down with various directives.  There's more on
this just recently in this list's archives, as I recall...

-- 
Jeremy Mates
http://www.sial.org/