All of lore.kernel.org
 help / color / mirror / Atom feed
From: Craig Swank <craigswank@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: ncurses
Date: Sun, 04 Mar 2012 14:11:43 -0700	[thread overview]
Message-ID: <4F53DA8F.5050109@gmail.com> (raw)

Hello,
I'm getting an error when I try to bitbake ncurses.  I set up my 
openembedded environment according to the instructions at:
http://www.angstrom-distribution.org/building-angstrom

when I do bitbake ncurses I get the following error:

| error: unknown type name 'SIG_ATOMIC_T'
| In file included from 
/home/craig/Projects/OE/setup-scripts/build/tmp-angstrom_2010_x-eglibc/work/x86_64-linux/ncurses-native-5.9-r4.1/ncurses-5.9/ncurses/build.priv.h:85:0,
|                  from 
/home/craig/Projects/OE/setup-scripts/build/tmp-angstrom_2010_x-eglibc/work/x86_64-linux/ncurses-native-5.9-r4.1/ncurses-5.9/ncurses/tinfo/make_keys.c:40:
| 
/home/craig/Projects/OE/setup-scripts/build/tmp-angstrom_2010_x-eglibc/work/x86_64-linux/ncurses-native-5.9-r4.1/ncurses-5.9/ncurses/../include/nc_alloc.h:97:0: 
warning: "strdup" redefined [enabled by default]
| /usr/include/x86_64-linux-gnu/bits/string2.h:1316:0: note: this is the 
location of the previous definition
| 
/home/craig/Projects/OE/setup-scripts/build/tmp-angstrom_2010_x-eglibc/work/x86_64-linux/ncurses-native-5.9-r4.1/ncurses-5.9/ncurses/curses.priv.h:1165:1: 
error: unknown type name 'SIG_ATOMIC_T'
| In file included from 
/home/craig/Projects/OE/setup-scripts/build/tmp-angstrom_2010_x-eglibc/work/x86_64-linux/ncurses-native-5.9-r4.1/ncurses-5.9/ncurses/curses.priv.h:1444:0,
|                  from 
/home/craig/Projects/OE/setup-scripts/build/tmp-angstrom_2010_x-eglibc/work/x86_64-linux/ncurses-native-5.9-r4.1/ncurses-5.9/ncurses/tinfo/access.c:33:
| 
/home/craig/Projects/OE/setup-scripts/build/tmp-angstrom_2010_x-eglibc/work/x86_64-linux/ncurses-native-5.9-r4.1/ncurses-5.9/ncurses/../include/nc_alloc.h:97:0: 
warning: "strdup" redefined [enabled by default]
| /usr/include/x86_64-linux-gnu/bits/string2.h:1316:0: note: this is the 
location of the previous definition
| make[1]: *** [../obj_s/access.o] Error 1
| make[1]: *** Waiting for unfinished jobs....
| make[1]: Leaving directory 
`/home/craig/Projects/OE/setup-scripts/build/tmp-angstrom_2010_x-eglibc/work/x86_64-linux/ncurses-native-5.9-r4.1/ncurses-5.9/narrowc/ncurses'
| make: *** [libs] Error 2
| make: Leaving directory 
`/home/craig/Projects/OE/setup-scripts/build/tmp-angstrom_2010_x-eglibc/work/x86_64-linux/ncurses-native-5.9-r4.1/ncurses-5.9/narrowc'
| ERROR: oe_runmake failed
NOTE: package ncurses-native-5.9-r4.1: task do_compile: Failed
ERROR: Task 219 
(virtual:native:/home/craig/Projects/OE/setup-scripts/sources/openembedded-core/meta/recipes-core/ncurses/ncurses_5.9.bb, 
do_compile) failed with exit code '1'

Can anyone suggest how I can get it working?

Just in case you need this:

OS: Ubuntu 11.10
Processor: quad core AMD (64 bit)


Craig



             reply	other threads:[~2012-03-04 21:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-04 21:11 Craig Swank [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-04-18 16:47 ncurses glen
2002-04-18 20:43 ` ncurses Richard Adams
2002-04-20 16:03 ` ncurses lawson_whitney
1997-06-30 17:54 ncurses Mike Shaver
1997-06-30 17:54 ` ncurses Mike Shaver

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=4F53DA8F.5050109@gmail.com \
    --to=craigswank@gmail.com \
    --cc=openembedded-devel@lists.openembedded.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.