[comp.sys.next] libX11 in MouseX package, compiling

squier@cs.Princeton.EDU (Richard Squier) (04/25/91)

I just installed MouseX on this '030 NeXT running 2.0.
But, when I try to compile an X application program,
I get unresolved references from calls in the libX11.a
library.  For instance,

	__XErrorFunction
	__XIOErrorFunction
	__Xdebug
	__XHeadOfDisplayList
	__qfree

are unresolved when a call to XOpenDisplay is in the
compiled program.
Any ideas on what the problem is?

	Richard Squier
	squier@princeton.edu
-- 

   | Richard Squier
   | squier@princeton.edu

wheelan@cs.mcgill.ca (Bill Heelan) (04/26/91)

From article <1991Apr25.015556.20481@newross.Princeton.EDU>, by squier@cs.Princeton.EDU (Richard Squier):
> I just installed MouseX on this '030 NeXT running 2.0.
> But, when I try to compile an X application program,
> I get unresolved references from calls in the libX11.a
> library.  For instance,
> 
> 	__XErrorFunction
> 	__XIOErrorFunction
> 	__Xdebug
> 	__XHeadOfDisplayList
> 	__qfree
> 
> are unresolved when a call to XOpenDisplay is in the
> compiled program.
> Any ideas on what the problem is?

   NeXT has changed 'ranlib' so that you must now use the '-c' option to
   get the standard behaviour.

                                                        - Bill