help-nano
[Top][All Lists]
Advanced

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

[Help-nano] Problems compiling nano 2.2.3 in Cygwin


From: Eric Oliver
Subject: [Help-nano] Problems compiling nano 2.2.3 in Cygwin
Date: Wed, 24 Feb 2010 08:21:33 -0800

Hello,

                I’m attempting to compile and run nano under cygwin.  You may ask, why not ask the folks over at cygwin’s support.  Well I don’t expect anyone to fix this problem for me but I’m looking for more information on what is troubling the compilation so I can take this information to cygwin’s support.  I’ve been taking notes on the errors and other things of interest.  I would like some help filling in the gaps.  From what I understand this happens in a function that deals with the resizing of windows down two variables that won’t seem to take assignments.

 

 

ERROR

-----

nano.c In fucntion 'handle_sigwinch':

 

nano.c:1267: error: lvalue required as left operand of assignment

nano.c:1268: error: lvalue required as left operand of assignment

make[1]: *** [nano.o] Error 1

make[1]: Leaving directory '/tmp/nano-2.2.3/src'

make: *** [install-recursive] Error 1

---------------------------------------------------------------

 

offending lines are:

 

COLS = win.ws_col;

LINES = win.ws_row;

 

Why does it appear that win.ws_col and win.ws_row appear only in

 one place and NOWHERE else?

 

The comments say that the variables COLS and LINES "are curses global

variables, and in some cases curses has already updated them. But not in

all cases. Argh." What does this mean for me to port this to cygwin?

 

What is an lvalue?

------------------

An lvalue is an _expression_ to which a value can be assigned. The lvalue

_expression_ is located on the left side of an assignment statement,

whereas an rvalue is located on the right side of an assignment

statement. Each assignment statement must have an lvalue and an rvalue.

the lvalue _expression_ must reference a storable variable in memory. It

cannot be constant.

------------------------------------------------------------------------

 

So does this imply that COLS and LINES are not seen as storable

variables in memory?  How do I go about making them so... Why is this

even happening? I've verified that I do have slcurses.h ncurses.h and curses.h

all are in /usr/include/ folder.

 

 

Thank you very much!


reply via email to

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