New: mplayer uses host xorg development files

https://bugs.busybox.net/show_bug.cgi?id=8206

Summary: mplayer uses host xorg development files
Product: buildroot
Version: 2015.05
Platform: PC
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
AssignedTo: unassigned at buildroot.uclibc.org
ReportedBy: glscantlen at gmail.com
CC: buildroot at uclibc.org
Estimated Hours: 0.0

I am using buildroot-2015.05
Installed on a fresh Ubuntu 14.04 host, with only basic build requirements ie "apt-get install build-essential git ccache"

I have configured BuildRoot for basic Xorg with mplayer. (I'll attach defconfig)
The "make" passes without error and everything works on target H/W except mplayer.
Mplayer acts as-if there is no xorg.
I have discovered, if I "apt-get install xorg-dev" to the host and rebuild mplayer it will then work.
Why is mplayer's configure using the host's xorg-development files? I would expect it must use the BuildRoot tree's development files.

sorry I can not attach a simple text file... DAH!
So I'll just paste here:

BR2_arm=y
BR2_cortex_a7=y
BR2_ARM_EABIHF=y BR2_DEFCONFIG="$(CONFIG_DIR)/defconfig" BR2_CCACHE=y
BR2_TOOLCHAIN_EXTERNAL=y BR2_TOOLCHAIN_EXTERNAL_CUSTOM=y BR2_TOOLCHAIN_EXTERNAL_PATH="$(HOME)/xu3_mplayer/linaro-4.9" BR2_TOOLCHAIN_EXTERNAL_CUSTOM_PREFIX="arm-linux-gnueabihf" BR2_TOOLCHAIN_EXTERNAL_HEADERS_3_17=y BR2_TOOLCHAIN_EXTERNAL_CUSTOM_GLIBC=y BR2_TOOLCHAIN_EXTERNAL_CXX=y BR2_ROOTFS_DEVICE_CREATION_DYNAMIC_EUDEV=y BR2_ROOTFS_POST_BUILD_SCRIPT="support/scripts/config_eth" BR2_PACKAGE_ALSA_UTILS=y BR2_PACKAGE_ALSA_UTILS_SPEAKER_TEST=y BR2_PACKAGE_FFMPEG=y
BR2_PACKAGE_MPLAYER=y
BR2_PACKAGE_MESA3D_DEMOS=y
BR2_PACKAGE_MESA3D=y BR2_PACKAGE_MESA3D_DRI_DRIVER_SWRAST=y BR2_PACKAGE_MESA3D_OPENGL_EGL=y BR2_PACKAGE_MESA3D_OPENGL_ES=y
BR2_PACKAGE_XORG7=y BR2_PACKAGE_XSERVER_XORG_SERVER=y BR2_PACKAGE_XSERVER_XORG_SERVER_MODULAR=y BR2_PACKAGE_XSERVER_XORG_SERVER_AIGLX=y BR2_PACKAGE_XAPP_TWM=y
BR2_PACKAGE_XAPP_XCLOCK=y BR2_PACKAGE_XDRIVER_XF86_INPUT_EVDEV=y BR2_PACKAGE_XDRIVER_XF86_INPUT_KEYBOARD=y BR2_PACKAGE_XDRIVER_XF86_INPUT_MOUSE=y BR2_PACKAGE_XDRIVER_XF86_VIDEO_ARMSOC=y BR2_PACKAGE_XDRIVER_XF86_VIDEO_FBDEV=y BR2_PACKAGE_XTERM=y
BR2_PACKAGE_PYTHON=y
BR2_PACKAGE_PYTHON_BZIP2=y BR2_PACKAGE_PYTHON_READLINE=y BR2_PACKAGE_PYTHON_SSL=y BR2_PACKAGE_PYTHON_PYEXPAT=y BR2_PACKAGE_PYTHON_ZLIB=y
BR2_PACKAGE_LIBDRI2=y
BR2_PACKAGE_LIBDRM_EXYNOS=y
BR2_PACKAGE_LIBGLEW=y
BR2_PACKAGE_LIBGLU=y
BR2_PACKAGE_WAYLAND=y
BR2_PACKAGE_OPENSSH=y
BR2_PACKAGE_RSYNC=y

Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

https://bugs.busybox.net/show_bug.cgi?id=8206

--- Comment #1 from Thomas Petazzoni <[email protected]> 2015-07-07 15:43:01 UTC --- What exact errors is "mplayer" giving you?

Can you attach the part of the build log related to mplayer (i.e all parts that are surrounded by ">>> mplayer ..." lines) ?

Buildroot tries as much as possible to not be influenced by things available on the host machine. However, since the builds are not done inside a chroot, we cannot guarantee 100% that things installed on your host machine will not influence the build in a subtle way.

Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

https://bugs.busybox.net/show_bug.cgi?id=8206

Bernd Kuhls <[email protected]> changed:

What |Removed |Added
----------------------------------------------------------------------------
AssignedTo|unassigned at buildroot.uclibc |bernd.kuhls at t-online.de
|.org |

Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

https://bugs.busybox.net/show_bug.cgi?id=8206

--- Comment #2 from Bernd Kuhls <[email protected]> 2015-07-07 21:00:59 UTC --- Please try this patch: http://patchwork.ozlabs.org/patch/492595/

Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

https://bugs.busybox.net/show_bug.cgi?id=8206

Bernd Kuhls <[email protected]> changed:

What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED

Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

https://bugs.busybox.net/show_bug.cgi?id=8206

Thomas Petazzoni <[email protected]> changed:

What |Removed |Added
----------------------------------------------------------------------------

             Status|ASSIGNED                    |RESOLVED
         Resolution|                            |FIXED

--- Comment #3 from Thomas Petazzoni <[email protected]> 2015-07-10 23:10:04 UTC --- Should be fixed by
http://git.buildroot.net/buildroot/commit/?id=df8bfa3f8c0c825655fac68a22b6b95039c5bd14.
Thanks Bernd!

Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

to: bugzilla at busybox.net
date: Tue, Jul 7, 2015 at 7:11 PM
subject: Re: [Bug 8206] mplayer uses host xorg development files
mailed-by: gmail.com

Hello Thomas,

I am not familiar with the specific log you are asking for, but I searched the entire buildroot dir with:
buildroot-2015.05$ grep -r ">> mplayer" ./
I got no hits. Is there a logging configuration I may not have turn on ? Beware I am fairly new to BuildRoot ~3mo. experience.

- What exact errors is "mplayer" giving you?

I'll have to apt-get remove xorg-dev on another system. to rebuild a bad mplayer that generates the errors. I'll get them to you asap.

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

to: bugzilla at busybox.net
date: Tue, Jul 7, 2015 at 9:30 PM
subject: Re: [Bug 8206] mplayer uses host xorg development files
mailed-by: gmail.com

Thomas & Bernd,

It is rather easy to reproduce the bad mplayer build.
if I remove the xorg-dev packages then make mplayer-dirclean, make mplayer-reinstall
I get a bad mplayer. see attached "console_log_bad_mplayer_execute.txt" if I then install xorg-dev packages and make mplayer-dirclean, make mplayer-reinstall
I get a good mplayer. see attached "console_log_good_mplayer_rebuild.txt" It appears I am not generating the build log that Thomas was asking for, so I've made console logs of the good and bad builds of mplayer. These logs are also attached:
"console_log_good_mplayer_rebuild.txt" "console_log_bad_mplayer_rebuild.txt"

When I remove xorg-dev these packages are contained in xorg-dev apt-get remove --purge xorg-dev then apt-get autoremove
the following packages are removed:
Removing libdmx-dev:amd64 (1:1.1.3-1) ...
Removing libdmx1:amd64 (1:1.1.3-1) ...
Removing xserver-xorg-dev (2:1.17.1-0ubuntu3) ...
Removing mesa-common-dev:amd64 (10.5.2-0ubuntu1) ...
Removing libdrm-dev:amd64 (2.4.60-2) ...
Removing libxft-dev (2.3.2-1) ...
Removing libfontconfig1-dev:amd64 (2.11.1-0ubuntu6) ...
Removing libexpat1-dev:amd64 (2.1.0-6ubuntu1) ...
Removing libxfont-dev (1:1.4.99.901-1ubuntu1) ...
Removing libfontenc-dev:amd64 (1:1.1.2-1) ...
Removing libfreetype6-dev:amd64 (2.5.2-2ubuntu3) ...
Removing libfs-dev:amd64 (2:1.0.6-1) ...
Removing libfs6:amd64 (2:1.0.6-1) ...
Removing libxaw7-dev:amd64 (2:1.0.12-2) ...
Removing libxmu-dev:amd64 (2:1.1.2-1) ...
Removing libxt-dev:amd64 (1:1.1.4-1) ...
Removing libsm-dev:amd64 (2:1.2.2-1) ...
Removing libice-dev:amd64 (2:1.0.9-1) ...
Removing libmirclient-dev:amd64 (0.12.1+15.04.20150324-0ubuntu1) ... Removing libmircommon-dev:amd64 (0.12.1+15.04.20150324-0ubuntu1) ... Removing libpciaccess-dev:amd64 (0.13.2-3build1) ...
Removing libpixman-1-dev (0.32.6-3) ...
Removing libpng12-dev:amd64 (1.2.51-0ubuntu3) ...
Removing libprotobuf-dev:amd64 (2.6.1-1) ...
Removing libprotobuf-lite9:amd64 (2.6.1-1) ...
Removing libxxf86vm-dev:amd64 (1:1.1.3-1) ...
Removing libxxf86dga-dev:amd64 (2:1.1.4-1) ...
Removing libx11-doc (2:1.6.2-2ubuntu2) ...
Removing libxcomposite-dev (1:0.4.4-1) ...
Removing libxcursor-dev:amd64 (1:1.1.14-1) ...
Removing libxdamage-dev:amd64 (1:1.1.4-2) ...
Removing libxvmc-dev:amd64 (2:1.0.8-2ubuntu1) ...
Removing libxv-dev:amd64 (2:1.0.10-1) ...
Removing libxtst-dev:amd64 (2:1.2.2-1) ...
Removing libxi-dev (2:1.7.4-1) ...
Removing libxfixes-dev:amd64 (1:5.0.1-2) ...
Removing libxinerama-dev:amd64 (2:1.1.3-1) ...
Removing libxkbcommon-dev (0.4.3-2) ...
Removing libxkbfile-dev:amd64 (1:1.0.8-1) ...
Removing libxmuu-dev:amd64 (2:1.1.2-1) ...
Removing libxmu-headers (2:1.1.2-1) ...
Removing libxpm-dev:amd64 (1:3.5.11-1) ...
Removing libxrandr-dev:amd64 (2:1.4.2-1) ...
Removing libxrender-dev:amd64 (1:0.9.8-1build1) ...
Removing libxres-dev (2:1.0.7-1) ...
Removing libxss-dev:amd64 (1:1.2.2-1) ...
Removing x11proto-bigreqs-dev (1:1.1.2-1) ...
Removing x11proto-composite-dev (1:0.4.2-2) ...
Removing x11proto-xf86dga-dev (2.1-3) ...
Removing x11proto-xf86bigfont-dev (1.2.0-3) ...
Removing x11proto-damage-dev (1:1.2.1-2) ...
Removing x11proto-dmx-dev (1:2.3.1-2) ...
Removing x11proto-dri2-dev (2.8-2) ...
Removing x11proto-dri3-dev (1.0-1) ...
Removing x11proto-fixes-dev (1:5.0-2ubuntu2) ...
Removing x11proto-fonts-dev (2.1.3-1) ...
Removing x11proto-gl-dev (1.4.17-1) ...
Removing x11proto-present-dev (1.0-1) ...
Removing x11proto-randr-dev (1.4.0+git20120101.is.really.1.4.0-0ubuntu1) ... Removing x11proto-record-dev (1.14.2-1) ...
Removing x11proto-render-dev (2:0.11.1-2) ...
Removing x11proto-resource-dev (1.2.0-3) ...
Removing x11proto-scrnsaver-dev (1.2.2-1) ...
Removing x11proto-video-dev (2.3.2-1) ...
Removing x11proto-xcmisc-dev (1.2.2-1) ...
Removing x11proto-xf86dri-dev (2.1.1-2) ...
Removing x11proto-xf86vidmode-dev (2.3.1-2) ...
Removing x11proto-xinerama-dev (1.2.1-2) ...
Removing zlib1g-dev:amd64 (1:1.2.8.dfsg-2ubuntu1) ...
Removing libxext-dev:amd64 (2:1.3.3-1) ...
Removing x11proto-xext-dev (7.3.0-1) ...
Removing libx11-dev:amd64 (2:1.6.2-2ubuntu2) ...
Removing libxcb1-dev:amd64 (1.10-2ubuntu1) ...
Removing libpthread-stubs0-dev:amd64 (0.3-4) ...
Removing libxau-dev:amd64 (1:1.0.8-1) ...
Removing libxdmcp-dev:amd64 (1:1.1.1-1build1) ...
Removing x11proto-input-dev (2.3.1-1) ...
Removing x11proto-kb-dev (1.0.6-2) ...
Removing xtrans-dev (1.3.5-1) ...
Removing x11proto-core-dev (7.0.26-1) ...
Removing xorg-sgml-doctools (1:1.11-1) ...
Processing triggers for man-db (2.7.0.2-5) ...
Processing triggers for libc-bin (2.21-0ubuntu4) ...
Processing triggers for doc-base (0.10.6) ...
Processing 3 removed doc-base files...

console_log_bad_mplayer_execute.txt
<http://buildroot-busybox.2317881.n4.nabble.com/file/n105280/console_log_bad_mplayer_execute.txt>
console_log_bad_mplayer_rebuild.txt
<http://buildroot-busybox.2317881.n4.nabble.com/file/n105280/console_log_bad_mplayer_rebuild.txt>
console_log_good_mplayer_execute.txt
<http://buildroot-busybox.2317881.n4.nabble.com/file/n105280/console_log_good_mplayer_execute.txt>
console_log_good_mplayer_rebuild.txt
<http://buildroot-busybox.2317881.n4.nabble.com/file/n105280/console_log_good_mplayer_rebuild.txt>

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

to: bugzilla at busybox.net
date: Thu, Jul 9, 2015 at 9:46 PM
subject: Re: [Bug 8206] mplayer uses host xorg development files
mailed-by: gmail.com

Bernd,

I applied your patch and "make mplayer-reinstall" without the host's xorg-dev installed.
still same issue.

I was not sure of the proper way to apply the patch within the buildroot env.
So I applied it manually. What is the proper way to patch a <package>.mk? I did not think it would go into the package/0007-Add-additional-X11-dependencies.patch.

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

Hello,

You have a Bugzilla account since you report a bug, so please re-open
https://bugs.busybox.net/show_bug.cgi?id=8206, and fill in those details in the bug tracker itself.

Thanks,

Thomas

Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

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.

No, you have to apply it directly to the buildroot tree:

cd <buildroot-dir>
patch -p1 < <patchfile>

Regards,
Arnout

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

https://bugs.busybox.net/show_bug.cgi?id=8206

--- Comment #4 from glscantlen <[email protected]> 2015-07-11 15:25:21 UTC --- Created attachment 6106
--> https://bugs.busybox.net/attachment.cgi?id=6106
console log when executing the "bad" mplayer

Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

So that doesn't solve the issue then?

Well, looking at the patch, it can't fix the issue because a 'make
mplayer-dirclean; make mplayer' run wouldn't change anything that this patch does...

Back to Bernd :-)

