From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] Problem with buildroot-2013.02 - ncurses
Date: Wed, 13 Mar 2013 00:14:23 +0100 [thread overview]
Message-ID: <513FB6CF.1070301@mind.be> (raw)
In-Reply-To: <84EA0F7435E5F64C9B660453645DB90497AD52AA50@DSW350.wattens.swarovski.com>
On 03/08/13 12:29, Spielmann Werner wrote:
> /usr/bin/gcc -DHAVE_CONFIG_H -I../ncurses -I. -I<MY_WORKSPACE>/buildroot-2013.02/output/host/usr/include -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -DNDEBUG -I. -I../include -I<MY_WORKSPACE>/buildroot-2013.02/output/host/usr/include/ncurses -O2 -I<MY_WORKSPACE>/buildroot-2013.02/output/host/usr/include --param max-inline-insns-single=1200 -c ../ncurses/./base/lib_addstr.c -o ../objects/lib_addstr.o
> /usr/bin/gcc -DHAVE_CONFIG_H -I../ncurses -I. -I<MY_WORKSPACE>/buildroot-2013.02/output/host/usr/include -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -DNDEBUG -I. -I../include -I<MY_WORKSPACE>/buildroot-2013.02/output/host/usr/include/ncurses -O2 -I<MY_WORKSPACE>/buildroot-2013.02/output/host/usr/include --param max-inline-insns-single=1200 -c ../ncurses/./base/lib_beep.c -o ../objects/lib_beep.o
> In file included from ../include/term_entry.h:48,
> from ../progs/progs.priv.h:111,
> from ../progs/tic.c:41:
> ../include/term.h:702: error: field ?Ottyb? has incomplete type
Looks like there's something fishy with your host's environment...
The field 'tty' that is indicated has type TTY, which is defined as
'struct termios'. struct termios is defined in
/usr/include/bits/termios.h, which is included by
/usr/include/termios.h, which is included by ../include/term.h.
So it _should_ work.
Can you do the following:
cd /home/spiewe/svnws/buildroot-2013.02/output/build/host-ncurses-5.9/progs
/usr/bin/gcc -I../progs -I. -DHAVE_CONFIG_H -I/home/spiewe/svnws/buildroot-2013.02/output/host/usr/include -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -DNDEBUG -I. -I../include -I/home/spiewe/svnws/buildroot-2013.02/output/host/usr/include/ncurses -O2 -I/home/spiewe/svnws/buildroot-2013.02/output/host/usr/include --param max-inline-insns-single=1200 -E ../progs/dump_entry.c > /tmp/dump_entry.E
and post the resulting /tmp/dump_entry.E in a pastebin. Then we can check
what is going wrong with termios.
BTW which distro do you use?
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
next prev parent reply other threads:[~2013-03-12 23:14 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-06 11:43 [Buildroot] Problem with buildroot-2013.02 - emacs Spielmann Werner
2013-03-07 6:31 ` Spielmann Werner
2013-03-07 8:30 ` Thomas Petazzoni
2013-03-07 12:47 ` Spielmann Werner
2013-03-07 13:08 ` Thomas Petazzoni
2013-03-08 11:29 ` [Buildroot] Problem with buildroot-2013.02 - ncurses Spielmann Werner
2013-03-08 12:16 ` Thomas Petazzoni
2013-03-08 13:07 ` Spielmann Werner
2013-03-08 13:16 ` Thomas Petazzoni
2013-03-11 7:35 ` Spielmann Werner
2013-03-12 14:51 ` Spielmann Werner
2013-03-12 23:14 ` Arnout Vandecappelle [this message]
2013-03-13 7:21 ` Thomas Petazzoni
2013-03-13 8:47 ` Spielmann Werner
2013-03-13 19:38 ` Arnout Vandecappelle
2013-03-14 7:15 ` Spielmann Werner
2013-03-14 8:03 ` Arnout Vandecappelle
2013-03-14 14:53 ` Spielmann Werner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=513FB6CF.1070301@mind.be \
--to=arnout@mind.be \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox