You are viewing a plain text version of this content. The canonical link for it is here.
Posted to apreq-dev@httpd.apache.org by Hal Robertson <ha...@yahoo.com> on 2003/07/31 05:08:21 UTC
simple apache 2 module using libapreq and mod_apreq
Hello,
I am new to this list. I have just downloaded version
2 of the library and am very happy to be working with
it.
I would like to know how far away an initial release
might be?
Also, I would like to write some simple Apache 2
modules using the library. I have a simple test
module that compiles fine and links w/ libapreq.so.2
but not mod_apreq.so. So when I go to install my
module Apache complains:
Cannot load
/home/hal/workspace/apache/release/modules/libmymod.so
into server:
/home/hal/workspace/apache/release//lib/libapreq.so.2:
undefined symbol: apreq_env_jar
I am a newbie w/ libtool and automake, but everything
looks fine to me. Am I missing something? Does
somebody have a simple example I can look at?
Any suggestions would be great.
thanks!
Hal
__________________________________
Do you Yahoo!?
The New Yahoo! Search - Faster. Easier. Bingo.
http://search.yahoo.com
Re: simple apache 2 module using libapreq and mod_apreq
Posted by Hal Robertson <ha...@yahoo.com>.
--- Randy Kobes <ra...@theoryx5.uwinnipeg.ca> wrote:
> Do you have a
> LoadModule apreq_module modules/mod_apreq.so
> directive before loading your module?
No, it was after.
Randy, you are a brilliant man. Thanks!
Hal
__________________________________
Do you Yahoo!?
The New Yahoo! Search - Faster. Easier. Bingo.
http://search.yahoo.com
Re: simple apache 2 module using libapreq and mod_apreq
Posted by Randy Kobes <ra...@theoryx5.uwinnipeg.ca>.
On Wed, 30 Jul 2003, Hal Robertson wrote:
> Hello,
Welcome!
> I am new to this list. I have just downloaded version
> 2 of the library and am very happy to be working with
> it.
>
> I would like to know how far away an initial release
> might be?
I'm not sure - Joe would have a better idea ...
> Also, I would like to write some simple Apache 2
> modules using the library. I have a simple test
> module that compiles fine and links w/ libapreq.so.2
> but not mod_apreq.so. So when I go to install my
> module Apache complains:
>
> Cannot load
> /home/hal/workspace/apache/release/modules/libmymod.so
> into server:
> /home/hal/workspace/apache/release//lib/libapreq.so.2:
> undefined symbol: apreq_env_jar
>
> I am a newbie w/ libtool and automake, but everything
> looks fine to me. Am I missing something? Does
> somebody have a simple example I can look at?
Do you have a
LoadModule apreq_module modules/mod_apreq.so
directive before loading your module?
--
best regards,
randy kobes
Re: simple apache 2 module using libapreq and mod_apreq
Posted by Stas Bekman <st...@stason.org>.
Randy Kobes wrote:
> On Tue, 5 Aug 2003, Stas Bekman wrote:
>
>
>>Randy Kobes wrote:
>>
>>>I'm away until next week, so can't test this out, but
>>>would the MakeMaker attribute FIRST_MAKEFILE be of any
>>>help here? That is, after generating the top-level
>>>Makefile, have Makefile.PL rename it to something
>>>else, and then use this name as a value to FIRST_MAKEFILE
>>>within WriteMakefile().
>>
>>Won't that intervene with the non-perl build, for users which aren't
>>interested in the perl glue. I suppose that if they don't run 'perl
>>Makefile.PL' it makes no difference to them.
>>
>> So if we say:
>>
>> FIRST_MAKEFILE => Makefile.mod_perl
>>
>>the top-level Makefile could include:
>>
>>dist :
>> make -f Makefile.mod_perl dist
>>
>>but it's probably too messy to have two Makefiles. Is there a way we can
>>generate Makefile normally via MakeMaker and then somehow integrate the
>>autoconf's stuff in? Or the other way around?
>
>
> You're right that it will become messy to have two Makefiles ...
> As far as trying to integrate things, perhaps one could
> let autoconf generate a Makefile, and then, within Makefile.PL,
> rename it to Makefile.auto, or something, and then in Makefile.PL
> add in something to
> include Makefile.auto
> in MakeMaker's generated Makefile? I guess this would also
> involve changing the default targets so as to include those
> of Makefile.auto. And since it's done within Makefile.PL,
> it would only affect those users wishing to use the perl glue.
I don't think this will quite work as most variables will get duplicated. we
could probably start with just providing a dist target for the top level
Makefile that will call the perl's generated Makefile.
> Another possibility, which though would add a perl dependency,
> is to use Module::Build rather than MakeMaker, and then add
> in the autoconf Makefile targets into Module::Build.
That's not an option untill we get mp2 support M::B. Currently one has to use
ModPerl::MM instead of ExtUtils::MakeMaker to get things right.
__________________________________________________________________
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
Re: simple apache 2 module using libapreq and mod_apreq
Posted by Randy Kobes <ra...@theoryx5.uwinnipeg.ca>.
On Tue, 5 Aug 2003, Stas Bekman wrote:
> Randy Kobes wrote:
> >
> > I'm away until next week, so can't test this out, but
> > would the MakeMaker attribute FIRST_MAKEFILE be of any
> > help here? That is, after generating the top-level
> > Makefile, have Makefile.PL rename it to something
> > else, and then use this name as a value to FIRST_MAKEFILE
> > within WriteMakefile().
>
> Won't that intervene with the non-perl build, for users which aren't
> interested in the perl glue. I suppose that if they don't run 'perl
> Makefile.PL' it makes no difference to them.
>
> So if we say:
>
> FIRST_MAKEFILE => Makefile.mod_perl
>
> the top-level Makefile could include:
>
> dist :
> make -f Makefile.mod_perl dist
>
> but it's probably too messy to have two Makefiles. Is there a way we can
> generate Makefile normally via MakeMaker and then somehow integrate the
> autoconf's stuff in? Or the other way around?
You're right that it will become messy to have two Makefiles ...
As far as trying to integrate things, perhaps one could
let autoconf generate a Makefile, and then, within Makefile.PL,
rename it to Makefile.auto, or something, and then in Makefile.PL
add in something to
include Makefile.auto
in MakeMaker's generated Makefile? I guess this would also
involve changing the default targets so as to include those
of Makefile.auto. And since it's done within Makefile.PL,
it would only affect those users wishing to use the perl glue.
Another possibility, which though would add a perl dependency,
is to use Module::Build rather than MakeMaker, and then add
in the autoconf Makefile targets into Module::Build.
--
best regards,
randy
Re: simple apache 2 module using libapreq and mod_apreq
Posted by Stas Bekman <st...@stason.org>.
Randy Kobes wrote:
> On Tue, 5 Aug 2003, Stas Bekman wrote:
>
> [ .. ]
>
>>I think httpd-apreq-2 is a fine dist directory name. e.g. LWP builds in
>>libwww-perl. All is needed is to add a 'make dist' target which will
>>name the distribution as Apache-Request-2.x.tar.gz. Unfortunately we
>>can't rely on ExtUtils::MakeMaker::WriteMakefile here, since we already
>>have a top-level Makefile generated by autoconf.
>>
>>Otherwise useing DISTVNAME and DISTNAME targets could handle that in a
>>simple way.
>
>
> I'm away until next week, so can't test this out, but
> would the MakeMaker attribute FIRST_MAKEFILE be of any
> help here? That is, after generating the top-level
> Makefile, have Makefile.PL rename it to something
> else, and then use this name as a value to FIRST_MAKEFILE
> within WriteMakefile().
Won't that intervene with the non-perl build, for users which aren't
interested in the perl glue. I suppose that if they don't run 'perl
Makefile.PL' it makes no difference to them.
So if we say:
FIRST_MAKEFILE => Makefile.mod_perl
the top-level Makefile could include:
dist :
make -f Makefile.mod_perl dist
but it's probably too messy to have two Makefiles. Is there a way we can
generate Makefile normally via MakeMaker and then somehow integrate the
autoconf's stuff in? Or the other way around?
__________________________________________________________________
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
Re: simple apache 2 module using libapreq and mod_apreq
Posted by Randy Kobes <ra...@theoryx5.uwinnipeg.ca>.
On Tue, 5 Aug 2003, Stas Bekman wrote:
[ .. ]
> I think httpd-apreq-2 is a fine dist directory name. e.g. LWP builds in
> libwww-perl. All is needed is to add a 'make dist' target which will
> name the distribution as Apache-Request-2.x.tar.gz. Unfortunately we
> can't rely on ExtUtils::MakeMaker::WriteMakefile here, since we already
> have a top-level Makefile generated by autoconf.
>
> Otherwise useing DISTVNAME and DISTNAME targets could handle that in a
> simple way.
I'm away until next week, so can't test this out, but
would the MakeMaker attribute FIRST_MAKEFILE be of any
help here? That is, after generating the top-level
Makefile, have Makefile.PL rename it to something
else, and then use this name as a value to FIRST_MAKEFILE
within WriteMakefile().
--
best regards,
randy
Re: simple apache 2 module using libapreq and mod_apreq
Posted by Stas Bekman <st...@stason.org>.
Joe Schaefer wrote:
> Hal Robertson <ha...@yahoo.com> writes:
>
>
>>Hello,
>>
>>I am new to this list. I have just downloaded version
>>2 of the library and am very happy to be working with
>>it.
>
>
> Great!
>
>
>>I would like to know how far away an initial release
>>might be?
>
>
> The STATUS file should list the remaining issues.
>
> As far as the code itself goes, AFAICT it's releasable
> right now. However, the perldocs and the build system
> (especially the dependence on 'httpd-apreq-2' being the
> base directory) need more work before a release should
> go out.
I think httpd-apreq-2 is a fine dist directory name. e.g. LWP builds in
libwww-perl.
All is needed is to add a 'make dist' target which will name the distribution
as Apache-Request-2.x.tar.gz. Unfortunately we can't rely on
ExtUtils::MakeMaker::WriteMakefile here, since we already have a top-level
Makefile generated by autoconf.
Otherwise useing DISTVNAME and DISTNAME targets could handle that in a simple way.
__________________________________________________________________
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
Re: simple apache 2 module using libapreq and mod_apreq
Posted by Joe Schaefer <jo...@sunstarsys.com>.
Hal Robertson <ha...@yahoo.com> writes:
> Hello,
>
> I am new to this list. I have just downloaded version
> 2 of the library and am very happy to be working with
> it.
Great!
> I would like to know how far away an initial release
> might be?
The STATUS file should list the remaining issues.
As far as the code itself goes, AFAICT it's releasable
right now. However, the perldocs and the build system
(especially the dependence on 'httpd-apreq-2' being the
base directory) need more work before a release should
go out.
--
Joe Schaefer