Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v4 2/2] package/x11r7/xdriver_xf86-video-nouveau: new package
Date: Sat, 19 Dec 2015 15:56:47 +0100	[thread overview]
Message-ID: <20151219155647.0a4ca4b8@free-electrons.com> (raw)
In-Reply-To: <1450534925-9099-2-git-send-email-bernd.kuhls@t-online.de>

Dear Bernd Kuhls,

On Sat, 19 Dec 2015 15:22:05 +0100, Bernd Kuhls wrote:
> Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de>
> ---
> v2: no changes

I've applied, but it triggers a kconfig warning (which already existed
for some other packages):

warning: (BR2_PACKAGE_MESA3D_GALLIUM_DRIVER_NOUVEAU && BR2_PACKAGE_MESA3D_DRI_DRIVER_NOUVEAU && BR2_PACKAGE_XDRIVER_XF86_VIDEO_NOUVEAU) selects BR2_PACKAGE_LIBDRM_NOUVEAU which has unmet direct dependencies (BR2_PACKAGE_LIBDRM && (BR2_i386 || BR2_x86_64))

So it already existed for BR2_PACKAGE_MESA3D_GALLIUM_DRIVER_NOUVEAU and
BR2_PACKAGE_MESA3D_DRI_DRIVER_NOUVEAU, and your package
(BR2_PACKAGE_XDRIVER_XF86_VIDEO_NOUVEAU) just adds a new bogus select.
I've still applied your package because this issue needs to be fixed
separately, and address for all three Config.in options.

Essentially, this happens because I'm building on ARM, and the
BR2_PACKAGE_LIBDRM_NOUVEAU option is only available on i386 and x86_64.
However, I wonder why BR2_PACKAGE_LIBDRM_NOUVEAU is not available on
ARM, since I'm pretty sure that the Nouveau driver is used on ARM on
some Tegra platforms.

Right now, this causes a build failure:

checking for LIBDRM_NOUVEAU... no
configure: error: Package requirements (libdrm_nouveau >= 2.4.25) were not met:

With the following (not very minimal) configuration:

BR2_arm=y
BR2_TOOLCHAIN_EXTERNAL=y
BR2_TOOLCHAIN_EXTERNAL_CUSTOM=y
BR2_TOOLCHAIN_EXTERNAL_DOWNLOAD=y
BR2_TOOLCHAIN_EXTERNAL_URL="http://autobuild.buildroot.org/toolchains/tarballs/br-arm-full-2015.11-rc1-71-g90d1299.tar.bz2"
BR2_TOOLCHAIN_EXTERNAL_GCC_4_7=y
BR2_TOOLCHAIN_EXTERNAL_HEADERS_3_10=y
BR2_TOOLCHAIN_EXTERNAL_LOCALE=y
# BR2_TOOLCHAIN_EXTERNAL_HAS_THREADS_DEBUG is not set
BR2_TOOLCHAIN_EXTERNAL_INET_RPC=y
BR2_TOOLCHAIN_EXTERNAL_CXX=y
BR2_INIT_NONE=y
BR2_SYSTEM_BIN_SH_NONE=y
# BR2_PACKAGE_BUSYBOX is not set
BR2_PACKAGE_MESA3D=y
BR2_PACKAGE_MESA3D_DRI_DRIVER_SWRAST=y
BR2_PACKAGE_XORG7=y
BR2_PACKAGE_XSERVER_XORG_SERVER=y
BR2_PACKAGE_XDRIVER_XF86_VIDEO_NOUVEAU=y
BR2_PACKAGE_LIBGLFW=y
BR2_PACKAGE_LIBSOIL=y
# BR2_TARGET_ROOTFS_TAR is not set

Can you have a look?

Thanks!

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

  reply	other threads:[~2015-12-19 14:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-19 14:22 [Buildroot] [PATCH v4 1/2] package/x11r7/xserver_xorg-server: bump version to 1.18.0 Bernd Kuhls
2015-12-19 14:22 ` [Buildroot] [PATCH v4 2/2] package/x11r7/xdriver_xf86-video-nouveau: new package Bernd Kuhls
2015-12-19 14:56   ` Thomas Petazzoni [this message]
2015-12-19 16:57     ` [Buildroot] [PATCH v4 2/2]package/x11r7/xdriver_xf86-video-nouveau:new package Bernd Kuhls
2015-12-19 14:53 ` [Buildroot] [PATCH v4 1/2] package/x11r7/xserver_xorg-server: bump version to 1.18.0 Thomas Petazzoni

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=20151219155647.0a4ca4b8@free-electrons.com \
    --to=thomas.petazzoni@free-electrons.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