Re: Tru64 5.1 and unresolved externals when building modules

[Peter Stephenson <pws@xxxxxxx>]

On Tue, 13 Nov 2007 21:15:00 -0500
"Thomas Pfau" <tfpfau@xxxxxxxxx> wrote:
> 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.

Thanks for looking further.  The shell doesn't currently attempt to
sanitize the symbols against shared libraries (when writing code you
sometimes only find there's a problem when a module load fails and
crashes the shell).  So adding the option is probably the right thing to do.
I'm not sure how to test; probably adding it for Tru64 alone would be OK.
It's not clear from config.guess what $host value configure sets, however.
I might get a chance to check tomorrow night.

pws