bug-ncurses
[Top][All Lists]
Advanced

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

ncurses 5.7 compile failure when crosscompiling to arm


From: Bernhard Rosenkraenzer
Subject: ncurses 5.7 compile failure when crosscompiling to arm
Date: Tue, 09 Mar 2010 12:56:04 +0100
User-agent: BlankPage Webmail/0.3-beta

Hi,
ncurses 5.7 compiles and works fine on x86_64, but when I try to
crosscompile it to armv6j-unknown-linux-gnueabi, I get (while compiling a
tool that is run on the x86_64 build machine, not even while building the
arm lib):

gcc -o make_hash -DHAVE_CONFIG_H -I../ncurses -I. -I./../include
-I../include   ./tinfo/make_hash.c
In file included from ./tinfo/make_hash.c:40:0:
../ncurses/curses.priv.h:559:2: error: expected specifier-qualifier-list
before ‘cchar_t’
../ncurses/curses.priv.h:615:2: error: expected specifier-qualifier-list
before ‘cchar_t’
../ncurses/curses.priv.h:909:2: error: expected specifier-qualifier-list
before ‘cchar_t’
In file included from ./tinfo/make_hash.c:40:0:
../ncurses/curses.priv.h:1689:1: warning: parameter names (without types)
in function declaration
../ncurses/curses.priv.h:1690:31: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
‘__attribute__’ before ‘_nc_to_widechar’
../ncurses/curses.priv.h:1724:48: error: expected declaration specifiers
or ‘...’ before ‘cchar_t’
../ncurses/curses.priv.h:1729:56: error: expected ‘;’, ‘,’ or ‘)’ before
‘*’ token
../ncurses/curses.priv.h:1860:37: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
‘__attribute__’ before ‘_nc_render’
../ncurses/curses.priv.h:1862:113: error: expected declaration specifiers
or ‘...’ before ‘cchar_t’
../ncurses/curses.priv.h:1866:67: error: expected ‘;’, ‘,’ or ‘)’ before
‘*’ token
../ncurses/curses.priv.h:1870:61: error: expected declaration specifiers
or ‘...’ before ‘mbstate_t’
make[1]: *** [make_hash] Error 1
make[1]: Leaving directory `/usr/src/ark/BUILD/ncurses-5.7/ncurses'
make: *** [all] Error 2

I tried both stock 5.7 and 5.7 with all patches up to 20100306 applies,
with identical results.

Any ideas?

ttyl
bero




reply via email to

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