Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Romain Naour <romain.naour@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] Cannot build glibc for ARM with GCC10
Date: Sat, 27 Jun 2020 23:35:30 +0200	[thread overview]
Message-ID: <2d032ef9-149c-29f2-5311-e21af074fcdd@gmail.com> (raw)
In-Reply-To: <CAGm1_ku8d5Gy5haB5CQow=kntoyboQ5SZBmYUp51kpggjxKZng@mail.gmail.com>

Hi, Yegor, Thomas,

Le 27/06/2020 ? 19:18, Yegor Yefremov a ?crit?:
> Hi Thomas,
> 
> On Sat, Jun 27, 2020 at 4:43 PM Thomas Petazzoni
> <thomas.petazzoni@bootlin.com> wrote:
>>
>> On Fri, 26 Jun 2020 18:51:57 +0200
>> Yegor Yefremov <yegorslists@googlemail.com> wrote:
>>
>>> I just wanted to test GCC10 with glibc and encountered the following error:
>>
>> Did you try with the updated glibc version, provided by the following
>> patch series:
>>
>> https://patchwork.ozlabs.org/project/buildroot/list/?series=182049
> 
> The patch series has solved my problem.

Indeed, glibc 2.30 doesn't contain fixes for gcc 10, only glibc 2.31 build with
gcc 10.

We are up-to-date on the glibc 2.30 stable branch, so even glibc upstream didn't
backported gcc 10 fixes.

I currently backported 6 patches from glibc 2.31 to start fixing the build but
glibc still doesn't build. I'm not sure it's worth the effort... I would suggest
to disable glibc 2.30 with gcc 10.

Best regards,
Romain

> 
> Thanks.
> 
> Regards,
> Yegor
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
> 

      reply	other threads:[~2020-06-27 21:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-26 16:51 [Buildroot] Cannot build glibc for ARM with GCC10 Yegor Yefremov
2020-06-27 14:43 ` Thomas Petazzoni
2020-06-27 17:18   ` Yegor Yefremov
2020-06-27 21:35     ` Romain Naour [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=2d032ef9-149c-29f2-5311-e21af074fcdd@gmail.com \
    --to=romain.naour@gmail.com \
    --cc=buildroot@busybox.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