Regards,
Arnout

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

https://bugs.busybox.net/show_bug.cgi?id=8206

--- Comment #5 from Bernd Kuhls <[email protected]> 2015-07-11 15:38:21 UTC --- Quoting
http://thread.gmane.org/gmane.comp.lib.uclibc.buildroot/119274/focus=119720

console_log_bad_mplayer_rebuild.txt
<http://buildroot-busybox.2317881.n4.nabble.com/file/n105280/console_log_bad_mplayer_rebuild.txt>

console_log_good_mplayer_rebuild.txt
<http://buildroot-busybox.2317881.n4.nabble.com/file/n105280/console_log_good_mplayer_rebuild.txt>

It is clearly visible that mplayer, without my patch posted in this bug report, picked up xorg headers from the host. I could reproduce the behaviour from console_log_bad_mplayer_rebuild.txt, which is fixed with my patch.

Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

Dear Arnout Vandecappelle,

Basically, the mplayer X11 support assumes that the user will enable all the relevant X.org libraries to make things work. While probably, it should be doing more of "select BR2_PACKAGE_<blah> if BR2_PACKAGE_XORG7" so that if X.org has been enabled, mplayer automatically enables the necessary libraries.

Best regards,

Thomas

Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

But that doesn't explain why it _works_ when these packages are present _on the
host_...

