All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Waldemar Brodkorb <wbx@openadk.org>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v2] package/evilwm: fix compilation with external toolchains
Date: Fri, 2 Jan 2026 18:20:10 +0100	[thread overview]
Message-ID: <20260102182010.42a16d03@windsurf> (raw)
In-Reply-To: <aMKU_BEQ4TKSd6qq@waldemar-brodkorb.de>

On Thu, 11 Sep 2025 11:23:08 +0200
Waldemar Brodkorb <wbx@openadk.org> wrote:

> Switch to generic-package, as the configure script isn't really a
> autotool generated script. This fixes building evilwm with an
> external toolchain.
> 
> Fixes:
>  - https://autobuild.buildroot.org/results/250/25040ce7e94acf8f92c24db895d7dea081de1d7a
> 
> Signed-off-by: Waldemar Brodkorb <wbx@openadk.org>
> ---
> v1->v2:
>   - add link to autobuilder (suggested by Arnout)
>   - use TARGET_CROSS (suggested by Arnout)
> ---
>  package/evilwm/evilwm.mk | 24 +++++++++++++++++++++++-
>  1 file changed, 23 insertions(+), 1 deletion(-)

Applied to master, thanks.

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2026-01-02 17:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-11  9:23 [Buildroot] [PATCH v2] package/evilwm: fix compilation with external toolchains Waldemar Brodkorb
2026-01-02 17:20 ` Thomas Petazzoni via buildroot [this message]
2026-01-13 19:45 ` Arnout Vandecappelle via buildroot

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=20260102182010.42a16d03@windsurf \
    --to=buildroot@buildroot.org \
    --cc=thomas.petazzoni@bootlin.com \
    --cc=wbx@openadk.org \
    /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.