From: Paul Ackersviller <pda@sdf.lonestar.org>
To: zsh-workers@sunsite.dk
Subject: Re: Modules on HP-UX
Date: Fri, 8 May 2009 18:42:56 +0000 [thread overview]
Message-ID: <20090508184256.GB13920@svalbard> (raw)
In-Reply-To: <090507163027.ZM15925@torch.brasslantern.com>
On Thu, May 07, 2009 at 04:30:27PM -0700, Bart Schaefer wrote:
> On May 7, 10:08pm, Paul Ackersviller wrote:
> } Subject: Re: D07multibyte.ztst failure on HP-UX 11.11
> }
> } BTW, there's one other thing with HP-UX tests I've been ignoring until
> } now, but would like to look at shortly. They end with:
> } rm: cannot remove `Modules/zsh/parameter.so': Text file busy
> } rm: cannot remove `Modules/zsh/zutil.so': Text file busy
> } rm: cannot remove `Modules/zsh/complete.so': Text file busy
> } rm: cannot remove `Modules/zsh/complist.so': Text file busy
> } rm: cannot remove `Modules/zsh/computil.so': Text file busy
> } rm: cannot remove `Modules/zsh/zle.so': Text file busy
>
> The test script creates a shadow directory with copies of all the
> shared objects so that it has a stable module_path for zmodload.
> HP-UX does paging for shared objects directly out of their files,
> so those files can't be removed while loaded by an application.
>
> It might work to "zmodload -u" the modules before "rm"ing the files.
I tried this on two of the lesser-used modules, namely complist and
zutil, but it made no difference. It's possible I put the "zmodload
-u" too early, but I can't see a better place than the end of the tests
that do the loading. I see no problems running zmodload interactively.
P.S. A tiny documentation nit -- zmodload says modules are usually call
.sl on HPUX, which is true, however the HP build names them .so's anyway.
next prev parent reply other threads:[~2009-05-08 18:43 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-27 3:17 D07multibyte.ztst failure on HP-UX 11.11 Paul Ackersviller
2009-04-27 4:42 ` Andrey Borzenkov
2009-04-27 19:26 ` Paul Ackersviller
2009-04-28 8:48 ` Peter Stephenson
2009-04-28 19:19 ` Paul Ackersviller
2009-04-28 19:48 ` Peter Stephenson
2009-04-30 3:01 ` Paul Ackersviller
2009-04-30 8:41 ` Peter Stephenson
2009-04-30 15:58 ` Paul Ackersviller
2009-04-30 16:03 ` Peter Stephenson
2009-05-01 14:52 ` Paul Ackersviller
2009-05-01 15:18 ` Peter Stephenson
2009-05-05 19:39 ` Paul Ackersviller
2009-05-06 19:22 ` Peter Stephenson
2009-05-06 21:50 ` Paul Ackersviller
2009-05-07 15:38 ` Peter Stephenson
2009-05-07 16:02 ` Peter Stephenson
2009-05-07 22:08 ` Paul Ackersviller
2009-05-07 23:30 ` Modules on HP-UX (Re: D07multibyte.ztst failure on HP-UX 11.11) Bart Schaefer
2009-05-08 8:34 ` Peter Stephenson
2009-05-08 14:20 ` Bart Schaefer
2009-05-08 14:29 ` Peter Stephenson
[not found] ` <090508084125.ZM17697@torch.brasslantern.com>
2009-05-11 8:52 ` Peter Stephenson
2009-05-08 18:42 ` Paul Ackersviller [this message]
2009-05-12 20:22 ` Modules on HP-UX, with small PATCH Paul Ackersviller
2009-05-08 14:23 ` D07multibyte.ztst failure on HP-UX 11.11 Peter Stephenson
2009-05-02 1:00 ` Phil Pennock
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=20090508184256.GB13920@svalbard \
--to=pda@sdf.lonestar.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).