All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/s390-tools: fix build error due to undefined KMS_PLUGIN_LOCATION
Date: Thu, 22 Apr 2021 23:49:20 +0200	[thread overview]
Message-ID: <20210422234920.0054edd4@windsurf> (raw)
In-Reply-To: <20210324090001.179735-1-egorenar@linux.ibm.com>

Hello Alexander,

On Wed, 24 Mar 2021 10:00:01 +0100
Alexander Egorenkov <egorenar@linux.ibm.com> wrote:

> Fixes the following build error:
> kms.c:44:2: error: #error KMS_PLUGIN_LOCATION must be defined
>    44 | #error KMS_PLUGIN_LOCATION must be defined
>       |  ^~~~~
> /usr/bin/make -C ../..//libutil/ libutil.a
> kms.c: In function ?load_kms_plugin?:
> kms.c:274:5: error: ?KMS_PLUGIN_LOCATION? undeclared (first use in this function)
>   274 |     KMS_PLUGIN_LOCATION, so_name);
>       |     ^~~~~~~~~~~~~~~~~~~
> kms.c:274:5: note: each undeclared identifier is reported only once for each
> function it appears in
> 
> Signed-off-by: Alexander Egorenkov <egorenar@linux.ibm.com>
> ---
>  ...rror-when-the-compiler-flags-are-ove.patch | 51 +++++++++++++++++++
>  1 file changed, 51 insertions(+)
>  create mode 100644 package/s390-tools/0002-zkey-Fix-build-error-when-the-compiler-flags-are-ove.patch

Thanks for the patch. However, another patch doing exactly the same
thing had been posted 2 days before, and has been applied on March 30.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

      reply	other threads:[~2021-04-22 21:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-24  9:00 [Buildroot] [PATCH 1/1] package/s390-tools: fix build error due to undefined KMS_PLUGIN_LOCATION Alexander Egorenkov
2021-04-22 21:49 ` Thomas Petazzoni [this message]

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=20210422234920.0054edd4@windsurf \
    --to=thomas.petazzoni@bootlin.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 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.