From: Waldemar Brodkorb <wbx@openadk.org>
To: Arnout Vandecappelle <arnout@rnout.be>
Cc: Bernd Kuhls <bernd@kuhls.net>,
buildroot@uclibc.org, Vincent Stehle <vincent.stehle@laposte.net>
Subject: Re: [Buildroot] HPPA fails to build , was: Analysis of build errors, was: Re: [autobuild.buildroot.org] Daily results for 2026-05-08
Date: Mon, 18 May 2026 20:17:00 +0200 [thread overview]
Message-ID: <agtXnGstcPCbQEyK@waldemar-brodkorb.de> (raw)
In-Reply-To: <82c062f9-6151-4363-8344-f0fdba96f032@rnout.be>
Hi Arnout,
Arnout Vandecappelle via buildroot wrote,
> Hi Vincent,
>
> On 09/05/2026 09:00, Bernd Kuhls wrote:
> > > glibc-2.43-22-g8362e8ce10b2... | 2
> > fails only on hppa, no upstream fix in sight, what about reverting
> > 1822f07e94951c5a37f78c1009d54fc95d01d39c?
>
> Since glibc is the only libc for HP-PA, I think this means we'll have to
> throw out HP-PA entirely. Or do you see a solution?
That is not entirely true :). uClibc-ng has support for HP-PA, but only
static support no ld.so support.
best regards
Waldemar
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2026-05-18 18:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <69fea782.050a0220.8af99.ac9e__38452.1139830881$1778296731$gmane$org@mx.google.com>
2026-05-09 7:00 ` [Buildroot] Analysis of build errors, was: Re: [autobuild.buildroot.org] Daily results for 2026-05-08 Bernd Kuhls
2026-05-18 18:05 ` [Buildroot] HPPA fails to build , was: " Arnout Vandecappelle via buildroot
2026-05-18 18:17 ` Waldemar Brodkorb [this message]
2026-05-18 20:31 ` Arnout Vandecappelle via buildroot
2026-05-19 21:33 ` Vincent Stehlé via 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=agtXnGstcPCbQEyK@waldemar-brodkorb.de \
--to=wbx@openadk.org \
--cc=arnout@rnout.be \
--cc=bernd@kuhls.net \
--cc=buildroot@uclibc.org \
--cc=vincent.stehle@laposte.net \
/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