Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Message-ID: <105e01c1959a$47097970$0200a8c0@lifelesswks> From: "Robert Collins" To: , "Gerrit P. Haase @ cygwin" References: Subject: Re: Anyone got mod_perl working? Date: Sat, 5 Jan 2002 14:37:17 +1100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-OriginalArrivalTime: 05 Jan 2002 03:39:21.0032 (UTC) FILETIME=[8FA19C80:01C1959A] ----- Original Message ----- From: "Dan Horne" > > "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/