public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nathan Chancellor <nathan@kernel.org>
To: Jesper Juhl <jesperjuhl76@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Building a allyesconfig kernel fails because macros are being redefined
Date: Sun, 12 Oct 2025 18:24:23 -0700	[thread overview]
Message-ID: <20251013012423.GA331@ax162> (raw)
In-Reply-To: <CAHaCkme7C8LDpWVX8TnDQQ+feWeQy_SA3HYfpyyPNFee_+Z2EA@mail.gmail.com>

On Mon, Oct 13, 2025 at 01:47:54AM +0200, Jesper Juhl wrote:
> My current git HEAD is at  3a8660878839faadb4f1a6dd72c3179c1df56787
> 
> If I do :
>     make mrproper
>     make allyesconfig
>     make -j 33
> it eventually fails with :
> 
> ...
>  INSTALL libsubcmd_headers
>  CALL    scripts/checksyscalls.sh
>  CC [U]  samples/vfs/test-statx
>  CC [U]  samples/watch_queue/watch_test
> In file included from samples/vfs/test-statx.c:23:
> usr/include/linux/fcntl.h:160:9: error: ‘AT_RENAME_NOREPLACE’
> redefined [-Werror]
>  160 | #define AT_RENAME_NOREPLACE     0x0001
>      |         ^~~~~~~~~~~~~~~~~~~
> In file included from samples/vfs/test-statx.c:13:
> /usr/include/stdio.h:171:10: note: this is the location of the
> previous definition
>  171 | # define AT_RENAME_NOREPLACE RENAME_NOREPLACE
>      |          ^~~~~~~~~~~~~~~~~~~
> usr/include/linux/fcntl.h:161:9: error: ‘AT_RENAME_EXCHANGE’ redefined [-Werror]
>  161 | #define AT_RENAME_EXCHANGE      0x0002
>      |         ^~~~~~~~~~~~~~~~~~
> /usr/include/stdio.h:173:10: note: this is the location of the
> previous definition
>  173 | # define AT_RENAME_EXCHANGE RENAME_EXCHANGE
>      |          ^~~~~~~~~~~~~~~~~~
> usr/include/linux/fcntl.h:162:9: error: ‘AT_RENAME_WHITEOUT’ redefined [-Werror]
>  162 | #define AT_RENAME_WHITEOUT      0x0004
>      |         ^~~~~~~~~~~~~~~~~~
> /usr/include/stdio.h:175:10: note: this is the location of the
> previous definition
>  175 | # define AT_RENAME_WHITEOUT RENAME_WHITEOUT
>      |          ^~~~~~~~~~~~~~~~~~

This is a bug in glibc:

https://inbox.sourceware.org/libc-alpha/20250823052706.GA4056405@ax162/
https://sourceware.org/git?p=glibc.git;a=commit;h=1166170d95863e5a6f8121a5ca9d97713f524f49

Cheers,
Nathan

  reply	other threads:[~2025-10-13  1:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-12 23:47 Building a allyesconfig kernel fails because macros are being redefined Jesper Juhl
2025-10-13  1:24 ` Nathan Chancellor [this message]
2025-11-09  7:13 ` [PATCH 0/2] fix AT_RENAME_* redefinitions with glibc < 2.43 Masaharu Noguchi
2025-11-09  7:13   ` [PATCH 1/2] uapi: fcntl: guard AT_RENAME_* aliases Masaharu Noguchi
2025-11-09 16:13     ` David Laight
2025-11-09  7:13   ` [PATCH 2/2] samples: vfs: avoid libc AT_RENAME_* redefinitions Masaharu Noguchi
2025-11-09 16:04     ` David Laight

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=20251013012423.GA331@ax162 \
    --to=nathan@kernel.org \
    --cc=jesperjuhl76@gmail.com \
    --cc=linux-kernel@vger.kernel.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