[Top][All Lists]

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

Re: Ncurses/dialog static linking on 64bit problem

From: Thomas Dickey
Subject: Re: Ncurses/dialog static linking on 64bit problem
Date: Tue, 8 May 2007 16:55:51 -0400 (EDT)

On Tue, 8 May 2007, VinX wrote:

Thomas Dickey wrote:
Is it that the static linking fails, or that the application fails to run.
no dialog runs but not draw... it write on standard output only part of
text and some others strange chars... as if it didn't understand the
terminal are using... (but terminfo is enabled and i have all files into

So either it's picking up some unexpected library, or there's some bug
to investigate.

You can make the debugging a little easier by configuring ncurses with
its tracing feature enabled (configure --with-trace).  The current
dialog program also has tracing (though less powerful).

By running the program in both environments with the tracing activated,
you may see some discrepancy between the two.  (I'm not sure what you
would find).

Given an application that's linked with ncurses+tracing, you can set
the NCURSES_TRACE environment variable, e.g,.

        export NCURSES_TRACE=0xffff

and the application writes to "trace" with the call/return information
and associated details.

Aside from pointer-values in the traces, they "should" be the same...

I don't see any discussion of what -L options you used to limit that to
the static libraries just built (or using ldd to verify that dialog
was built with static ncurses libraries).

Yes, after ./configure in dialog package i edit the makefile and edit
the LIBS variable same as this:
LIBS = -L/path/my/ncurses/build/lib/ -lncurses  -lm -L/lib #
and CC become "gcc -static"


Thomas E. Dickey

reply via email to

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