You are viewing a plain text version of this content. The canonical link for it is here.
Posted to modperl@perl.apache.org by dorian <do...@foobarsystems.com> on 2003/02/14 05:30:58 UTC
Apache::Module installation issues
i'm not sure that this is an actual problem with Apache::Module itself, but
it seems to stem from mod_perl distribution's mod_perl.h here:
#ifdef PERL_THREADS
#define _INCLUDE_APACHE_FIRST
#endif
#ifdef _INCLUDE_APACHE_FIRST
#include "apache_inc.h"
#endif
the perl i built against was the stock debian/i386/unstable 5.8.0 which has
ithreads built in, although i had similar results with a source-built copy
on solaris9/sparc. the mod_perl version is 1.27. i found that if i explicitly
prepended the include for apache_inc.h in the xs, the module appeared to build
successfully.
strangely enough, the -DPERL_THREADS was being passed into the build, which
to my knowledge should have activated the include but i suppose i must be
missing something. i notice that the module hasn't been updated since 1999,
is there a replacement for its functionality that i don't know about?
cheers,
.dorian
Re: the modperl-modules repository ( was Re: Apache::Module installation
issues)
Posted by Stas Bekman <st...@stason.org>.
Ask Bjoern Hansen wrote:
> On Wed, 12 Mar 2003, Stas Bekman wrote:
>
>
>>>What should we call the repository? I have Apache::DBI under the
>>>"Apache/" directory. Should we just have the others go there too?
>>>That would make sense, no?
>>
>>Let's call it 'modperl-modules'? 'Apache' could do too, but then we will have
>>things like Apache/Apache/Peek... modperl-modules/Apache/Peek reads better.
>
>
> No, we would just have Apache/Peek. :-)
Ah, no, it should be Apache-Peek, regardless what the top level dir is.
Apache/Apache-Peek or modperl-modules/Apache-Peek. not Apache/Peek as I've
suggested before.
Also if some of the modules will have separate lifes for mp1 and mp2. It'll be:
Apache-Peek-1.0
Apache-Peek-2.0
or similar.
> We can make an alias so they also can be checked out as
> modperl-modules/Apache/*.
>
>
>>However there are a few Doug's modules which aren't strictly mod_perl: GTop
>>and Sys::Signal (which are looking for a new home), but I guess these can go
>>into the same dir.
>
>
> Hmn, that's an argument for making it modperl-modules/*.
>
> Robert and I will consider if we want to make a top level directory
> for "CPAN modules" too, I think. We can make it easy to use with
> CVS aliases and groups, so don't worry about that. :-)
As I pointed out in the reply to Robert (to explain my reasoning):
I've suggested 'modperl-modules', so it'll fit well with repositories from
cvs.apache.org's hierarchy, which has modperl, modperl-2.0, modperl-docs.
I'm thinking here about developer's convenience (mine ;). The easiest would be
to have it hosted at cvs.apache.org, but as ask correctly pointed out, getting
commit access to new people is not simple at all.
__________________________________________________________________
Stas Bekman JAm_pH ------> Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide ---> http://perl.apache.org
mailto:stas@stason.org http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org http://ticketmaster.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org
For additional commands, e-mail: dev-help@perl.apache.org
Re: the modperl-modules repository ( was Re: Apache::Module installation
issues)
Posted by Ask Bjoern Hansen <as...@develooper.com>.
On Wed, 12 Mar 2003, Stas Bekman wrote:
> > What should we call the repository? I have Apache::DBI under the
> > "Apache/" directory. Should we just have the others go there too?
> > That would make sense, no?
>
> Let's call it 'modperl-modules'? 'Apache' could do too, but then we will have
> things like Apache/Apache/Peek... modperl-modules/Apache/Peek reads better.
No, we would just have Apache/Peek. :-)
We can make an alias so they also can be checked out as
modperl-modules/Apache/*.
> However there are a few Doug's modules which aren't strictly mod_perl: GTop
> and Sys::Signal (which are looking for a new home), but I guess these can go
> into the same dir.
Hmn, that's an argument for making it modperl-modules/*.
Robert and I will consider if we want to make a top level directory
for "CPAN modules" too, I think. We can make it easy to use with
CVS aliases and groups, so don't worry about that. :-)
- ask
--
ask bjoern hansen, http://www.askbjoernhansen.com/ !try; do();
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org
For additional commands, e-mail: dev-help@perl.apache.org
Re: the modperl-modules repository ( was Re: Apache::Module installation
issues)
Posted by Stas Bekman <st...@stason.org>.
Ask Bjoern Hansen wrote:
> On Tue, 11 Mar 2003, Stas Bekman wrote:
>
> [cvs at cvs.perl.org]
>
>>Ask, so how do we take it from here? I now have fixes for a bunch
>>of modules which were orphaned by their owners.
>
>
> Create an account at http://auth.perl.org/ if you don't have one
> already and send your user name to cvs at perl.org.
ok
> What should we call the repository? I have Apache::DBI under the
> "Apache/" directory. Should we just have the others go there too?
> That would make sense, no?
Let's call it 'modperl-modules'? 'Apache' could do too, but then we will have
things like Apache/Apache/Peek... modperl-modules/Apache/Peek reads better.
However there are a few Doug's modules which aren't strictly mod_perl: GTop
and Sys::Signal (which are looking for a new home), but I guess these can go
into the same dir.
__________________________________________________________________
Stas Bekman JAm_pH ------> Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide ---> http://perl.apache.org
mailto:stas@stason.org http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org http://ticketmaster.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org
For additional commands, e-mail: dev-help@perl.apache.org
Re: the modperl-modules repository ( was Re: Apache::Module installation
issues)
Posted by Ask Bjoern Hansen <as...@develooper.com>.
On Tue, 11 Mar 2003, Stas Bekman wrote:
[cvs at cvs.perl.org]
> Ask, so how do we take it from here? I now have fixes for a bunch
> of modules which were orphaned by their owners.
Create an account at http://auth.perl.org/ if you don't have one
already and send your user name to cvs at perl.org.
What should we call the repository? I have Apache::DBI under the
"Apache/" directory. Should we just have the others go there too?
That would make sense, no?
> Also would it be possible to keep the history while adding these projects?
> e.g. if the original owners supply a snapshot of the actual cvs repository?
Yes, of course.
- ask
--
ask bjoern hansen, http://www.askbjoernhansen.com/ !try; do();
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org
For additional commands, e-mail: dev-help@perl.apache.org
Re: the modperl-modules repository ( was Re: Apache::Module installation
issues)
Posted by Stas Bekman <st...@stason.org>.
Stas Bekman wrote:
> Ask Bjoern Hansen wrote:
>
>> On Mon, 17 Feb 2003, Stas Bekman wrote:
>>
>> We'd be happy to host such a repository over at cvs.perl.org.
>> (Easier/lower overhead to get people commit access there than at
>> cvs.apache.org).
>
>
> +1, Thanks Ask!
Ask, so how do we take it from here? I now have fixes for a bunch of modules
which were orphaned by their owners.
Also would it be possible to keep the history while adding these projects?
e.g. if the original owners supply a snapshot of the actual cvs repository?
__________________________________________________________________
Stas Bekman JAm_pH ------> Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide ---> http://perl.apache.org
mailto:stas@stason.org http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org http://ticketmaster.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org
For additional commands, e-mail: dev-help@perl.apache.org
Re: the modperl-modules repository ( was Re: Apache::Module installation
issues)
Posted by Stas Bekman <st...@stason.org>.
Ask Bjoern Hansen wrote:
> On Mon, 17 Feb 2003, Stas Bekman wrote:
>
> We'd be happy to host such a repository over at cvs.perl.org.
> (Easier/lower overhead to get people commit access there than at
> cvs.apache.org).
+1, Thanks Ask!
__________________________________________________________________
Stas Bekman JAm_pH ------> Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide ---> http://perl.apache.org
mailto:stas@stason.org http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org http://ticketmaster.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org
For additional commands, e-mail: dev-help@perl.apache.org
Re: the modperl-modules repository ( was Re: Apache::Module installation
issues)
Posted by Ask Bjoern Hansen <as...@develooper.com>.
On Mon, 17 Feb 2003, Stas Bekman wrote:
We'd be happy to host such a repository over at cvs.perl.org.
(Easier/lower overhead to get people commit access there than at
cvs.apache.org).
- ask
--
ask bjoern hansen, http://www.askbjoernhansen.com/ !try; do();
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org
For additional commands, e-mail: dev-help@perl.apache.org
the modperl-modules repository ( was Re: Apache::Module installation
issues)
Posted by Stas Bekman <st...@stason.org>.
Geoffrey Young wrote:
>
>
> dorian wrote:
>
>>> I don't remember what was the outcome of the patch I've posted a long
>>> time ago. I sent it after having the same problem.
>>
>>
>>
>> ah, so it's actually a problem with the mod_perl distribution then?
>
>
> well, maybe not.
>
> try this patch
>
> http://marc.theaimsgroup.com/?l=apache-modperl-dev&m=98295430720401&w=2
>
> as you can see from the rest of the thread, doug applied it but it looks
> as if Apache::Module hasn't had a release since then.
OK, let's pursue my idea of a new repository modperl-modules, where we can put
essential modules which are maintained by those who already have a commit
access, but either too busy to actively commit things (e.g., doug) or simply
want the code to be in the public repository (e.g., me).
Once we have this repository we can all commit to it, and the respective CPAN
module owners can simply upload the new releases. Moreover nowadays CPAN
allows to co-own modules, so if one of us is not around the co-owner can
release the module. Finally users will be able to access the cvs snapshots of
the modules.
What layout should we have? Should we have modules separated by the mod_perl
version they build with? Let's take a few modules. We have Apache::Module
which works with 1.0, Apache::Scoreboard which we have separate versions for
each mod_perl released. And Apache::Peek, which I've ported to work with both
mod_perl versions (but can't release before we change 2.0 to support 3rd party
xs modules).
So should we go for something like:
modperl-modules/1.0/Apache-Module
modperl-modules/1.0/Apache-Scoreboard
modperl-modules/2.0/Apache-Scoreboard
modperl-modules/any/Apache-Peek
or:
modperl-modules/Apache-Module-1.0
modperl-modules/Apache-Scoreboard-1.0
modperl-modules/Apache-Scoreboard-2.0
modperl-modules/Apache-Peek/
or else (your input comes here):
__________________________________________________________________
Stas Bekman JAm_pH ------> Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide ---> http://perl.apache.org
mailto:stas@stason.org http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org http://ticketmaster.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org
For additional commands, e-mail: dev-help@perl.apache.org
Re: Apache::Module installation issues
Posted by Geoffrey Young <ge...@modperlcookbook.org>.
dorian wrote:
>>I don't remember what was the outcome of the patch I've posted a long time
>>ago. I sent it after having the same problem.
>
>
> ah, so it's actually a problem with the mod_perl distribution then?
well, maybe not.
try this patch
http://marc.theaimsgroup.com/?l=apache-modperl-dev&m=98295430720401&w=2
as you can see from the rest of the thread, doug applied it but it looks as
if Apache::Module hasn't had a release since then.
HTH
--Geoff
Re: Apache::Module installation issues
Posted by dorian <do...@foobarsystems.com>.
> I don't remember what was the outcome of the patch I've posted a long time
> ago. I sent it after having the same problem.
ah, so it's actually a problem with the mod_perl distribution then?
i'm actually curious as to where apache_inc.h is supposed to be included,
if threads aren't defined.
.dorian
Re: Apache::Module installation issues
Posted by Stas Bekman <st...@stason.org>.
dorian wrote:
> i'm not sure that this is an actual problem with Apache::Module itself, but
> it seems to stem from mod_perl distribution's mod_perl.h here:
>
> #ifdef PERL_THREADS
> #define _INCLUDE_APACHE_FIRST
> #endif
>
> #ifdef _INCLUDE_APACHE_FIRST
> #include "apache_inc.h"
> #endif
>
> the perl i built against was the stock debian/i386/unstable 5.8.0 which has
> ithreads built in, although i had similar results with a source-built copy
> on solaris9/sparc. the mod_perl version is 1.27. i found that if i explicitly
> prepended the include for apache_inc.h in the xs, the module appeared to build
> successfully.
>
> strangely enough, the -DPERL_THREADS was being passed into the build, which
> to my knowledge should have activated the include but i suppose i must be
> missing something. i notice that the module hasn't been updated since 1999,
> is there a replacement for its functionality that i don't know about?
I don't remember what was the outcome of the patch I've posted a long time
ago. I sent it after having the same problem.
Index: src/modules/perl/mod_perl.h
===================================================================
RCS file: /home/cvs/modperl/src/modules/perl/mod_perl.h,v
retrieving revision 1.116
diff -u -r1.116 mod_perl.h
--- src/modules/perl/mod_perl.h 23 May 2002 04:35:16 -0000 1.116
+++ src/modules/perl/mod_perl.h 14 Feb 2003 04:45:37 -0000
@@ -72,11 +72,8 @@
#endif
#ifdef PERL_THREADS
-#define _INCLUDE_APACHE_FIRST
-#endif
-
-#ifdef _INCLUDE_APACHE_FIRST
#include "apache_inc.h"
+#define _INCLUDE_APACHE_FIRST
#endif
#include "EXTERN.h"
__________________________________________________________________
Stas Bekman JAm_pH ------> Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide ---> http://perl.apache.org
mailto:stas@stason.org http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org http://ticketmaster.com