[Top][All Lists]

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

Re: [Help-nano] Color Syntax Highlighting on Solaris 8 shows up as white

From: Garth Dahlstrom
Subject: Re: [Help-nano] Color Syntax Highlighting on Solaris 8 shows up as white and grey
Date: Tue, 17 Apr 2007 12:10:39 -0400

Oh, thanks for the reply...  I've since figured out the problem
(though it did take quite a while), I didn't post that I'd found
solution because I figured nobody cared. :)

The problem lies with the terminal emulation.  I built and installed
ncurses into my home dir, exported TERMINFO_DIRS to my ncurses dir and
exported TERM to xterm.  And now I have color...

Here is the cleaned up version of what I used to build

#### Building Nano on Solaris ####
### GED 2007
### This is a non-root install, assumes running bash, and your .bashrc contains:
###   export build_dest=~/ged
###   export PATH=${build_dest}/bin:$PATH
###   export TERMINFO_DIRS=${build_dest}/share/terminfo/:/usr/share/lib/terminfo
### change build_dest to whatever you'd like, just make sure it has a
/bin subdir

export build_dest=~/ged
export build_base=`pwd`

### Get sources
# wget
# wget
# wget

### Build texinfo - builddep required for ncurses/nano
(gunzip -c texinfo-4.2.tar.gz | tar -xvf -; cd texinfo-4.2;
./configure && make; cp ./makeinfo/makeinfo ${build_dest}/bin/)

### Build ncurses
cd ${build_base}
ncurses_version=$(basename `ls -lrt --color=none ncurses-*.tar.gz|tail
-1| cut -b57-` .tar.gz)
gunzip -c ${ncurses_version}.tar.gz | tar -xvf -
cd ${build_base}/${ncurses_version}
./configure --without-curses-h --enable-overwrite
make install DESTDIR=${build_base}/${ncurses_version}

### Build Nano
export CPPFLAGS=-I${build_base}/${ncurses_version}/usr/local/include
export LDFLAGS=-L${build_base}/${ncurses_version}/usr/local/lib
cd ${build_base}
nano_version=$(basename `ls -lrt --color=none nano-*.tar.gz|tail -1|
cut -b57-` .tar.gz)
gunzip -c ${nano_version}.tar.gz | tar -xvf -
cd ${build_base}/${nano_version}
make clean; ./configure --enable-all && make
mv src/nano ${build_dest}/bin/${nano_version}-`date +%Y%m%d` && rm
${build_dest}/bin/nano; (cd ${build_dest}/bin/ && ln -s
${nano_version}-`date +%Y%m%d` nano)

On 4/17/07, David Ramsey <address@hidden> wrote:
Garth Dahlstrom wrote:
> Hi,
> Some months back I managed to build nano 1.999 using "./configure
> --enable-all", I copied some of the .nanorc syntax highlighting from
> my linux box and I fired up nano using numerous different files that
> match the syntax highlight rules.
> What happens on my servers is where colours should be applied I get
> white instead (when syntax highlighting is off everything is
> silver/grey).  I've tried different TERM settings like vt100, ansi,
> xterm, linux, but the result is the same...
> I know putty with these term settings can display colour as I have a
> colour PS2 prompt and Midnight Commander works in colour.
> Is something else I can try or some way to troubleshoot this?

Sorry for the delay; I've been extremely busy until recently.

I'm not certain what to try, since I have no access to a Solaris
machine, but I have a few questions that may help narrow this down.

1. Your other post, which I'll get to below, mentions build problems on
Solaris 8 linking against ncurses.  Is this also on Solaris 8, and is
nano also linked against ncurses?

2. If it is on Solaris 8, I found this link about colorization after
some googling.  Is it any help?

3. When you mention your color prompt and Midnight Commander, are you
using them on these servers?

4. Are you accessing these servers locally or remotely when the problem

5. What terminal are you using on these servers?  (The actual program,
not the $TERM value it uses.)

6. Is your Midnight Commander linked against slang or ncurses?  (For

7. Which versions of slang and/or ncurses do you have installed?


> I have a small problem with my build which I've read may be related to
> a lack of ncurses.h...

If this link is anything to go by

, that sounds right.  Since nano does build, and the error log shows a
linking problem against ncurses, it could be that nano's being built
against Solaris curses, and then linked against ncurses, which fails
because the two curses (curseses?) are different internally.  This is
because nano first tries to build using ncurses.h, and falls back to
curses.h if ncurses.h isn't available.

> If anyone with experince building nano could offer suggestions as to
> how to fix this, I'd be greatful.

Does Solaris have a development package for ncurses (which should have
ncurses.h)?  If so, try installing it, and then see if nano builds

--- == __/ t.O ==--

reply via email to

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