From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] xorg-driver-input-tslib compile error
Date: Sun, 13 Nov 2011 10:26:16 +0100 [thread overview]
Message-ID: <20111113092616.GB9073@pengutronix.de> (raw)
In-Reply-To: <loom.20111113T033317-924@post.gmane.org>
Hi,
On Sun, Nov 13, 2011 at 03:12:15AM +0000, Francesco Brasini wrote:
> I'm using ptxdist-2011.10.1 and OSELAS.BSP-Pengutronix-Mini2440-2011.10.0
> on a debian squeeze host machine (with OSELAS.Toolchain-2011.03.1).
>
> I was successful in compiling a number of packages and in generating images
> for the kernel and barebox (and boot without problems a mini2440 board with
> 1G of flash), largely thanks to the excellent documentation that you have made
> available.
>
> So far I experienced a single failure, trying to compile xorg-driver-input-
> tslib.
>
> The relevant log messages follows:
[...]
Disable XORG_SERVER_TSLIB (Build kdrive tslib touchscreen support), or
better don't build kdrive at all. You don't need Xorg and a kdrive based
server.
The problem ist that using "kdrive tslib support" will add some
"#define TSLIB 1" or something like that to a global Xorg header. This
breaks "_X_EXPORT InputDriverRec TSLIB = {".
Michael
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
--
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2011-11-13 9:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-13 3:12 Francesco Brasini
2011-11-13 9:26 ` Michael Olbrich [this message]
[not found] ` <4ECCEFA7.7090700@gmail.com>
2011-11-23 15:23 ` Michael Olbrich
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=20111113092616.GB9073@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=ptxdist@pengutronix.de \
/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