All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thierry Bultel <thierry.bultel@wanadoo.fr>
To: buildroot@busybox.net
Subject: [Buildroot] xapp_init: bad substitution of mcookie path in startx
Date: Thu, 17 Jan 2013 17:06:39 +0100	[thread overview]
Message-ID: <50F8218F.4070701@wanadoo.fr> (raw)
In-Reply-To: <871uf5obh3.fsf@dell.be.48ers.dk>

Hi,

Sorry for the long delay

The  bug is reproducible with latest release,
and I finally found out why.

The issue is that in xapp_xinit, 'configure' checks for 'mcookie', and 
the first time, founds it ... on the host side, ie the 
"/usr/bin/mcookie" of Ubuntu for instance. This is the path that is 
substituted in startx.

When rebuilding the xapp_xinit package, "mcookie" has been built by 
buildroot, in the xorg_server package. Thus "configure" finds it in our 
build directory, ie output/host/usr/bin/mcookie, which is not a target path.

A quick fix (not meaning it is the cleanest way) is simply to add

XAPP_XINIT_CONF_OPT += MCOOKIE=/usr/bin/mcookie

in xapp_xinit.mk

Thierry


Le 04/12/2012 20:37, Peter Korsgaard a ?crit :
>>>>>> "Thierry" == Thierry Bultel <thierry.bultel@wanadoo.fr> writes:
>
>   Thierry> Hi,
>   Thierry> The generated "startx" has the host path for mcookie:
>
>
>
>   Thierry> ----------
>   Thierry>    esac
>
>   Thierry>     authdisplay=${display:-:0}
>
>
>   Thierry> mcookie=`/nous/BASYSTEMES/Buildroot/output.imx6neon/host/usr/bin/mcookie`
>
> What buildroot version are you using? It seems to be correct here with
> current git:
>
> grep bin/mcookie output/target/usr/bin/startx
>      mcookie=`/usr/bin/mcookie`
>

  parent reply	other threads:[~2013-01-17 16:06 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-04 12:35 [Buildroot] xapp_init: bad substitution of mcookie path in startx Thierry Bultel
2012-12-04 19:37 ` Peter Korsgaard
2012-12-04 21:12   ` Thierry Bultel
2013-01-17 16:06   ` Thierry Bultel [this message]
2013-01-19 13:27     ` Arnout Vandecappelle
2013-01-19 13:42       ` Thomas Petazzoni
2013-01-19 15:57         ` Arnout Vandecappelle
2013-01-20  8:53           ` Peter Korsgaard

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=50F8218F.4070701@wanadoo.fr \
    --to=thierry.bultel@wanadoo.fr \
    --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 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.