Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: AIX compile problem (Re: 3.1.6-bart-7)
- X-seq: zsh-workers 8331
- From: Sven Wischnowsky <wischnow@xxxxxxxxxxxxxxxxxxxxxxx>
- To: zsh-workers@xxxxxxxxxxxxxx
- Subject: Re: AIX compile problem (Re: 3.1.6-bart-7)
- Date: Tue, 19 Oct 1999 08:27:52 +0200 (MET DST)
- In-reply-to: "Bart Schaefer"'s message of Tue, 19 Oct 1999 04:40:29 +0000
- Mailing-list: contact zsh-workers-help@xxxxxxxxxxxxxx; run by ezmlm
Bart Schaefer wrote:
> On Oct 18, 4:42pm, Oliver Kiddle wrote:
>
> } I needed the following patch in order to successfully compile on AIX
> } 3.2.5. I'm not totally sure that this is the correct fix but the
> } .export files don't seem to be auto-generated anywhere
First of all: my fault, sorry, I constantly forget about those files.
> No, the .export files are an undocumented bit of module-ness: If a
> module defines any C symbols (except those for normal autoloading) that
> other modules might need to see, those have to be listed in the .export
> for a certain class of dynamic loading schemes; that file is passed to
> the $(DLLINK) program when building the shared object.
>
> If anyone remembers the exact details, please add something about it to
> Etc/zsh-development-guide. Perhaps it *could* be auto-generated using
> a variant of the makepro.awk script?
Yes, please. Has anyone tried what happens if we just stuff all
symbols we collect in the `*.pro' files there? (And what are those
files needed for anyway?)
Bye
Sven
--
Sven Wischnowsky wischnow@xxxxxxxxxxxxxxxxxxxxxxx
Messages sorted by:
Reverse Date,
Date,
Thread,
Author