[net.sources.bugs] Unresolved lables in Emacs 3.8b

mark@cogent.UUCP (Captain Neptune) (03/19/87)

Upon compiling emacs 3.8b under HP-UX, which seems to be a pretty good
Sys5 port, I get the following unresolved symbols:

/bin/ld: Unsatisfied symbols:
   sysint (code)
   mlreplyt (code)
   get1key (code)
   scwrite (code)
   ctoec (code)
   tgetc (code)
   agetc (code)
   mlreply (code)
   getname (code)
   term (data)
   mlyesno (code)
   ectoc (code)
   getstring (code)
   aputc (code)
   getcmd (code)

Would these be BSD calls?  Would I have suitable substitutes under Sys5?
Help would be appreciated.  Thanks in advance.
-- 
+----------------------------------------------------------------------------+
|     Mark Steven Jeghers         ECHOMPGULP - process has eaten it          |
| cryptography, terrorist, DES, drugs, cipher, secret, decode, NSA, CIA, NRO |
|                                                                            |
|     {ihnp4,cbosgd,lll-lcc,lll-crg}|{dual,ptsfa}!cogent!mark                |
|                                                                            |
| Cogent Software Solutions can not be held responsible for anything said    |
| by the above person since they have no control over him in the first place |
+----------------------------------------------------------------------------+

jsa@tut.UUCP (03/20/87)

in article <179@cogent.UUCP>, mark@cogent.UUCP (Captain Neptune) says:
> 
> Upon compiling emacs 3.8b under HP-UX, which seems to be a pretty good
> Sys5 port, I get the following unresolved symbols:
> 
> /bin/ld: Unsatisfied symbols:
>    sysint (code)    mlreplyt (code)
>    get1key (code)   scwrite (code)
>    ctoec (code)     tgetc (code)
>    agetc (code)     mlreply (code)
>    getname (code)   term (data)
>    mlyesno (code)   ectoc (code)
>    getstring (code) aputc (code)
>    getcmd (code)
> 
> Would these be BSD calls?  Would I have suitable substitutes under Sys5?
> Help would be appreciated.  Thanks in advance.

	The above mentioned are NOT any specific BSD -calls.

	You can fix this by adding input.c to your Makefile.
	It seemed to be missing from there, and all the functions
	above are in input.c .


	Then an other thing :

		I am currently using IBM PC/AT with MicroPort's
		UNIX System V release 2.

		I did compile uEmacs allright. But it seems that
		the console key mappings don't work. All I can
		get out of the arrow-keys is h's l's j's and k's
		as if the console was ment to be used ONLY with vi !!

		The keyset command does not allow the keypad keys
		to be configured again.

		Does anyone happen to know how to make uEmacs work
		right in this case ???

-- 
Jari Salo             Tampere University of Technology / Computer Syst Lab
UUCP: mcvax!tut!jsa   PO box 527   SF-33101 Tampere
:All rights reversed. This message may be reproduced, stored in a retrieval
:system or transmitted further without the prior permission of the author.

leonard@acf4.UUCP (03/26/87)

I'm running V5 R2.0.4 on a 3b2... 
I just installed MicroEmacs 3.8b and I had to modify the makefile to load
the curses library, since no termcap library comes with this release.
Also turned off COLOR, AZTEC and all Terminal output definintions,
except TERMCAP in 'estruct.h.'

Shanna Leonard
ARRPA:leonard@acf4.nyu.edu