From: "Yaakov (Cygwin/X)" <yselkowitz@users.sourceforge.net>
To: cygwin <cygwin@cygwin.com>
Subject: Re: cygport (0.11.0): Installing dll's into perl site directories (not /usr/bin)
Date: Tue, 04 Sep 2012 01:27:00 -0000 [thread overview]
Message-ID: <1346722038.6024.28.camel@YAAKOV04> (raw)
In-Reply-To: <7D847B86-17E1-430E-8482-9CDB7DE61140@mac.com>
http://cygwin.com/acronyms/#PCYMTWLL !
On Tue, 2012-09-04 at 10:21 +1000, Mark O'Keefe wrote:
> I'm trying to use cygport to package up DLL's that are used as part
> of a set of perl packages.
Being vague doesn't help us help you. Telling us what package you're
trying to build, and attaching your (draft) .cygport files, does.
> The place that these are meant to be installed is under the perl site
> configuration (/usr/lib/perl5/site_perl/<version>/auto/<package>/<subpackage>/*.dll.
Cygwin packages should install Perl modules into vendor_perl
(PERL_VENDORLIB and PERL_VENDORARCH in cygport terms).
> Currently what happens is libtool munges the path to ../bin. If I
> don't use cygport to do the installation, this means that the DLL's
> are installed into: /usr/lib/perl5/site_perl/<version>/auto/<package>/bin
> This doesn't work as this location is not in the search path for
> perl's DynaLoader.
>
> When you add cygport to the equation the files end up in: /usr/bin
> Again, this doesn't work as this isn't in the load path.
This means "-module" is missing from the *_la_LDFLAGS for these
module(s). You'll need to patch the affected Makefile.am file(s) and
restart the build to fix this.
Yaakov
--
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
next prev parent reply other threads:[~2012-09-04 1:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-04 0:22 Mark O'Keefe
2012-09-04 1:27 ` Yaakov (Cygwin/X) [this message]
2012-09-04 6:55 ` Mark O'Keefe
2012-09-04 7:12 ` Yaakov (Cygwin/X)
2012-09-04 14:07 ` Mark O'Keefe
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=1346722038.6024.28.camel@YAAKOV04 \
--to=yselkowitz@users.sourceforge.net \
--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).