Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
X-SBRSScore:	None
X-IronPort-AV:	i="3.95,166,1120428000"; d="scan'208"; a="12128418:sNHT26945008"
To:	"Gerrit P. Haase" <gerrit AT familiehaase DOT de>
Cc:	cygwin AT cygwin DOT com
Subject:	Re: error compiling apache-1.3.33 with mod_perl and perl-5.8.7-1
From:	Harald Joerg <harald DOT joerg AT fujitsu-siemens DOT com>
In-Reply-To:	<42F0F80E.6060308@familiehaase.de> (Gerrit P. Haase's message of "Wed, 03 Aug 2005 18:59:58 +0200")
References:	<42D0178C DOT 6070803 AT familiehaase DOT de> <20050709131329 DOT GC3284 AT postle DOT net> <kvacjzozk1 DOT fsf AT mcp0147c DOT mch DOT fsc DOT net> <42F0F80E DOT 6060308 AT familiehaase DOT de>
Date:	Thu, 04 Aug 2005 10:51:23 +0200
Message-ID:	<kvy87ixeyc.fsf@mcp0147c.mch.fsc.net>
User-Agent:	Gnus/5.1001 (Gnus v5.10.1) Emacs/21.2 (cygwin)
MIME-Version:	1.0
X-IsSubscribed:	yes

Gerrit P. Haase writes:

> [...]
>>>Bruno Postle wrote:
>> [...]
>>>>undefined reference to `_boot_'
>>> [...]
>>>Something broken with generating the code for perlxsi?
> [...]
>> If $static_ext was empty, it is now " Win32CORE", with a leading
>> space.
>> When building perlxsi.c, ExtUtils::Embed splits $static_ext, which
>> according to Perl's rules, creates two elements: '' and 'Win32CORE'.
>> The empty element creates a line in perlxsi.c which calls for 'boot_'.
>> Ouch.
>
> IMO a bug in ExtUtils::Embed.

I'd have said so - but this version of ExtUtils::Embed has been around
for a while.  That's why I have been looking for a solution - or a
workaround - within the cygwin build.

Nevertheless I'll try to file a bug report to perlbug.  Having
Extutils::Embed kill undefined static_ext elements doesn't harm and
makes the procedure more robust.

>> I don't know enough about building perl - especially I've no idea
>> whether the sequence of static_ext is of any importance.  Maybe the
>> following is a simple solution:
>> ===========================================================================
>> --- perl-5.8.6/hints/cygwin.sh.orig	2004-02-22 14:07:58.000000000 -0800
>> +++ perl-5.8.6/hints/cygwin.sh.haj	2004-12-08 20:52:01.891572800 -0800
>> @@ -57,3 +57,4 @@
>>  ldflags="$ldflags -s"
>>  ccdlflags="$ccdlflags -s"
>>  lddlflags="$lddlflags -s"
>> +static_ext="Win32CORE $static_ext"
>> --- perl-5.8.7/cygwin/cygwin.c.orig	2005-04-22 12:54:18.000000000
>> +0200
>> ===========================================================================
>
>
> Should do it.  I'll change it for future releases.

Great!  I prefer to run vanilla cygwin installations instead of my own
compilations - they tend to be more stable :-)

> [...]  Would mod_perl work with a mod_so setup as well?
>
> Yes it should work.  Have you tried to link directly against the DLL?

You mean against /usr/bin/libhttpd.dll?

I've tried, but failed miserably so far.  I've been starting with the
build procedure delivered with mod_perl (DO_HTTPD=1), which creates a
different Apache than what I get from cygwin's setup.  I have yet to
find out how cygwin's Apache has been built...
-- 
Cheers,
haj

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -