All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michel Dänzer" <michel@daenzer.net>
To: Laurent Carlier <lordheavym@gmail.com>
Cc: Heiko Becker <heirecka@exherbo.org>, dri-devel@lists.freedesktop.org
Subject: Re: [ANNOUNCE] libdrm 2.4.94
Date: Mon, 27 Aug 2018 11:38:50 +0200	[thread overview]
Message-ID: <2ae7fa44-42ea-89ea-2b39-63d47f53e9c1@daenzer.net> (raw)
In-Reply-To: <1966883.0QWE3fz6q4@lordh-pc>


[-- Attachment #1.1.1: Type: text/plain, Size: 2003 bytes --]

On 2018-08-24 7:44 p.m., Laurent Carlier wrote:
> 
> 11/15 amdgpu-symbol-check                     FAIL     0.22 s (exit status 1)
> 
> --- command ---
> LANG='en_US.UTF-8' SUDO_GID='0' OLDPWD='/build/libdrm/src' 
> COMMAND_MODE='legacy' USERNAME='builduser' SUDO_COMMAND='/bin/bash -c bash -c 
> cd\ /startdir;\ makepkg\ "$@" -bash --syncdeps --noconfirm --log --holdver --
> skipinteg --install' CFLAGS='-march=x86-64 -mtune=generic -O2 -pipe -fstack-
> protector-strong -fno-plt' USER='builduser' CXXFLAGS='-march=x86-64 -
> mtune=generic -O2 -pipe -fstack-protector-strong -fno-plt' TEXTDOMAINDIR='/
> usr/share/locale' PWD='/build/libdrm/src/build' HOME='/build' 
> TEXTDOMAIN='pacman-scripts' SUDO_USER='root' SUDO_UID='0' MAIL='/var/mail/
> builduser' CHOST='x86_64-pc-linux-gnu' SHELL='/bin/bash' TERM='xterm-256color' 
> SHLVL='3' CPPFLAGS='-D_FORTIFY_SOURCE=2' SOURCE_DATE_EPOCH='1535132201' 
> LOGNAME='builduser' LDFLAGS='-Wl,-O1,--sort-common,--as-needed,-z,relro,-
> z,now' PATH='/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/bin/site_perl:/usr/
> bin/vendor_perl:/usr/bin/core_perl:/usr/bin/site_perl:/usr/bin/vendor_perl:/
> usr/bin/core_perl:/usr/bin/site_perl:/usr/bin/vendor_perl:/usr/bin/core_perl:/
> usr/bin/site_perl:/usr/bin/vendor_perl:/usr/bin/core_perl' MAKEFLAGS='-j9' 
> _='/usr/bin/meson' NM='/usr/bin/nm' /usr/bin/bash /build/libdrm/src/build/../
> libdrm-2.4.94/amdgpu/amdgpu-symbol-check amdgpu/libdrm_amdgpu.so.1.0.0
> --- stdout ---
> amdgpu_find_bo_by_cpu_mapping

Part of the problem here is probably that the *-symbol-check scripts
haven't actually checked anything in an autotools build since commit
4f08bfe96da1 ("*-symbol-check: Don't hard-code nm executable"):

 ../../amdgpu/amdgpu-symbol-check: line 74: -D: command not found
 PASS amdgpu-symbol-check (exit status: 0)


-- 
Earthling Michel Dänzer               |               http://www.amd.com
Libre software enthusiast             |             Mesa and X developer


[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2018-08-27  9:39 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-23 22:37 [ANNOUNCE] libdrm 2.4.94 Kristian H. Kristensen
2018-08-24  5:43 ` Laurent Carlier
2018-08-24 16:19   ` Kristian Høgsberg
2018-08-24  8:13 ` Michel Dänzer
2018-08-24 16:27   ` Kristian Høgsberg
2018-08-24 16:37     ` Michel Dänzer
2018-08-31  8:22       ` Daniel Vetter
2018-08-24 17:44 ` Laurent Carlier
2018-08-27  9:38   ` Michel Dänzer [this message]
2018-08-27 10:03     ` Emil Velikov
2018-08-27 10:06       ` Michel Dänzer

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=2ae7fa44-42ea-89ea-2b39-63d47f53e9c1@daenzer.net \
    --to=michel@daenzer.net \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=heirecka@exherbo.org \
    --cc=lordheavym@gmail.com \
    /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.