Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] xterm fails to compile
Date: Fri, 4 Mar 2011 13:35:33 +0100	[thread overview]
Message-ID: <20110304133533.1e06310f@surf> (raw)
In-Reply-To: <20110304121139.54ce01d0@gmail.com>

Hello Frederic,

On Fri, 4 Mar 2011 12:11:39 +0100
Frederic Bassaler <frederic.bassaler@gmail.com> wrote:

> -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

Yes, xterm needs ncurses. I have the following patch in one of my
branch since July 2010, but never had the time to finalize it. I think
it should fix your problem:

=======================================================================
commit 2bb119327287ff859d5bc292881fc7e8f6c83bc6
Author: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Date:   Thu Jul 22 15:45:19 2010 +0200

    xterm: add missing dependency on ncurses
    
    Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>

diff --git a/package/xterm/Config.in b/package/xterm/Config.in
index da3e9fe..447c912 100644
--- a/package/xterm/Config.in
+++ b/package/xterm/Config.in
@@ -1,6 +1,7 @@
 config BR2_PACKAGE_XTERM
        bool "xterm"
        depends on BR2_PACKAGE_XORG7
+       select BR2_PACKAGE_NCURSES
        help
          xterm terminal emulator
 
diff --git a/package/xterm/xterm.mk b/package/xterm/xterm.mk
index b07eda4..2304dd7 100644
--- a/package/xterm/xterm.mk
+++ b/package/xterm/xterm.mk
@@ -7,7 +7,8 @@
 XTERM_VERSION:=259
 XTERM_SOURCE:=xterm-$(XTERM_VERSION).tgz
 XTERM_SITE:=ftp://invisible-island.net/xterm
-XTERM_DEPENDENCIES = xserver_xorg-server
+XTERM_DEPENDENCIES = xserver_xorg-server ncurses
 XTERM_INSTALL_TARGET_OPT = DESTDIR=$(TARGET_DIR) install
+XTERM_CONF_OPT = --disable-imake
 
 $(eval $(call AUTOTARGETS,package,xterm))
=======================================================================

> 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)

Hum, which driver failed exactly ? Because for example
xdriver_xf86-input-evdev already has the dependency on
xserver_xorg-server. And from a quick look, it seems that all other
input drivers also have xserver_xorg-server in their dependencies.
Could you bit a more specific about the failure (i.e give us
the .config + build log) ?

Thanks !

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

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

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-04 11:11 [Buildroot] xterm fails to compile Frederic Bassaler
2011-03-04 12:35 ` Thomas Petazzoni [this message]
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=20110304133533.1e06310f@surf \
    --to=thomas.petazzoni@free-electrons.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