From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 8206] mplayer uses host xorg development files
Date: Sat, 3 Oct 2015 07:56:43 +0100 [thread overview]
Message-ID: <560F7C2B.5070608@mind.be> (raw)
In-Reply-To: <1443806071553-113718.post@n4.nabble.com>
On 02-10-15 18:14, glscantlen wrote:
> I realize this is an old thread, but it appears the issue was not resolved
> and I have a solution that works for my defconfig on both 2015.05 & .08.
>
> The most recent version I have tested is snapshot 2015.08 from
> git.buildroot.net
> on Sept.30. That version has exhibited the same issue as previous versions
> noted in this thread "mplayer uses host xorg development files"
>
> The solution I am using is described here:
> - Fix a bug in the mplayer's .mk file. Add Buildroot's path
> for staging to mplayer's configuration, ~ line 259
> $ nano -w package/mplayer/mplayer.mk
> --extra-cflags="$(MPLAYER_CFLAGS) -I$(STAGING_DIR)/usr/include" \
> --extra-ldflags="$(MPLAYER_LDFLAGS) -L$(STAGING_DIR)/usr/lib" \
I've done a few tests with the PARANOID handling to detect a problem here, but
couldn't find any. However, I do notice in the configure script that it will
happily search for headers in /usr/include, but AFAICS without actually adding
/usr/include to the search path. Explicitly adding $(STAGING_DIR)/usr/include
will work because then configure will look for the header file in that place.
The ldflags addition shouldn't be needed however.
Now, the problem in your case seems to be that you don't have
BR2_PACKAGE_XLIB_LIBXV selected, which means that there will be no useful X11
support included. And indeed, the logs you posted earlier show that mplayer is
using the framebuffer instead of X11.
That said, I guess the mplayer package could really use some love to properly
deal with all the silliness in its configure script.
Regards,
Arnout
>
>
>
>
> --
> View this message in context: http://buildroot-busybox.2317881.n4.nabble.com/Bug-8206-New-mplayer-uses-host-xorg-development-files-tp104861p113718.html
> Sent from the Buildroot (busybox) mailing list archive at Nabble.com.
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
>
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF
next prev parent reply other threads:[~2015-10-03 6:56 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
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 [this message]
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=560F7C2B.5070608@mind.be \
--to=arnout@mind.be \
--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