Re: Eximon on SunOS/OpenWindows

Página superior
Eliminar este mensaje
Responder a este mensaje
Autor: Nigel Metheringham
Fecha:  
A: Richard Gilbert
Cc: exim-users, Ian OSullivan
Asunto: Re: Eximon on SunOS/OpenWindows

} But there are also libXmu.sa and libXmu.so which are searched in
} preference to the static library, libXmu.a.  Interestingly, libXmu.sa only
} contains the sharedlib.o module: 
} 
} mbone{exim}: nm libXmu.sa
}  
} sharedlib.o:
}          U _applicationShellWidgetClass
} 00000000 T _get_applicationShellWidgetClass
} 0000000c T _get_wmShellWidgetClass
}          U _wmShellWidgetClass
} 
} All the rest of the library is in libXmu.so.  (This is probably obvious to
} people who understand shared libraries.)  But this doesn't explain why the
} symbols remain undefined. 


The .so file contains the code. The .sa file contains initialised data,
which might not be shareable between invocations. Many libraries have no
.sa file, and those that do will have a (small) subset of the data within
them.

} Anyway, to cut a long story short, I created a symbolic link in
} /usr/openwin/lib to libXmu.a called libXmu_static.a and searched this as
} an extra library (along with the math library which was also necessary) by
} adding:
}
} EXTRALIBS_EXIMON=-lXmu_static -lm

You could have changed that to

    EXTRALIBS_EXIMON=/usr/openwin/lib/libXmu.a -lm


and not played with the links.


I'd check that your libXmu shared bits are intact - each of the .so/.sa
files should be a symlink to a .s?.ver.num file where ver num are digits
corresponding to the major and minor version numbers. The version numbers
of both bits should be the same.

    Nigel.
-- 
[ Nigel.Metheringham@???   -  Systems Software Engineer ]
[ Tel : +44 113 251 6012                   Fax : +44 113 224 0003 ]
[            Friends don't let friends use sendmail!              ]