bug-ncurses
[Top][All Lists]
Advanced

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

Re: Building 64-bit version of ncurses on Solaris 8


From: Thomas Dickey
Subject: Re: Building 64-bit version of ncurses on Solaris 8
Date: Fri, 1 Feb 2002 05:59:47 -0500
User-agent: Mutt/1.2.5i

On Fri, Feb 01, 2002 at 12:43:44AM -0600, Albert Chin wrote:
> I am attempting to build a 64-bit version of the ncurses library on
> Solaris 8/SPARC using the Sun C compiler. Building the 32-bit version
> works fine. However, for the 64-bit version (CFLAGS="-xarch=v9"):
> 
> cd ../obj_s;  cc -I../ncurses -I.  -I. -I../include
> -I/opt/TWWfsw/ncurses5/include/ncurses -DHAVE_CONFIG_H -mr -Qn -xO2
> -xtarget=generic -xarch=v9  -KPIC -c ../ncurses/./base/vsscanf.c
> "../ncurses/./base/vsscanf.c", line 50: undefined struct/union member: _flag
> "../ncurses/./base/vsscanf.c", line 51: undefined struct/union member: _ptr
> "../ncurses/./base/vsscanf.c", line 51: undefined struct/union member: _base
> "../ncurses/./base/vsscanf.c", line 51: warning: improper
> pointer/integer combination: op "="
> "../ncurses/./base/vsscanf.c", line 52: undefined struct/union member: _cnt
> "../ncurses/./base/vsscanf.c", line 53: undefined struct/union member: _file
> cc: acomp failed for ../ncurses/./base/vsscanf.c
> 
> The problem is that in /usr/include/stdio_impl.h:
>   struct FILE {
>     long __pad[16];
>   }
> when we're compiling in 64-bit mode. For 32-bit mode, you get the
> usual things you expect in the FILE struct.
> 
> Is there a solution? An alternate vsscanf is available as part of the
> trio library:
>   http://ctrio.sourceforge.net

that's possible (though it might take some rework).  I could always make a
fallback working about as well as safe_sprintf, but have been reluctant to do
so because it's a lot of code for a special case.  Someone else reported this
last month and simply ifdef'd the code to say it fails.

-- 
Thomas E. Dickey <address@hidden>
http://invisible-island.net
ftp://invisible-island.net



reply via email to

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