From: "Robert Collins" <robert.collins@itdomain.com.au>
To: <dhorne@xtra.co.nz>, "Gerrit P. Haase @ cygwin" <cygwin@cygwin.com>
Subject: Re: Anyone got mod_perl working?
Date: Fri, 04 Jan 2002 19:39:00 -0000 [thread overview]
Message-ID: <105e01c1959a$47097970$0200a8c0@lifelesswks> (raw)
In-Reply-To: <BLEDKFLJDLPNJONGFLHNMELIBPAB.dhorne@xtra.co.nz>
----- Original Message -----
From: "Dan Horne" <dhorne@xtra.co.nz>
>
> "However, I think that building mod_perl under Cygwin is a not a good
> idea (yet). For example, you won't be able to build libapreq
> (Apache::Request):
> it requires some symbols from apache and under win32 it's impossible
> to link .dll to symbols in .exe which loads this .dll.
> That's why win32 apache is split into Apache.exe and ApacheCore.dll --
> it allows modules to link with ApacheCore.dll. Unfortunately,
> Cygwin builds single httpd.exe binary and libapreq fails to link
> to ap_table_add, ap_getword and many other symbols residing in apache
> binary."
>
> If you have any other ideas, please let me know :)
A .exe is the same as a .dll to Win32. You should be able to link back
to the .exe, if you generate an import library for the exported symbols.
Rob
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
next prev parent reply other threads:[~2002-01-05 3:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-01 23:57 Dan Horne
2002-01-02 5:17 ` Stipe Tolj
2002-01-02 8:32 ` Gerrit P. Haase
2002-01-02 14:07 ` Dan Horne
2002-01-04 8:31 ` Gerrit P. Haase
2002-01-04 18:36 ` Dan Horne
2002-01-04 19:39 ` Robert Collins [this message]
2002-01-05 3:35 ` Gerrit P. Haase
2002-01-09 9:20 ` Recurring message? " Eric M. Monsler
2002-01-09 10:12 ` Gerrit P. Haase
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='105e01c1959a$47097970$0200a8c0@lifelesswks' \
--to=robert.collins@itdomain.com.au \
--cc=cygwin@cygwin.com \
--cc=dhorne@xtra.co.nz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).