Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: glscantlen <glscantlen@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 8206] mplayer uses host xorg development files
Date: Sat, 11 Jul 2015 07:36:19 -0700 (PDT)	[thread overview]
Message-ID: <1436625379066-105305.post@n4.nabble.com> (raw)
In-Reply-To: <55A12A5E.4010900@mind.be>

Thanks Arnout,

That is essentially what I've done.
My initial thinking was the patch got copied into the tree somewhere, then
re-build.
But that is not the case , as your reply suggests.




--
View this message in context: http://buildroot-busybox.2317881.n4.nabble.com/Bug-8206-New-mplayer-uses-host-xorg-development-files-tp104861p105305.html
Sent from the Buildroot (busybox) mailing list archive at Nabble.com.

  reply	other threads:[~2015-07-11 14:36 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-06 16:15 [Buildroot] [Bug 8206] New: mplayer uses host xorg development files bugzilla at busybox.net
2015-07-07 15:43 ` [Buildroot] [Bug 8206] " bugzilla at busybox.net
2015-07-11 13:19   ` glscantlen
2015-07-11 13:31     ` glscantlen
2015-07-11 14:30       ` Thomas Petazzoni
2015-07-07 20:59 ` bugzilla at busybox.net
2015-07-07 21:00 ` bugzilla at busybox.net
2015-07-11 13:41   ` glscantlen
2015-07-11 14:38     ` Arnout Vandecappelle
2015-07-11 14:36       ` glscantlen [this message]
2015-07-11 15:26         ` Arnout Vandecappelle
2015-07-11 15:39           ` Thomas Petazzoni
2015-07-11 15:42             ` Arnout Vandecappelle
2015-10-02 17:14               ` glscantlen
2015-10-03  6:56                 ` Arnout Vandecappelle
2015-07-07 21:01 ` bugzilla at busybox.net
2015-07-10 23:10 ` bugzilla at busybox.net
2015-07-11 15:25 ` bugzilla at busybox.net
2015-07-11 15:38 ` bugzilla at busybox.net
2015-07-13 13:12   ` glscantlen
2015-07-11 16:07 ` bugzilla at busybox.net
2015-10-22 20:22 ` bugzilla at busybox.net
2016-08-31 21:18 ` bugzilla at busybox.net
2016-09-01 15:11 ` bugzilla at busybox.net

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=1436625379066-105305.post@n4.nabble.com \
    --to=glscantlen@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