Buildroot Archive on 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/libedit: fix compile error
Date: Sat, 12 Aug 2023 12:43:56 +0200	[thread overview]
Message-ID: <20230812124356.6dd3e574@windsurf> (raw)
In-Reply-To: <ZNdBDn3B5k1Xgl4S@waldemar-brodkorb.de>

Hello Waldemar,

On Sat, 12 Aug 2023 10:21:34 +0200
Waldemar Brodkorb <wbx@openadk.org> wrote:

> Header file uses ssize_t so sys/types.h must be included.
> 
> Fixes:
>  - http://autobuild.buildroot.net/results/439/439538b23776a58ff81c38754a19ee92c3590a1f
> 
> Signed-off-by: Waldemar Brodkorb <wbx@openadk.org>
> ---
> Author was informed via email about the issue.
> ---
>  package/libedit/0002-add-sys-types_h.patch | 15 +++++++++++++++
>  1 file changed, 15 insertions(+)
>  create mode 100644 package/libedit/0002-add-sys-types_h.patch

I have applied to master, but after significantly improving the commit
log. For all the "fixes" that you send, there is almost always a
critical information that is missing: since when is the problem
occurring. Indeed, we want to know if the fix needs to be backported to
one of our stable branches or not.

So here, I had to do that research myself, to realize it's the version
bump in commit cc69dbf8fdef6619c4ea09a4aaa97cd5ad3ee423 that introduced
the regression. Since this commit is no yet in any release (other than
2023.08-rc1), there is no need to backport your fix to a previous
stable Buildroot branch. This is really a critical piece of information
that Peter Korsgaard will need when reviewing patches for backport to
stable branches.

So could you please always, always, always to this research and include
the relevant information in the commit log? It will make things a lot
easier when reviewing/merging the patches.

The final commit log looks like this:

commit fe42fa8017b10602ed57ee066f8a9710f0f8e7ca (HEAD -> master, official/master)
Author: Waldemar Brodkorb <wbx@openadk.org>
Date:   Sat Aug 12 10:21:34 2023 +0200

    package/libedit: fix compile error with uClibc
    
    In Buildroot commit cc69dbf8fdef6619c4ea09a4aaa97cd5ad3ee423
    ("package/libedit: bump version to 20221030-3.1"), the version of
    libedit was bumped from 20210910-3.1 to 20221030-3.1. This broke the
    build with uClibc:
    
    ./sys.h:96:1: error: unknown type name 'ssize_t'; did you mean 'size_t'?
    
    Header file uses ssize_t so sys/types.h must be included.
    
    This commit adds a patch that fixes this issue.
    
    Fixes:
    
      http://autobuild.buildroot.net/results/439538b23776a58ff81c38754a19ee92c3590a1f
    
    Signed-off-by: Waldemar Brodkorb <wbx@openadk.org>
    Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>

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:[~2023-08-12 10:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-12  8:21 [Buildroot] [PATCH] package/libedit: fix compile error Waldemar Brodkorb
2023-08-12 10:43 ` Thomas Petazzoni via buildroot [this message]
2023-08-12 11:18   ` Waldemar Brodkorb

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=20230812124356.6dd3e574@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox