07-29-2009
Are you calling initscr before anything else in your main function...initscr should be the first statement there and endwin should be the last call prior to returning.
10 More Discussions You Might Find Interesting
1. Programming
Hello,
when i compile with xlc on aix i got the error message "ld: 0711-317 ERROR: Undefined symbol: .hello"
dummy.pc:
#include <stdio.h>
#include <stdlib.h>
#include <string.h>
#include "dummy.h"
int main ( )
{
printf("\nbefore Hello");
hello();
printf("\npast Hello"); ... (2 Replies)
Discussion started by: stockdan
2 Replies
2. Programming
Iam attempting a script to return the current cursor position using the getyc macro
I have #included the curses.h
however on compilation (with gcc) it errors with
Undefined symbol .getcury
Undefined symbol .gercurx
Any ideas where I can find a solution or what I've missed (7 Replies)
Discussion started by: gefa
7 Replies
3. Programming
Didn't have this problem in AIX, but ported to Linux with GCC compiler and am now getting a runtime error:
tssutil: symbol lookup error: /work/agility/devel/bin/libagam.so: undefined symbol: fstat
I'm sure most of you know that fstat is an intrinsic function just like printf, memcpy, etc. When I... (5 Replies)
Discussion started by: marcus121
5 Replies
4. AIX
Hi,
I am using xlC compiler. The compilation goes fine but at the time of linking it gives the following error
ld: 0711-345 Use the -bloadmap or -bnoquiet option to obtain more information.
ld: 0711-317 ERROR: Undefined symbol: .u_strlen_2_6
ld: 0711-317 ERROR: Undefined symbol:... (0 Replies)
Discussion started by: nachiketv
0 Replies
5. Programming
Hi, i've compiled my app on x86_64 with -m32 gcc option. Can anybody tell me what is/would typically cause the 'undefined symbol: clock_gettime' error??
-1
k){0N!x y}
'/home/da71336/simon/mkvfh/mkv.so: undefined symbol: clock_gettime
@
"q"
"subr:mkv 2:`subr,3; subc:mkv 2:`subc,1;... (4 Replies)
Discussion started by: dpa078
4 Replies
6. AIX
Hi All,
When I am compiling expect 5.40 library in AIX 5.3, I am getting the following error while generating expect5.40.so file.
ld: 0711-317 ERROR: Undefined symbol: .log
ld: 0711-317 ERROR: Undefined symbol: .pow
ld: 0711-345 Use the -bloadmap or... (0 Replies)
Discussion started by: ravindra_maddal
0 Replies
7. Programming
Hi,
I am working with Solaris 5.9 and I am newbie in Socket programming and I stated working with socket programming and I copyed a simple client & server program from a website which I am attaching with this and when I am compiling these files.I am getting the error--
Please Help me to... (1 Reply)
Discussion started by: smartgupta
1 Replies
8. Programming
I have a C code which i am trying to compile using gcc. When i am trying to compile it i get the error undefined symbol error though i am providing the -l*** option where *** refers to the module where the object files for those symbols are present.
Can someone help me on the same. (4 Replies)
Discussion started by: manaankit
4 Replies
9. Programming
When I try to link a .so file I get the undefined symbol error. Though I have the library file in my system. The compile and linking commands used are as follows
g++ -m64 -g -Wall -I./include -c dxl_sample.c
g++ -o firstprogram -m64 -g -Wall -I./include -Bdynamic... (1 Reply)
Discussion started by: Ranadeep Ghosal
1 Replies
10. UNIX for Advanced & Expert Users
When I try to link a .so file I get the undefined symbol error. Though I have the library file in my system. The compile and linking commands used are as follows
g++ -m64 -g -Wall -I./include -c dxl_sample.c
g++ -o firstprogram -m64 -g -Wall -I./include -Bdynamic... (1 Reply)
Discussion started by: Ranadeep Ghosal
1 Replies
initscr(3NCURSES) initscr(3NCURSES)
NAME
initscr, newterm, endwin, isendwin, set_term, delscreen - curses screen initialization and manipulation routines
SYNOPSIS
#include <curses.h>
WINDOW *initscr(void);
int endwin(void);
bool isendwin(void);
SCREEN *newterm(char *type, FILE *outfd, FILE *infd);
SCREEN *set_term(SCREEN *new);
void delscreen(SCREEN* sp);
DESCRIPTION
initscr is normally the first curses routine to call when initializing a program. A few special routines sometimes need to be called be-
fore it; these are slk_init, filter, ripoffline, use_env. For multiple-terminal applications, newterm may be called before initscr.
The initscr code determines the terminal type and initializes all curses data structures. initscr also causes the first call to refresh to
clear the screen. If errors occur, initscr writes an appropriate error message to standard error and exits; otherwise, a pointer is re-
turned to stdscr.
A program that outputs to more than one terminal should use the newterm routine for each terminal instead of initscr. A program that needs
to inspect capabilities, so it can continue to run in a line-oriented mode if the terminal cannot support a screen-oriented program, would
also use newterm. The routine newterm should be called once for each terminal. It returns a variable of type SCREEN * which should be
saved as a reference to that terminal. The arguments are the type of the terminal to be used in place of $TERM, a file pointer for output
to the terminal, and another file pointer for input from the terminal (if type is NULL, $TERM will be used). The program must also call
endwin for each terminal being used before exiting from curses. If newterm is called more than once for the same terminal, the first ter-
minal referred to must be the last one for which endwin is called.
A program should always call endwin before exiting or escaping from curses mode temporarily. This routine restores tty modes, moves the
cursor to the lower left-hand corner of the screen and resets the terminal into the proper non-visual mode. Calling refresh or doupdate
after a temporary escape causes the program to resume visual mode.
The isendwin routine returns TRUE if endwin has been called without any subsequent calls to wrefresh, and FALSE otherwise.
The set_term routine is used to switch between different terminals. The screen reference new becomes the new current terminal. The previ-
ous terminal is returned by the routine. This is the only routine which manipulates SCREEN pointers; all other routines affect only the
current terminal.
The delscreen routine frees storage associated with the SCREEN data structure. The endwin routine does not do this, so delscreen should be
called after endwin if a particular SCREEN is no longer needed.
RETURN VALUE
endwin returns the integer ERR upon failure and OK upon successful completion.
Routines that return pointers always return NULL on error.
X/Open defines no error conditions. In this implementation endwin returns an error if the terminal was not initialized.
NOTES
Note that initscr and newterm may be macros.
PORTABILITY
These functions are described in the XSI Curses standard, Issue 4. It specifies that portable applications must not call initscr more than
once.
Old versions of curses, e.g., BSD 4.4, may have returned a null pointer from initscr when an error is detected, rather than exiting. It is
safe but redundant to check the return value of initscr in XSI Curses.
SEE ALSO
ncurses(3NCURSES), kernel(3NCURSES), refresh(3NCURSES), slk(3NCURSES), util(3NCURSES)
initscr(3NCURSES)