Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Athaariq Ardhiansyah <buildroot@athaariq.my.id>
Cc: Romain Naour <romain.naour@gmail.com>,
	Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
	buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/glibc: fix fsconfig_command redeclaration bug
Date: Sat, 1 Oct 2022 17:56:15 +0200	[thread overview]
Message-ID: <20221001155615.GA30794@scaer> (raw)
In-Reply-To: <20221001020445.1458953-1-buildroot@athaariq.my.id>

Athaariq, All,

On 2022-10-01 02:05 +0000, Athaariq Ardhiansyah spake thusly:
> Temporary fix for buildroot-specific bug.

How is this a buildroot-specific bug? Can you elaborate on that part? If
it is really a buildroot-related bug, then we want to understand it, and
fix it, not work around it.

> Ideally, we should install linux-headers first then glibc. Is this actually possible on Buildroot?

This is exactly what we are doing already, and for as long as Buildroot
has supported building a glibc-ased toolchain, as the kernel headers are
required to build glibc; see package/glibc/glibc.mk@28:

   26 # Before glibc is configured, we must have the first stage
   27 # cross-compiler and the kernel headers
   28 GLIBC_DEPENDENCIES = host-gcc-initial linux-headers host-bison host-gawk \

> If yes, then we can also fix bug #15021 simultaneously if linux-headers being installed first as possible.

This part does not apply (or makes sense), as linux headers *are*
installed before glibc is even configured.

This issue is really weird, because the glibc commit we are using is
supposed to contain the related fixes:

    $ git los --oneline 2.36-44-g2628500f5dff1dd99c49a09b418b3b1ea3a6b5d3
    2628500f5d m68k: Enforce 4-byte alignment on internal locks (BZ #29537)
    [...]
    3bd3c612e9 Linux: Fix enum fsconfig_command detection in <sys/mount.h>
    bb1e8b0ca9 linux: Fix sys/mount.h usage with kernel headers
    d48813227b linux: Use compile_c_snippet to check linux/mount.h availability

(There are two new commits on the release/2.36/master branch, but they
seem unrelated to the issue:
    76e05613ee (origin/release/2.36/master) stdlib: Fix __getrandom_nocancel type and arc4random usage (BZ #29638)
    227c903587 get_nscd_addresses: Fix subscript typos [BZ #29605]
)

To be noted, and as Thomas noticed, OpenEmbeded is also using a glibc
2.36 commit, and even one older than ours, but they do not seem to have
issues.

So, we'd like to understand why this is causing an issue for us. Hence,
if you could elaborate on the firt part of your message, above, that
would be extermely useful!

Regards,
Yann E. MORIN.

> Signed-off-by: Athaariq Ardhiansyah <buildroot@athaariq.my.id>
> ---
>  .../0002-fsconfig_command-workaround.patch      | 17 +++++++++++++++++
>  1 file changed, 17 insertions(+)
>  create mode 100644 package/glibc/0002-fsconfig_command-workaround.patch
> 
> diff --git a/package/glibc/0002-fsconfig_command-workaround.patch b/package/glibc/0002-fsconfig_command-workaround.patch
> new file mode 100644
> index 0000000000..27dd25b244
> --- /dev/null
> +++ b/package/glibc/0002-fsconfig_command-workaround.patch
> @@ -0,0 +1,17 @@
> +diff --git a/sysdeps/unix/sysv/linux/sys/mount.h b/sysdeps/unix/sysv/linux/sys/mount.h
> +index 19841d0738..43a681d097 100644
> +--- a/sysdeps/unix/sysv/linux/sys/mount.h
> ++++ b/sysdeps/unix/sysv/linux/sys/mount.h
> +@@ -27,11 +27,7 @@
> + #include <stddef.h>
> + #include <sys/ioctl.h>
> + 
> +-#ifdef __has_include
> +-# if __has_include ("linux/mount.h")
> +-#  include "linux/mount.h"
> +-# endif
> +-#endif
> ++#include "linux/mount.h"
> + 
> + 
> + #define BLOCK_SIZE_BITS	10
> -- 
> 2.37.3
> 
> _______________________________________________
> buildroot mailing list
> buildroot@buildroot.org
> https://lists.buildroot.org/mailman/listinfo/buildroot

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 561 099 427 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2022-10-01 15:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-01  2:05 [Buildroot] [PATCH 1/1] package/glibc: fix fsconfig_command redeclaration bug Athaariq Ardhiansyah
2022-10-01 15:56 ` Yann E. MORIN [this message]
     [not found]   ` <84f6447a658a7c5c46852dc84fe5cb1a@athaariq.my.id>
2022-10-02  3:33     ` buildroot
2022-10-02  7:40       ` Yann E. MORIN
2022-10-04  6:59         ` Peter Seiderer
2022-10-04 19:41           ` Peter Seiderer
2022-10-05  2:08         ` 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=20221001155615.GA30794@scaer \
    --to=yann.morin.1998@free.fr \
    --cc=buildroot@athaariq.my.id \
    --cc=buildroot@buildroot.org \
    --cc=romain.naour@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox