[Top][All Lists]

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

Re: lynx-dev UTF-8 display questions (was: Superscripts)

From: Sergei Pokrovsky
Subject: Re: lynx-dev UTF-8 display questions (was: Superscripts)
Date: 09 Jun 2000 19:08:08 +0700
User-agent: Gnus/5.0807 (Gnus v5.8.7) Emacs/20.6

>>>>> Thomas E Dickey writes:

  Thomas> On Thu, 8 Jun 2000, Klaus Weide wrote:
  >> On 8 Jun 2000, Sergei Pokrovsky wrote: > I really had install
  >> fresh ncurses and xterm; but lynx didn't want > to compile with
  >> ncurses (at least, not the native cc, which had many > objections
  >> against the lynx code, like ; after cpp-expanded structure
  >> Maybe Tom is interested in pursuing this...

  Thomas> yes (need more information)

Well, there are quite a few strange things.  To start with, somtimes
./configure does not accept the native compiler:

| 18:46:32 lynx2-8-4#460$ rm config.cache
| config.cache: No such file or directory
| 18:46:32 lynx2-8-4#460$ which cc
| /opt/SUNWspro/bin/cc
| 18:46:44 lynx2-8-4#461$ which gcc
| /export/AB/local/bin//gcc
| 18:46:50 lynx2-8-4#462$ CC=cc
| 18:47:02 lynx2-8-4#463$ echo $CC
| cc
| 18:47:09 lynx2-8-4#464$ CC=cc;./configure --disable-news
| creating cache ./config.cache
| checking host system type... sparc-sun-solaris2.7
| Configuring for solaris2.7
| checking for gcc... gcc
| checking whether the C compiler (gcc  ) works... yes
| checking whether the C compiler (gcc  ) is a cross-compiler... no
| checking whether we are using GNU C... yes
| checking whether gcc accepts -g... yes

Looks like it is determined to use gcc (I've compiled ncurses with

Among other things ./configure tells that

| checking if curses supports alternate-character set... acs_map
| checking if curses supports fancy attributes... no
| checking for ncurses version... 5.0.19991023
| checking for obsolete/broken version of ncurses... no
| checking if curses supports color attributes... yes
| checking if we can include termio.h with curses... no
| srcdir is .
| updating cache ./config.cache
| creating ./config.status

Then at the compilation I get:

gcc -DHAVE_CONFIG_H   -I../../.. -I../../../src -I../../.. -I../../../src  
-I../../../WWW/Library/Implementation -O2    
-I../../../WWW/Library/Implementation/ -DXMOSAIC_HACK -DACCESS_AUTH -c 
gcc -DHAVE_CONFIG_H   -I../../.. -I../../../src -I../../.. -I../../../src  
-I../../../WWW/Library/Implementation -O2    
-I../../../WWW/Library/Implementation/ -DXMOSAIC_HACK -DACCESS_AUTH -c 
gcc -DHAVE_CONFIG_H   -I../../.. -I../../../src -I../../.. -I../../../src  
-I../../../WWW/Library/Implementation -O2    
-I../../../WWW/Library/Implementation/ -DXMOSAIC_HACK -DACCESS_AUTH -c 
In file included from ../../../src/LYStrings.h:4,
                 from ../../../WWW/Library/Implementation/HTTP.c:39:
../../../src/LYCurses.h:435: parse error before `FANCY_CURSES'
make[1]: *** [HTTP.o] Error 1

that is

| There is a problem with the configuration.  We expect to have FANCY_CURSES
| defined when COLOR_CURSES is defined, since we build on the attributes used in
| FANCY_CURSES.  Check your config.log to see why the FANCY_CURSES test failed.
| #endif


; To UNSUBSCRIBE: Send "unsubscribe lynx-dev" to address@hidden

reply via email to

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