All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: Romain Naour <romain.naour@gmail.com>
Cc: Guo Ren <ren_guo@c-sky.com>, buildroot <buildroot@buildroot.org>
Subject: Re: [Buildroot] csky 8xx toolchain issue
Date: Sat, 2 Oct 2021 20:25:34 +0200	[thread overview]
Message-ID: <20211002202534.40ca92ee@windsurf> (raw)
In-Reply-To: <6d635d7e-e88a-3b23-9682-a19ff3d08b7d@gmail.com>

Hello Romain,

On Sat, 2 Oct 2021 17:58:24 +0200
Romain Naour <romain.naour@gmail.com> wrote:

> The csky toolchain is still broken with recent host compiler and our CI will
> switch to Debian bullseye soon.
> 
> I tried to build with the latest upstream version of binutils, gcc and glibc and
> nothing build.
> 
> upstream gcc-11 doesn't support csky610 and csky860 needed for
> qemu_csky610_virt_defconfig and qemu_csky860_virt_defconfig.
> 
> qemu_csky807_virt_defconfig and qemu_csky810_virt_defconfig fail to build glibc
> with the following error:
> 
> glibc-2.34-9-g9acab0bba6a5a57323b1f94bf95b21618a9e5aa4/build/elf/librtld.os: in
> function `__sync_fetch_and_add_2':
> 
> build/host-gcc-initial-11.2.0/build/csky-buildroot-linux-gnuabiv2/libgcc/../../../libgcc/config/csky/linux-atomic.c:116:
> undefined reference to `__kernel_cmpxchg'
> 
> But even if the build succeeded there is no qemu binary to do a runtime test.

Considering these issues and the fact that there has been no updates in
terms of C-SKY support for a long time, I think we should consider
dropping support for the C-SKY CPU architecture.

Best regards,

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:[~2021-10-02 18:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-26 19:39 [Buildroot] csky 8xx toolchain issue Romain Naour
2021-08-26 21:59 ` Arnout Vandecappelle
2021-10-02 15:58   ` Romain Naour
2021-10-02 18:25     ` Thomas Petazzoni [this message]
2021-10-02 20:21       ` Romain Naour
2021-10-02 20:34         ` Yann E. MORIN
2021-10-02 20:44           ` Romain Naour

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=20211002202534.40ca92ee@windsurf \
    --to=thomas.petazzoni@bootlin.com \
    --cc=buildroot@buildroot.org \
    --cc=ren_guo@c-sky.com \
    --cc=romain.naour@gmail.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.