public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: <sisyphus1@optusnet.com.au>
To: <Ulrich.Herbst@t-systems.com>,	<cygwin@cygwin.com>
Subject: Re: WG: AW: Win32::Eventlog: Not found after upgrade
Date: Wed, 29 Jan 2014 11:58:00 -0000	[thread overview]
Message-ID: <D944D92855DC4144B4371A3109255C01@OwnerPC311012> (raw)
In-Reply-To: <634CFD657E419946BD70654E385A708F2491501B9A@HE111508.emea1.cds.t-internal.com>



-----Original Message----- 
From: Ulrich.Herbst

> 3. I don't want to build Win32::Eventlog on my own... for these reasons:
> - I had to do it on many systems...
> - We don't have compilers and make and tools... installed on them 
> (production environments)

Ok - alternatively it's only *2* files that need to be installed - 
Win32/EventLog.pm and auto/Win32/EventLog/EventLog.dll.
After you've manually built the module on your local machine, you'll find 
the former in blib/lib and the latter in blib/arch.
Assuming you're running the same version of perl across all systems, it's 
just a matter of installing those files into one of the @INC directories on 
all machines.
By convention, I think you'd install them into 
/usr/lib/perl5/site_perl/5.14 - so you'd end up with
/usr/lib/perl5/site_perl/5.14/Win32/EventLog.pm
and
/usr/lib/perl5/site_perl/5.14/auto/Win32/EventLog/EventLog.dll

If it's simple for you to effect that across the various systems, then you 
could go with that.

> So - will be in the near future a libwin32-version including 
> Win32::Eventlog running with Perl5.14 available from cygwin installer ?

I'm sort of thinking it should already be there. I'm running perl-5.14.2 on 
Cygwin-1.7.17, so I figured I'd test for myself ... alas, I can't find a 
mirror that can provide setup.ini, and setup.exe aborts at that point.
So I guess we wait for someone who *knows* to come along.

Btw, it would really help if, in your testing, you'd try to load 
Win32::EventLog instead of Win32::Eventlog. In some situations it probably 
doesn't matter, but testing the loading of "Win32::Eventlog" introduces an 
(unnecessary) uncertainty with which it would be better to go without.
The thing is that, although Windows is not case-sensitive, perl is - and 
failing to attend to case-sensitivity can lead to strange failures.

Cheers,
Rob


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

      reply	other threads:[~2014-01-29 11:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-29 10:51 Ulrich.Herbst
2014-01-29 11:58 ` sisyphus1 [this message]

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=D944D92855DC4144B4371A3109255C01@OwnerPC311012 \
    --to=sisyphus1@optusnet.com.au \
    --cc=Ulrich.Herbst@t-systems.com \
    --cc=cygwin@cygwin.com \
    /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).