lynx-dev
[Top][All Lists]
Advanced

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

lynx-dev Errors during make on HPUX


From: Ovanes Manucharyan
Subject: lynx-dev Errors during make on HPUX
Date: Wed, 2 Dec 1998 21:21:13 -0800 (Pacific Standard Time)

Hi, I am compiling on HPUX 10.20 with gcc &
system default curses.

As far as I know, I haven't changed
anything too drastic in the userdefs.h
file, just some options.....

I get the following errors during make.


In file included from ./LYShowInfo.c:37:
../cfg_defs.h:117: `usr' undeclared (first use in this function)
../cfg_defs.h:117: (Each undeclared identifier is reported only once
../cfg_defs.h:117: for each function it appears in.)
../cfg_defs.h:117: `bin' undeclared (first use in this function)
../cfg_defs.h:117: `compress' undeclared (first use in this function)
../cfg_defs.h:117: initializer element for `config_defines[0].value' is not 
constant
../cfg_defs.h:117: parse error before string constant
../cfg_defs.h:119: parse error before `1'
../cfg_defs.h:150: parse error before `1'
../cfg_defs.h:155: `mv' undeclared (first use in this function)
../cfg_defs.h:155: initializer element for `config_defines[28].value' is not 
constant
../cfg_defs.h:155: parse error before string constant
../cfg_defs.h:163: parse error before `1'
../cfg_defs.h:166: `tar' undeclared (first use in this function)
../cfg_defs.h:166: initializer element for `config_defines[36].value' is not 
constant
../cfg_defs.h:166: parse error before string constant
../cfg_defs.h:169: `contrib' undeclared (first use in this function)
../cfg_defs.h:169: `gunzip' undeclared (first use in this function)
../cfg_defs.h:169: initializer element for `config_defines[38].value' is not 
constant
../cfg_defs.h:169: parse error before string constant
../cfg_defs.h:172: parse error before `1'
../cfg_defs.h:175: parse error before `zip'
make[1]: *** [LYShowInfo.o] Error 1
make[1]: Leaving directory `/usr/local/src/lynx/lynx2-8-1/src'
make: *** [all] Error 2


IS this a seriuous error, and if so how can I fix it.


Sincerely,

Ovanes




reply via email to

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