Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Frederic Bassaler <frederic.bassaler@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot]  xterm fails to compile
Date: Fri, 4 Mar 2011 12:11:39 +0100	[thread overview]
Message-ID: <20110304121139.54ce01d0@gmail.com> (raw)

Hi everybody,

I'm currently trying to compile xterm (Buildroot 2011.02) but it fails :

make[1]: quittant le r?pertoire ? /home/fred/buildroot ?
>>> xterm 262 Building
PATH="/home/fred/buildroot/output/host/bin:/home/fred/buildroot/output/host/usr/bin:/home/fred/buildroot/output/host/usr/sbin/:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games"
PERLLIB="/home/fred/buildroot/output/host/usr/lib/perl"  /usr/bin/make
-j2  -C /home/fred/buildroot/output/build/xterm-262/ make[1]: entrant
dans le r?pertoire ? /home/fred/buildroot/output/build/xterm-262
? /home/fred/buildroot/output/host/usr/bin/i686-unknown-linux-uclibc-gcc
--sysroot=/home/fred/buildroot/output/host/usr/i686-unknown-linux-uclibc/sysroot
-I. -I. -DHAVE_CONFIG_H  -D_GNU_SOURCE  -DNARROWPROTO=1 -DFUNCPROTO=15
-DOSMAJORVERSION=2 -DOSMINORVERSION=6
-I/home/fred/buildroot/output/host/usr/i686-unknown-linux-uclibc/sysroot/usr/include/freetype2
-pipe -Os  -mtune=i686 -march=i686 -D_LARGEFILE_SOURCE
-D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64
-I/home/fred/buildroot/output/host/usr/i686-unknown-linux-uclibc/sysroot/usr/include
-I/home/fred/buildroot/output/host/usr/i686-unknown-linux-uclibc/sysroot/include
-c ./input.c /home/fred/buildroot/output/host/usr/bin/i686-unknown-linux-uclibc-gcc
--sysroot=/home/fred/buildroot/output/host/usr/i686-unknown-linux-uclibc/sysroot
-I. -I. -DHAVE_CONFIG_H  -D_GNU_SOURCE  -DNARROWPROTO=1 -DFUNCPROTO=15
-DOSMAJORVERSION=2 -DOSMINORVERSION=6
-I/home/fred/buildroot/output/host/usr/i686-unknown-linux-uclibc/sysroot/usr/include/freetype2
-pipe -Os  -mtune=i686 -march=i686 -D_LARGEFILE_SOURCE
-D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64
-I/home/fred/buildroot/output/host/usr/i686-unknown-linux-uclibc/sysroot/usr/include
-I/home/fred/buildroot/output/host/usr/i686-unknown-linux-uclibc/sysroot/include
-c ./main.c In file included from ./input.c:86: ./xtermcap.h:62:20:
error: curses.h: No such file or directory In file included
from ./main.c:121: ./xtermcap.h:62:20: error: curses.h: No such file or
directory make[1]: *** [input.o] Erreur 1 make[1]: *** Attente des
t?ches non termin?es.... make[1]: *** [main.o] Erreur 1 make[1]:
quittant le r?pertoire ? /home/fred/buildroot/output/build/xterm-262 ?
make: *** [/home/fred/buildroot/output/build/xterm-262/.stamp_built]
Erreur 2



On another note :

I was able to generate a working embedded i386 X.org + Blackbox wm
system, but it seems that it must be done in several steps :
- first build a bare Xorg
- then add the Xorg Drivers and needed utilities

otherwise, some packages may fail to compile because of dependencies
not working (eg. xf86-input-driver would require xorg-server, but
xorg-server wasn't compiled before)

             reply	other threads:[~2011-03-04 11:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-04 11:11 Frederic Bassaler [this message]
2011-03-04 12:35 ` [Buildroot] xterm fails to compile Thomas Petazzoni
2011-03-04 16:26   ` Frederic Bassaler

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=20110304121139.54ce01d0@gmail.com \
    --to=frederic.bassaler@gmail.com \
    --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