Re: APXS issue.

2007-07-22 Thread Mike
On Sat, Jul 21, 2007 at 06:32:09PM -0500, William A. Rowe, Jr. wrote: > You probably didn't ensure that the apache2 module structure to be declared > in a C namespace as an export. My mod_aspdotnet is one such example, He did. It's already declared as extern "C". Kind regards.

[EMAIL PROTECTED]: Re: Broken APXS]

2007-07-22 Thread Mike
- Forwarded message from Eric Covener <[EMAIL PROTECTED]> - On 7/22/07, Mike <[EMAIL PROTECTED]> wrote: > Greetings. > > apxs accepts only *.c files as its input. For other extensions it > doesn't invoke libtool in compile mode and several different issues > leading to empty Apache module

Re: APXS issue.

2007-07-22 Thread William A. Rowe, Jr.
Mike wrote: > On Sat, Jul 21, 2007 at 06:32:09PM -0500, William A. Rowe, Jr. wrote: >> You probably didn't ensure that the apache2 module structure to be declared >> in a C namespace as an export. My mod_aspdotnet is one such example, > He did. It's already declared as extern "C". Great! Wanted

APXS question

2007-07-22 Thread Farokh Irani
I'm trying to set up a makefile using apxs to compile and link a module and I'm running into a couple of problems. If I use the following command line: apxs -ic -S CC=g++ -n mod_fancy mod_fancy.cpp config.cpp everything works fine. In my makefile, I have the following (this is a partial): mod_

Re: APXS question

2007-07-22 Thread William A. Rowe, Jr.
Farokh Irani wrote: > apxs -i -n mod_fancy mod_fancy.o config.o You don't -i'nstall a .o file. It's not a loadable module. Loadable modules are the .so (.sl/.dll/.dylib) already-linked object files.

Re: APXS issue.

2007-07-22 Thread Ralf Mattes
On Sat, 2007-07-21 at 18:32 -0500, William A. Rowe, Jr. wrote: > Farokh Irani wrote: > >> On Wed, 2007-07-18 at 07:23 -0400, Farokh Irani wrote: > >> > >>> See any operating system documentation about shared libraries for > >>> more information, such as the ld(1) and ld.so(8) manual pages. > >>>

Re: APXS question

2007-07-22 Thread Ralf Mattes
On Sun, 2007-07-22 at 11:32 -0400, Farokh Irani wrote: > I'm trying to set up a makefile using apxs to compile and link a > module and I'm running into a couple of problems. > > If I use the following command line: > apxs -ic -S CC=g++ -n mod_fancy mod_fancy.cpp config.cpp > everything works fine

Re: APXS question

2007-07-22 Thread Farokh Irani
Farokh Irani wrote: apxs -i -n mod_fancy mod_fancy.o config.o You don't -i'nstall a .o file. It's not a loadable module. Loadable modules are the .so (.sl/.dll/.dylib) already-linked object files. I tried it with the .so files (apxs -i -n mod_fancy .libs/mod_fancy.so .libs/config.so) an

Re: APXS question

2007-07-22 Thread Farokh Irani
> I've tried it by using different files (ie .slo and .lo files), but I > get the same error. You want to installthe '*.so' file from the '.libs' directory. But be careful: that name depends on the platform. Tried that, and no go. > Any ideas? I'd really rather not have apxs recompiling ev

Re: APXS question

2007-07-22 Thread Graham Dumpleton
On 23/07/07, Farokh Irani <[EMAIL PROTECTED]> wrote: >Farokh Irani wrote: >>apxs -i -n mod_fancy mod_fancy.o config.o > >You don't -i'nstall a .o file. It's not a loadable module. > >Loadable modules are the .so (.sl/.dll/.dylib) already-linked object files. I tried it with the .so files (a

Re: APXS question

2007-07-22 Thread Graham Dumpleton
On 23/07/07, Graham Dumpleton <[EMAIL PROTECTED]> wrote: On 23/07/07, Farokh Irani <[EMAIL PROTECTED]> wrote: > >Farokh Irani wrote: > >>apxs -i -n mod_fancy mod_fancy.o config.o > > > >You don't -i'nstall a .o file. It's not a loadable module. > > > >Loadable modules are the .so (.sl/.dll/.

Re: APXS question

2007-07-22 Thread Graham Dumpleton
One final comment, the 'apxs' manual page provides a number of examples of using -i separate to compilation. For example: $ apxs -i -a mod_foo.la /path/to/instdso.sh mod_foo.la /path/to/apache/modules /path/to/libtool --mode=install cp mod_foo.la /path/to/apach

Re: APXS question

2007-07-22 Thread Eric Covener
On 7/22/07, Farokh Irani <[EMAIL PROTECTED]> wrote: /usr/local/apache2/bin/apxs -i -n mod_fancy .libs/mod_fancy.so .libs/config.so /usr/local/apache2/build/instdso.sh SH_LIBTOOL='/usr/local/apache2/build/libtool' .libs/mod_fancy.so /usr/local/apache2/modules /usr/local/apache2/build/libtool --mod

Re: APXS question

2007-07-22 Thread Farokh Irani
On 7/22/07, Farokh Irani <[EMAIL PROTECTED]> wrote: /usr/local/apache2/bin/apxs -i -n mod_fancy .libs/mod_fancy.so .libs/config.so /usr/local/apache2/build/instdso.sh SH_LIBTOOL='/usr/local/apache2/build/libtool' .libs/mod_fancy.so /usr/local/apache2/modules /usr/local/apache2/build/libtool --mo

Re: APXS question

2007-07-22 Thread Graham Dumpleton
On 23/07/07, Farokh Irani <[EMAIL PROTECTED]> wrote: >On 7/22/07, Farokh Irani <[EMAIL PROTECTED]> wrote: >>/usr/local/apache2/bin/apxs -i -n mod_fancy .libs/mod_fancy.so >>.libs/config.so >>/usr/local/apache2/build/instdso.sh >>SH_LIBTOOL='/usr/local/apache2/build/libtool' .libs/mod_fancy.so >>/