From: Oliver Kiddle <opk@u.genie.co.uk>
To: The Corridor <dfavor@corridor.com>
Cc: zsh@corridor.com
Subject: Re: How-to AIX + dynamic zsh?
Date: Thu, 06 Apr 2000 12:46:53 +0100 [thread overview]
Message-ID: <38EC792D.6AFD430A@u.genie.co.uk> (raw)
In-Reply-To: <200004061122.FAA18235@corridor.com>
The Corridor wrote:
>
> If someone has any of these working on AIX:
> - dynamically loadable modules
> - shared library for zsh itself
> email me directions of how you got it to work.
I have exactly that working and I haven't needed to do anything
particularly special to achieve it.
I have the following set in my .zshenv although you really shouldn't
need them.
export CC="/bin/cc"
export CFLAGS="-O2"
export LDFLAGS="-s"
If you are running csh or tcsh to build zsh, you will need to type
something like setenv CC "/bin/cc"
Unpack the zsh source and run configure. I tend to use a couple of
parameters like --enable-functions-subdirs and
--enable-etcdir=/usr/local/etc but these shouldn't make a difference.
When configure has finished, run make.
Which version of zsh are you trying to build? Exactly what errors or
problems do you come up against - with details of that I can probably
work out what the problem is? If you are compiling 3.1.6-dev-21, you
will need my small patch to utils.c which was in message #10519. All it
does is add mod_export to to the definition of utils.c - AIX needs an
explicit list of all symbols shared between separate shared libraries.
Oliver Kiddle
next prev parent reply other threads:[~2000-04-06 11:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-04-06 11:22 The Corridor
2000-04-06 11:46 ` Oliver Kiddle [this message]
[not found] ` <38EC9FF3.B12EE9BE@austin.ibm.com>
[not found] ` <38ECA546.107A6D91@u.genie.co.uk>
[not found] ` <38ECAE56.97D758B3@austin.ibm.com>
2000-04-07 12:23 ` Oliver Kiddle
[not found] ` <38EE00D8.82FE48C@austin.ibm.com>
2000-04-07 16:11 ` Oliver Kiddle
2000-04-06 12:56 The Corridor
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=38EC792D.6AFD430A@u.genie.co.uk \
--to=opk@u.genie.co.uk \
--cc=dfavor@corridor.com \
--cc=zsh@corridor.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.
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).