From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Charlie Jenkins <charlie@rivosinc.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] package/lmbench: Fix dependency discovery
Date: Sat, 19 Apr 2025 23:25:29 +0200 [thread overview]
Message-ID: <20250419232529.0f2de3d8@windsurf> (raw)
In-Reply-To: <20250410-fix_lmbench_dependency_discovery-v1-1-c86c22674010@rivosinc.com>
On Thu, 10 Apr 2025 13:38:38 -0700
Charlie Jenkins <charlie@rivosinc.com> wrote:
> lmbench dependency discovery relies on implicit return types for main().
> This causes compiler errors when -Wimplicit-int is enabled. The failure
> of the dependcy discovery causes lmbench to redifine typedefs the
> compiler already has in an incompatible manner. Add a patch to fix the
> discovery.
>
> Fixes:
> bench.h:81:13: error: conflicting types for ‘socklen_t’; have ‘int’
> 81 | typedef int socklen_t;
>
> bench.h:85:15: error: conflicting types for ‘off64_t’; have ‘int64’ {aka ‘long long int’}
> 85 | typedef int64 off64_t;
>
> Signed-off-by: Charlie Jenkins <charlie@rivosinc.com>
> ---
> .../0006-scripts-build-int-return-type-main.patch | 203 +++++++++++++++++++++
> 1 file changed, 203 insertions(+)
Applied to master after adding an Upstream: tag. 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
prev parent reply other threads:[~2025-04-19 21:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-10 20:38 [Buildroot] [PATCH] package/lmbench: Fix dependency discovery Charlie Jenkins
2025-04-19 21:25 ` 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=20250419232529.0f2de3d8@windsurf \
--to=buildroot@buildroot.org \
--cc=charlie@rivosinc.com \
--cc=thomas.petazzoni@bootlin.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 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.