Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Andreas Ziegler <br015@umbiko.net>
To: Fiona Klute <fiona.klute@gmx.de>
Cc: buildroot <buildroot@buildroot.org>
Subject: Re: [Buildroot] [autobuild.buildroot.org] Daily results for 2025-06-14
Date: Tue, 17 Jun 2025 07:15:51 +0000	[thread overview]
Message-ID: <756d3a2cab51640ce9e3f6730120cbe1@umbiko.net> (raw)
In-Reply-To: <mailman.38047.1750071190.2108631.buildroot@buildroot.org>

Hi Fiona, everyone

On 2025-06-16 12:53, Fiona Klute wrote:

> Hi everyone,
> 
> you might've noticed there are a lot of autobuild failures for
> host-gobject-introspection errors recently. One example:
> https://autobuild.buildroot.org/results/b9904209e13c1e4ce496aaff2f194064d2a6c691/

I noticed a dramatic increase in autobuild errors, probably since May 02 
[1].

>  From the error messages it looks like *something* links against system
> libreadline, which then links against libncursesw from host-ncurses
> (probably due to the LD_LIBRARY_PATH override), isn't fully compatible,
> and then the warning
> 
>> /bin/sh: 
>> /home/autobuild/autobuild/instance-22/output-1/host/lib/libncursesw.so.6: 
>> no version information available (required by 
>> /usr/lib/libreadline.so.8)
> 
> somehow ends up in the linker command line (which seems like a bug in
> itself, probably in in GOI, regardless of library paths).

I suspect an error in the autobuild routine itself, but am neither 
familiar with the actual setup nor where the autobuild code is located, 
so am unable to confirm this.

> My problem is that I can't reproduce the issue, and without that I 
> don't
> see how I can figure out where exactly things go wrong. I tried on my
> regular build system, and also with the
> registry.gitlab.com/buildroot.org/buildroot/base:20250218.2110 image,
> and both built host-gobject-introspection just fine with config from 
> the
> linked autobuild run (and a few others I've tried).

With your example, I get an error building host-rust _before_ 
host-gobject-introspection is reached, while running 'make 
host-gobject-introspection' the task completes without an error.

In the past, reproduction of autobuild errors on my own build system was 
fairly consistent.

> Does anyone else have an idea, or a suggestion how to replicate the
> autobuild environment (because there must be some difference if it
> consistently fails there, but not with the container)?

> Best regards,
> Fiona

Kind regards,
Andreas

<cut>

[1] https://marc.info/?l=buildroot&m=174661114911988&w=2
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

       reply	other threads:[~2025-06-17  7:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.38047.1750071190.2108631.buildroot@buildroot.org>
2025-06-17  7:15 ` Andreas Ziegler [this message]
2025-06-15  3:14 [Buildroot] [autobuild.buildroot.org] Daily results for 2025-06-14 Buildroot Notifications
2025-06-16 10:53 ` Fiona Klute via buildroot
2026-08-17  9:13   ` Franciszek Stachura

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=756d3a2cab51640ce9e3f6730120cbe1@umbiko.net \
    --to=br015@umbiko.net \
    --cc=buildroot@buildroot.org \
    --cc=fiona.klute@gmx.de \
    /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