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] xlib libXt build problem
Date: Tue, 28 Jul 2009 10:03:33 +0200	[thread overview]
Message-ID: <20090728100333.16e1cbc4@surf> (raw)
In-Reply-To: <f8955f9e0907271636p26bea750s1f3e6be1782badac@mail.gmail.com>

Le Mon, 27 Jul 2009 16:36:27 -0700,
Dan Lykowski <lykowdk@gmail.com> a ?crit :

> Steve,
>  Try to replace the xlib_libXt-1.0.5-makestrs-nocc.patch with this
> one.
> 
> I grabbed it from upstream a while back and haven't had time to
> submit it. It fixed the problem for me, but I don't know if it 'does
> the right thing(tm)'.

This patch has been included in 1.0.6 of libXt. Therefore, I will bump
the libXt package to 1.0.6.

However, note that in the current development version of Buildroot, the
compilation of libXt and libXaw is no longer required to compile the
X.org server. These old (and ugly) toolkits are probably never used on
embedded systems, so having them as a hard dependency of the X.org
server was a bit too strong. It also ~1 Mb of space on the target
filesystem, since these libraries were quite big.

See
http://git.buildroot.net/buildroot/commit/?id=ae8bbdf891c8343313cd2d3be2df079214576a4a

If you don't want to use a development version of Buildroot, these
improvements will be part of the 2009.08, that should be released neext
month.

Sincerly,

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

      reply	other threads:[~2009-07-28  8:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-27 17:30 [Buildroot] xlib libXt build problem Steve Bennett
2009-07-27 19:50 ` Thomas Petazzoni
2009-07-27 20:18   ` Steve Bennett
2009-07-27 20:09 ` Steve Bennett
2009-07-27 23:36 ` Dan Lykowski
2009-07-28  8:03   ` Thomas Petazzoni [this message]

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=20090728100333.16e1cbc4@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