From: Charlie Jenkins <charlie@rivosinc.com>
To: Julien Olivain <ju.o@free.fr>
Cc: buildroot@buildroot.org, Eric Le Bihan <eric.le.bihan.dev@free.fr>
Subject: Re: [Buildroot] [PATCH] package/linux-pam: bump to version 1.7.0
Date: Wed, 2 Apr 2025 11:36:41 -0700 [thread overview]
Message-ID: <Z-2DuYT4ymI3vNBn@ghost> (raw)
In-Reply-To: <f0605945c9018fab7218ae831b193b3b@free.fr>
On Tue, Apr 01, 2025 at 09:00:07PM +0200, Julien Olivain wrote:
> Hi Charlies,
>
> Thanks for the patch.
>
> On 01/04/2025 04:57, Charlie Jenkins wrote:
> > Bump to latest version. Remove patch included in release and fixup the
> > configure options due to linux-pam migrating to the Meson build system.
> >
> > Signed-off-by: Charlie Jenkins <charlie@rivosinc.com>
> [...]
> > diff --git a/package/linux-pam/linux-pam.mk
> > b/package/linux-pam/linux-pam.mk
> > index 23b09efbaea6a148924bc0eb7721e6cbec7f8e6b..4f18a12c2059e70498ecb0adb1b23dff2fa04388
> > 100644
> > --- a/package/linux-pam/linux-pam.mk
> > +++ b/package/linux-pam/linux-pam.mk
> > @@ -4,17 +4,15 @@
> > #
> > ################################################################################
> >
> > -LINUX_PAM_VERSION = 1.6.1
> > +LINUX_PAM_VERSION = 1.7.0
>
> This new version seems to introduce new build failures. See: [1]
>
> Apparently, setting BR2_PACKAGE_LINUX_PAM_LASTLOG=y requires a libc
> with the logwtmp() function. Maybe this option should depends on !musl.
> See for example [2].
>
> Also, the bootlin-microblazeel-uclibc toolchain is failing. It seems
> to be due to linker warnings to be treated as errors. Maybe a fix
> like [3] should be added.
>
> Could you have a look to those issues and send an updated patch,
> please?
Thanks! There's a third problem I am not sure how to resolve. The
problem is:
<path to buildroot>/output/host/opt/ext-toolchain/bin/../lib/gcc/microblazeel-buildroot-linux-uclibc/13.3.0/../../../../microblazeel-buildroot-linux-uclibc/bin/ld: FDE encoding in <path to buildroot>/output/host/opt/ext-toolchain/bin/../lib/gcc/microblazeel-buildroot-linux-uclibc/13.3.0/libgcc.a(_umoddi3.o)(.eh_frame) prevents .eh_frame_hdr table being created
Do you know how to resolve this?
- Charlie
>
> Best regards,
>
> Julien.
>
> [1] https://gitlab.com/jolivain/buildroot/-/pipelines/1747133176
> [2] https://gitlab.com/buildroot.org/buildroot/-/commit/14532e4fc6e02a755b30e634fd60f53b92655bcd
> [3] https://gitlab.com/buildroot.org/buildroot/-/commit/132eec5c47f5f9542d0c2e93d12341d624627de0
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2025-04-02 18:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-01 2:57 [Buildroot] [PATCH] package/linux-pam: bump to version 1.7.0 Charlie Jenkins
2025-04-01 19:00 ` Julien Olivain
2025-04-02 18:36 ` Charlie Jenkins [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=Z-2DuYT4ymI3vNBn@ghost \
--to=charlie@rivosinc.com \
--cc=buildroot@buildroot.org \
--cc=eric.le.bihan.dev@free.fr \
--cc=ju.o@free.fr \
/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