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] package/dc3dd: fix compile issues
Date: Wed, 14 Aug 2024 23:42:33 +0200	[thread overview]
Message-ID: <20240814234233.3eb8f179@windsurf> (raw)
In-Reply-To: <Zrtc85Eh/rXEpune@waldemar-brodkorb.de>

Waldemar,

On Tue, 13 Aug 2024 15:17:39 +0200
Waldemar Brodkorb <wbx@openadk.org> wrote:

> Add a patch from Debian to fix the autobuild issues.
> Furthermore something like ea2f52494c32c53a3def6dc3b0c5b9d5d7c7edf4
> from cvs package is required as well.
> 
> Fixes:
>  - http://autobuild.buildroot.net/results/6a0/6a0c5dc057eb348afcd5e3859cb37059d6bd91c1
> 
> Signed-off-by: Waldemar Brodkorb <wbx@openadk.org>
> ---
>  ...e.y-compile-on-QNX-and-NetBSD-5-i386.patch | 104 ++++++++++++++++++
>  package/dc3dd/dc3dd.mk                        |   2 +
>  2 files changed, 106 insertions(+)
>  create mode 100644 package/dc3dd/0004-Make-getdate.y-compile-on-QNX-and-NetBSD-5-i386.patch

Thanks for the investigation, I've applied to master. But here as well,
I would have _really_ preferred a deeper explanation: what was causing
the build issue (which configurations?), and since when the issue
existed? Could you try to add this kind of information for the next
build fixes?

Thanks a lot!

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:[~2024-08-14 21:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-13 13:17 [Buildroot] [PATCH] package/dc3dd: fix compile issues Waldemar Brodkorb
2024-08-14 21:42 ` Thomas Petazzoni via buildroot [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=20240814234233.3eb8f179@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.