All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Leonid Yuriev <leo@yuriev.ru>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [autobuild.buildroot.net] Your daily results for 2022-10-10
Date: Wed, 12 Oct 2022 11:36:34 +0200	[thread overview]
Message-ID: <20221012113634.1ae5d496@windsurf> (raw)
In-Reply-To: <14ff4a72-41f4-256c-aaa9-b1948391ba6d@yuriev.ru>

Hello Leonid,

On Tue, 11 Oct 2022 14:11:10 +0300
Leonid Yuriev <leo@yuriev.ru> wrote:

> Please fix the configuration error of toolchain for microblaze arch.
> 
> I already wrote about this problem at the beginning of the summer, and 
> then changed the diagnostic message to make the error more obvious.
> 
> Basically, the failed assertion (see below) checks that the width of 
> l_start end l_len fields of the struct flock are enough to hold values 
> of off_t type.
> So, the libc in the toolchain is misconfigured or/and has wrong layout 
> of headers, etc.

This particular configuration was built using the glibc C library. If
you believe there is a bug in glibc, I would suggest to fill in a bug
report at https://sourceware.org/bugzilla/.

Thanks for your help with this!

Thomas
-- 
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      reply	other threads:[~2022-10-12  9:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20221011084540.jebe33uW@myt6-3efb34da3dd5.qloud-c.yandex.net>
2022-10-11 11:11 ` [Buildroot] [autobuild.buildroot.net] Your daily results for 2022-10-10 Leonid Yuriev
2022-10-12  9:36   ` Thomas Petazzoni via buildroot [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=20221012113634.1ae5d496@windsurf \
    --to=buildroot@buildroot.org \
    --cc=leo@yuriev.ru \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.