[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: Thu, 10 May 2007 20:46:20 -0400 (EDT)

On Thu, 10 May 2007, VinX wrote:

Thomas Dickey wrote:
But also there should be a file named "trace" which is created by
setting the NCURSES_TRACE variable and
linking to the --with-trace'd ncurses.  You can check if the static
executable has trace functions, since "nm" would show "trace", "_tracef"
and several other "_traceXXX" symbols.

yes, i had a mistake!

Now i have generated two trace files, one by an 32bit architecture
(trace_dialog32) and one by a 64bit (trace_dialog64)...
I have 'diffed' this files with:
#in attachment gzipped
diff -ruNp trace_dialog32 trace_dialog64 > diff_trace_dialog
I have found this difference:
render_char bkg {' ' = 040} (0),
         attrs {A_BOLD|A_COLOR{1 = {COLOR_CYAN, COLOR_BLUE}}} (1)

      -> ch {' ' = 040 |
            {A_BOLD|A_COLOR{1 = {COLOR_CYAN, COLOR_BLUE}}}} (1)
render_char bkg {000} (0),
         attrs {A_BOLD|A_COLOR{1 = {COLOR_CYAN, COLOR_BLUE}}} (1)
      -> ch {000 |
            {A_BOLD|A_COLOR{1 = {COLOR_CYAN, COLOR_BLUE}}}} (1)

'000'... is it the problem?

probably - ignoring pointers, that is the first difference.

It should be set to a blank, e.g., in

    SetChar(win->_nc_bkgd, BLANK_TEXT, BLANK_ATTR);

Thomas E. Dickey

reply via email to

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