zsh-workers
 help / color / mirror / code / Atom feed
From: Andrej Borsenkow <Andrej.Borsenkow@mow.siemens.ru>
To: Fletch <fletch@phydeaux.org>
Cc: <zsh-workers@sunsite.dk>
Subject: Re: Where to add extra libraries for modules
Date: Sun, 22 Jul 2001 09:08:25 +0400 (MSD)	[thread overview]
Message-ID: <Pine.SV4.4.33.0107220901140.13598-100000@itsrm2.mow.siemens.ru> (raw)
In-Reply-To: <m2y9phybno.fsf@freebie.phydeaux.org>

On 21 Jul 2001, Fletch wrote:

>
>
>         The problem is that the mkmakemod.sh script has already spit
> out a rule for `zperl.$(DL_EXT)'.  I realize that I could stick the
> ldopts invocation in DLLDFLAGS and/or LDFLAGS in the configure script,
> but then that'd be including them for every module.
>
>
>         Would it make sense (possibly) to add an `extralibs' paramter
> in the .mdd and then have mkmakemod.sh include that in the rule for
> module.$(DL_EXT)?
>

It would be trivial, but ...

on most systems perl lib is installed into own directory not in standard
libpath. That means that you have to link your program with some variant
of

LD_RUN_PATH=/usr/lib/perl/5.6.0/... $(LD) ... -L$... -lperl ...

Now, the problem is - I do now that it works when linking main program. I
do not know if it works when linking shared object.

Also, we have AIX and Cygwin. Cygwin may be easier because here libperl is
in PATH (I guess, nust check), but I suspect it won't work for AIX at all
(because we need list of symbols exported from libperl.so). Anybody knows
status of perl on AIX?

Note, that there is no prolem with static perl library.

-andrej


  reply	other threads:[~2001-07-22  5:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-22  1:50 Fletch
2001-07-22  5:08 ` Andrej Borsenkow [this message]
2001-07-22 15:43   ` Fletch
2001-07-23  4:32     ` Andrej Borsenkow
2001-07-23 16:31 ` Bart Schaefer
2001-07-30 15:25   ` Clint Adams

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=Pine.SV4.4.33.0107220901140.13598-100000@itsrm2.mow.siemens.ru \
    --to=andrej.borsenkow@mow.siemens.ru \
    --cc=fletch@phydeaux.org \
    --cc=zsh-workers@sunsite.dk \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

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 NNTP newsgroup(s).