I also noticed that Xorg terminates in the bad case - before mplayer is even
started.

Regards,
Arnout

Arnout Vandecappelle      arnout dot vandecappelle at essensium dot com
Senior Embedded Software Architect . . . . . . +32-478-010353 (mobile)
Essensium, Mind division . . . . . . . . . . . . . . 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

https://bugs.busybox.net/show_bug.cgi?id=8206

glscantlen <[email protected]> changed:

What |Removed |Added
----------------------------------------------------------------------------

             Status|RESOLVED                    |REOPENED
         Resolution|FIXED                       |

--- Comment #6 from glscantlen <[email protected]> 2015-07-11 16:07:51 UTC --- Developers were not aware of failures and further testing because gmail replies were being dropped without notification.

Information provided by additional testing:

date:    Tue, Jul 7, 2015 at 9:30 PM
subject:    Re: [Bug 8206] mplayer uses host xorg development files

mailed-by: gmail.com

Thomas & Bernd,

It is rather easy to reproduce the bad mplayer build.
if I remove the xorg-dev packages then make mplayer-dirclean, make mplayer-reinstall
I get a bad mplayer. see attached "console_log_bad_mplayer_execute.txt" if I then install xorg-dev packages and make mplayer-dirclean, make mplayer-reinstall
I get a good mplayer. see attached "console_log_good_mplayer_rebuild.txt" It appears I am not generating the build log that Thomas was asking for, so I've made console logs of the good and bad builds of mplayer. These logs are also attached:
"console_log_good_mplayer_rebuild.txt" "console_log_bad_mplayer_rebuild.txt"

