From: Eric Anholt <eric@anholt.net>
To: Eric Engestrom <eric.engestrom@imgtec.com>,
dri-devel@lists.freedesktop.org
Cc: Heiko Becker <heirecka@exherbo.org>, Timo Gurr <timo.gurr@gmail.com>
Subject: Re: [PATCH libdrm v2] *-symbol-check: Don't hard-code nm executable
Date: Thu, 22 Feb 2018 15:27:36 -0800 [thread overview]
Message-ID: <877er4r4ev.fsf@anholt.net> (raw)
In-Reply-To: <20180219163533.8943-1-eric.engestrom@imgtec.com>
[-- Attachment #1.1: Type: text/plain, Size: 425 bytes --]
Eric Engestrom <eric.engestrom@imgtec.com> writes:
> From: Heiko Becker <heirecka@exherbo.org>
>
> Helpful if your nm executable has a prefix based on the
> architecture, for example.
>
> Signed-off-by: Heiko Becker <heirecka@exherbo.org>
> Cc: Timo Gurr <timo.gurr@gmail.com>
> [Eric: v2: rebase and add Meson support]
> Signed-off-by: Eric Engestrom <eric.engestrom@imgtec.com>
Reviewed-by: Eric Anholt <eric@anholt.net>
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 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
next prev parent reply other threads:[~2018-02-22 23:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-19 14:34 [Bug 105163] *-symbol-checks hard-code the nm executable bugzilla-daemon
2018-02-19 16:35 ` [PATCH libdrm v2] *-symbol-check: Don't hard-code " Eric Engestrom
2018-02-22 23:27 ` Eric Anholt [this message]
2018-02-23 0:25 ` Emil Velikov
2018-02-23 15:02 ` Eric Engestrom
2018-02-23 15:04 ` Eric Engestrom
2018-02-23 16:56 ` Emil Velikov
2018-02-26 15:18 ` [Bug 105163] *-symbol-checks hard-code the " bugzilla-daemon
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=877er4r4ev.fsf@anholt.net \
--to=eric@anholt.net \
--cc=dri-devel@lists.freedesktop.org \
--cc=eric.engestrom@imgtec.com \
--cc=heirecka@exherbo.org \
--cc=timo.gurr@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox