From: jarausch@igpm.rwth-aachen.de
To: Andrej.Borsenkow@mow.siemens.ru
Cc: zsh-workers@sunsite.dk
Subject: Re: propagate LDFLAGS to modules - howto?
Date: Tue, 10 Jul 2001 10:47:29 +0200 [thread overview]
Message-ID: <200107100847.KAA39683@numa1.igpm.rwth-aachen.de> (raw)
In-Reply-To: <Pine.SV4.4.33.0107092138000.12375-100000@itsrm2.mow.siemens.ru>
On 9 Jul, Andrej Borsenkow wrote:
> On Mon, 9 Jul 2001 jarausch@igpm.rwth-aachen.de wrote:
>
>> Hi,
>>
>> I've configured current zsh (on my IRIX-6.5 box) with
>> LDFLAGS='-s -L/usr/LOCAL/lib -rpath=/usr/LOCAL/lib'
>> since my libpcre.so is there.
>>
>> But when executing pcregrep (having loaded it before
>> without any error message)
>> I get an rld error showing that /usr/LOCAL/lib
>> is not in the list of searched directories.
>>
>> How can I pass this information to the Makefile
>> building libpcre ?
>>
>
> DLLDFLAGFS=...
probably that's DLLDFLAGS=
Now I've rebuilt zsh and
ldd pcre.so correctly gives
libpcre.so.1 => /usr/LOCAL/lib/libpcre.so.1
and ls -l /usr/LOCAL/lib/libpcre.so.1* gives
lrwxr-xr-x 1 root sys 14 Jul 4 10:52 /usr/LOCAL/lib/libpcre.so.1 -> libpcre.so.1.1
-rw-r--r-- 1 root sys 85136 Jul 4 10:52 /usr/LOCAL/lib/libpcre.so.1.1
but now
zmodload pcre
gives
zsh: failed to load module: pcre
So how to find out the reason?
Therefore a plea for a new feature
Could zmodload take a '-v' option and show
where it tries to load from and some more detail of
the reason it failed?
Thanks,
Helmut Jarausch
Lehrstuhl fuer Numerische Mathematik
Institute of Technology, RWTH Aachen
D 52056 Aachen, Germany
next prev parent reply other threads:[~2001-07-10 8:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-09 8:29 jarausch
2001-07-09 17:39 ` Andrej Borsenkow
2001-07-10 8:47 ` jarausch [this message]
2001-07-10 9:11 ` Bart Schaefer
2001-07-10 9:25 ` jarausch
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=200107100847.KAA39683@numa1.igpm.rwth-aachen.de \
--to=jarausch@igpm.rwth-aachen.de \
--cc=Andrej.Borsenkow@mow.siemens.ru \
--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).