lynx-dev
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: LYNX-DEV SSL Patch problem


From: Klaus Weide
Subject: Re: LYNX-DEV SSL Patch problem
Date: Wed, 30 Oct 1996 22:36:55 -0600 (CST)

On Wed, 30 Oct 1996, Chad Simmons wrote:

> I did what he said and sslref's makefile auto compiles the des libs, but
> now I get
> make[1]: Entering directory `/home/chads/sslref2.0/libdes-3.0'
> cc  -O2      -c read_pwd.c -o read_pwd.o
> read_pwd.c:17: parse error before string constant
> In file included from /usr/include/asm/termios.h:4,
>                  from /usr/include/linux/termios.h:5,
>                  from /usr/include/termios.h:28,
>                  from /usr/include/sys/ioctl.h:6,
>                  from read_pwd.c:19:
> /usr/include/asm/termbits.h:16: parse error before `cc_t'
> /usr/include/asm/termbits.h:16: warning: no semicolon at end of struct or
> union
> /usr/include/asm/termbits.h:17: warning: data definition has no type or
> storage
> class
> /usr/include/asm/termbits.h:18: parse error before `}'
> read_pwd.c: In function `read_pw':
> read_pwd.c:124: storage size of `tty_orig' isn't known
> read_pwd.c:124: storage size of `tty_new' isn't known
> make[1]: *** [read_pwd.o] Error 1
> make[1]: Leaving directory `/home/chads/sslref2.0/libdes-3.0'
> make: *** [libdes-3.0/libdes.a] Error 2
> This is the most annoying thing to compile.

So what does the beginning of /usr/include/asm/termbits.h (first 20 lines)
look like?

Maybe you have got the SIG11 problem.. There is a whole FAQ on it at

   Linkname: The SIG11 problem
        URL: http://www.bitwizard.nl/sig11/

and I can confirm that it is real.  _IF_ that's your problem, your 
best immediate solution is just retry the compilation several times...
if you get *different* error messages on subsequent attempts, you
definitely have a problem..

  Klaus

;
; To UNSUBSCRIBE:  Send a mail message to address@hidden
;                  with "unsubscribe lynx-dev" (without the
;                  quotation marks) on a line by itself.
;



reply via email to

[Prev in Thread] Current Thread [Next in Thread]