Zsh Mailing List Archive
Messages sorted by: Reverse Date, Date, Thread, Author

Re: Tru64 5.1 and unresolved externals when building modules

I noticed the 'test' target in the makefile and invoked it.  All test
seem to run successfully so I tried installing it.  It appears to be
working OK.  I just thought something was broken when it complained
about all of those unresolved symbols.

The man page for ld mentions "-expect_unresolved <pattern>" which
turns off the error messages for any unresolved symbols matching the
specified shell pattern.  I added "-expect_unresolved '*'" to
DLLDFLAGS and it builds quietly.

On Nov 13, 2007 7:25 AM, Peter Stephenson <pws@xxxxxxx> wrote:
> "Thomas Pfau" wrote:
> > I'm trying to build zsh on Tru64 5.1 but can't seem to get the modules
> > to build.  I've tried the standard cc, sed, and awk and also the gnu
> > versions of each with the same results.  For each module it attempts
> > to build, it displays 'Warning: Unresolved:' followed by a list of
> > symbols that appear to be from the main zsh executable.  This happens
> > with both zsh 4.3.2 and 4.3.4.
> I haven't heard this one before, and without access to the system
> there's not a lot that can be done.  You could try statically linking
> (configure --disable-dynamic), in which case make sure you edit
> config.modules to mark any modules you use as statically loaded.
> If it's only a few of the symbols from the main executable it might be
> they aren't correctly marked for export, however I thought I'd tested
> that for 4.3.4 and there shouldn't be more than a few at most in any
> case.  I will certainly make sure I test this for 4.3.5.
> --
> Peter Stephenson <pws@xxxxxxx>                  Software Engineer
> CSR PLC, Churchill House, Cambridge Business Park, Cowley Road
> Cambridge, CB4 0WZ, UK                          Tel: +44 (0)1223 692070


Messages sorted by: Reverse Date, Date, Thread, Author