zsh-workers
 help / color / mirror / code / Atom feed
From: Anthony Heading <aheading@jpmorgan.com>
To: zsh-workers@sunsite.dk
Subject: dynamic modules without libzsh.so?
Date: Mon, 22 Aug 2005 20:01:41 -0400	[thread overview]
Message-ID: <20050823000141.GA21090@bretton.ny.jpmorgan.com> (raw)


Hi,

How does one build the core zsh statically (i.e. with
builtin.o etc as part of the main executable, not in
libzsh-4.2.5.so), while still having zle and zftp
and so on created as loadable modules?

None of the configure invocations I've tried seem
to work, and while config.modules has link=static for
zsh/main that doesn't seem to stop libzsh-($VERSION).so
being built, since this seems to be controlled by
the expansion of Src/Makefile.in.

FWIW, the reason I want to do this is to have a
moveable zsh binary which is not dependent on an
embedded RPATH to the shared lib (and this is on
Solaris 8 where $ORIGIN support is broken).

Thanks

Anthony

PS.  On Solaris with gcc 4 (and I think earlier)
dynamic modules get disabled by default - it's
necessary to set DLLDFLAGS=-shared to override
a default setting of '-G' which doesn't work

This communication is for informational purposes only. It is not intended
as an offer or solicitation for the purchase or sale of any financial
instrument or as an official confirmation of any transaction. All market prices,
data and other information are not warranted as to completeness or accuracy and
are subject to change without notice. Any comments or statements made herein 
do not necessarily reflect those of JPMorgan Chase & Co., its subsidiaries 
and affiliates.


             reply	other threads:[~2005-08-23  0:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-23  0:01 Anthony Heading [this message]
2005-08-23  2:52 ` Bart Schaefer
2005-08-23  3:27   ` Anthony Heading

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=20050823000141.GA21090@bretton.ny.jpmorgan.com \
    --to=aheading@jpmorgan.com \
    --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).