When I remove xorg-dev these packages are contained in xorg-dev apt-get remove --purge xorg-dev then apt-get autoremove
the following packages are removed:
Removing libdmx-dev:amd64 (1:1.1.3-1) ...
Removing libdmx1:amd64 (1:1.1.3-1) ...
Removing xserver-xorg-dev (2:1.17.1-0ubuntu3) ...
Removing mesa-common-dev:amd64 (10.5.2-0ubuntu1) ...
Removing libdrm-dev:amd64 (2.4.60-2) ...
Removing libxft-dev (2.3.2-1) ...
Removing libfontconfig1-dev:amd64 (2.11.1-0ubuntu6) ...
Removing libexpat1-dev:amd64 (2.1.0-6ubuntu1) ...
Removing libxfont-dev (1:1.4.99.901-1ubuntu1) ...
Removing libfontenc-dev:amd64 (1:1.1.2-1) ...
Removing libfreetype6-dev:amd64 (2.5.2-2ubuntu3) ...
Removing libfs-dev:amd64 (2:1.0.6-1) ...
Removing libfs6:amd64 (2:1.0.6-1) ...
Removing libxaw7-dev:amd64 (2:1.0.12-2) ...
Removing libxmu-dev:amd64 (2:1.1.2-1) ...
Removing libxt-dev:amd64 (1:1.1.4-1) ...
Removing libsm-dev:amd64 (2:1.2.2-1) ...
Removing libice-dev:amd64 (2:1.0.9-1) ...
Removing libmirclient-dev:amd64 (0.12.1+15.04.20150324-0ubuntu1) ... Removing libmircommon-dev:amd64 (0.12.1+15.04.20150324-0ubuntu1) ... Removing libpciaccess-dev:amd64 (0.13.2-3build1) ...
Removing libpixman-1-dev (0.32.6-3) ...
Removing libpng12-dev:amd64 (1.2.51-0ubuntu3) ...
Removing libprotobuf-dev:amd64 (2.6.1-1) ...
Removing libprotobuf-lite9:amd64 (2.6.1-1) ...
Removing libxxf86vm-dev:amd64 (1:1.1.3-1) ...
Removing libxxf86dga-dev:amd64 (2:1.1.4-1) ...
Removing libx11-doc (2:1.6.2-2ubuntu2) ...
Removing libxcomposite-dev (1:0.4.4-1) ...
Removing libxcursor-dev:amd64 (1:1.1.14-1) ...
Removing libxdamage-dev:amd64 (1:1.1.4-2) ...
Removing libxvmc-dev:amd64 (2:1.0.8-2ubuntu1) ...
Removing libxv-dev:amd64 (2:1.0.10-1) ...
Removing libxtst-dev:amd64 (2:1.2.2-1) ...
Removing libxi-dev (2:1.7.4-1) ...
Removing libxfixes-dev:amd64 (1:5.0.1-2) ...
Removing libxinerama-dev:amd64 (2:1.1.3-1) ...
Removing libxkbcommon-dev (0.4.3-2) ...
Removing libxkbfile-dev:amd64 (1:1.0.8-1) ...
Removing libxmuu-dev:amd64 (2:1.1.2-1) ...
Removing libxmu-headers (2:1.1.2-1) ...
Removing libxpm-dev:amd64 (1:3.5.11-1) ...
Removing libxrandr-dev:amd64 (2:1.4.2-1) ...
Removing libxrender-dev:amd64 (1:0.9.8-1build1) ...
Removing libxres-dev (2:1.0.7-1) ...
Removing libxss-dev:amd64 (1:1.2.2-1) ...
Removing x11proto-bigreqs-dev (1:1.1.2-1) ...
Removing x11proto-composite-dev (1:0.4.2-2) ...
Removing x11proto-xf86dga-dev (2.1-3) ...
Removing x11proto-xf86bigfont-dev (1.2.0-3) ...
Removing x11proto-damage-dev (1:1.2.1-2) ...
Removing x11proto-dmx-dev (1:2.3.1-2) ...
Removing x11proto-dri2-dev (2.8-2) ...
Removing x11proto-dri3-dev (1.0-1) ...
Removing x11proto-fixes-dev (1:5.0-2ubuntu2) ...
Removing x11proto-fonts-dev (2.1.3-1) ...
Removing x11proto-gl-dev (1.4.17-1) ...
Removing x11proto-present-dev (1.0-1) ...
Removing x11proto-randr-dev (1.4.0+git20120101.is.really.1.4.0-0ubuntu1) ... Removing x11proto-record-dev (1.14.2-1) ...
Removing x11proto-render-dev (2:0.11.1-2) ...
Removing x11proto-resource-dev (1.2.0-3) ...
Removing x11proto-scrnsaver-dev (1.2.2-1) ...
Removing x11proto-video-dev (2.3.2-1) ...
Removing x11proto-xcmisc-dev (1.2.2-1) ...
Removing x11proto-xf86dri-dev (2.1.1-2) ...
Removing x11proto-xf86vidmode-dev (2.3.1-2) ...
Removing x11proto-xinerama-dev (1.2.1-2) ...
Removing zlib1g-dev:amd64 (1:1.2.8.dfsg-2ubuntu1) ...
Removing libxext-dev:amd64 (2:1.3.3-1) ...
Removing x11proto-xext-dev (7.3.0-1) ...
Removing libx11-dev:amd64 (2:1.6.2-2ubuntu2) ...
Removing libxcb1-dev:amd64 (1.10-2ubuntu1) ...
Removing libpthread-stubs0-dev:amd64 (0.3-4) ...
Removing libxau-dev:amd64 (1:1.0.8-1) ...
Removing libxdmcp-dev:amd64 (1:1.1.1-1build1) ...
Removing x11proto-input-dev (2.3.1-1) ...
Removing x11proto-kb-dev (1.0.6-2) ...
Removing xtrans-dev (1.3.5-1) ...
Removing x11proto-core-dev (7.0.26-1) ...
Removing xorg-sgml-doctools (1:1.11-1) ...
Processing triggers for man-db (2.7.0.2-5) ...
Processing triggers for libc-bin (2.21-0ubuntu4) ...
Processing triggers for doc-base (0.10.6) ...
Processing 3 removed doc-base files...

Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

Notice:
The logs of good and bad mplayer builds/executes
were taken before the patch was applied.
The ONLY change between the good & bad was the
install/remove of xorg-dev
sorry for the late reply.

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

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" \

--
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.

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

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

https://bugs.busybox.net/show_bug.cgi?id=8206

kenneth <[email protected]> changed:

What |Removed |Added
----------------------------------------------------------------------------

   Attachment #6106|0                           |1

is patch| |

Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

https://bugs.busybox.net/show_bug.cgi?id=8206

--- Comment #7 from Thomas Petazzoni <[email protected]> --- I've submitted a patch to fix this: https://patchwork.ozlabs.org/patch/664684/

You are receiving this mail because:
You are on the CC list for the bug.

https://bugs.busybox.net/show_bug.cgi?id=8206

Thomas Petazzoni <[email protected]> changed:

What |Removed |Added
----------------------------------------------------------------------------

             Status|REOPENED                    |RESOLVED
         Resolution|---                         |FIXED

--- Comment #8 from Thomas Petazzoni <[email protected]> --- Patch applied in
https://git.buildroot.org/buildroot/commit/?id=6ae3ce9585dcbdfd381111aa9d885bc5b46020d4.

You are receiving this mail because:
You are on the CC list for the bug.