From: Oliver Kiddle <opk@u.genie.co.uk>
To: The Corridor <dfavor@corridor.com>
Cc: zsh-workers@sunsite.auc.dk
Subject: Re: AIX - getting dynamic modules working
Date: Mon, 03 Apr 2000 12:51:57 +0100 [thread overview]
Message-ID: <38E885DD.EE18A598@u.genie.co.uk> (raw)
In-Reply-To: <200003311927.MAA11630@corridor.com>
The Corridor wrote:
> 1) I've tried setting $LDFLAGS in the environment and
> running configure, but $LDFLAGS does not make it into
> the Makefile(s).
Are you sure that you exported LDFLAGS. Try:
export LDFLAGS=whatever
This works fine for me (on AIX).
What do you actually want to put in the LDFLAGS. I use a dynamic zsh on
AIX and have never had any problems compiling it that relate to compiler
options.
> Let me know the best way to pass in linker commands
> to configure.
One of the best ways if you are generally using the same options is to
create a config.site shell script. This gets run by configure everytime
so lets you setup common variables. I also use it so that I keep a
single configure cache which speeds things up a lot. See the autoconf
manuals for more details.
> 2) Has anyone tried to change the zsh makefiles to use
> libtool. If so, send me your makefiles, as this is
> probably a better place to start.
Not that I know of and I really hope nobody does. Admittedly I haven't
looked at libtool for a few versions but the last time I did, there was
a lot that I didn't like. It seems to be primarily concerned with
allowing you to handle shared and static libraries interchangeably which
is something which I've never found to be a problem anyway. There no
attempt to use any kernel supported shared object versioning systems
used by OS's such as IRIX but it has it's own version system which
relies on a mess of symbolic links and which is fairly useless without
kernel support. It seemed to slightly miss what I considered to be the
main potential use of it - platform independence for software using
DSOs.
Oliver Kiddle
prev parent reply other threads:[~2000-04-03 11:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-03-31 19:27 The Corridor
2000-04-03 11:51 ` Oliver Kiddle [this message]
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=38E885DD.EE18A598@u.genie.co.uk \
--to=opk@u.genie.co.uk \
--cc=dfavor@corridor.com \
--cc=zsh-workers@sunsite.auc.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).