[Buildroot] [Bug 12631] New: glibc support Power-PC SPE

[Buildroot] [Bug 12631] New: glibc support Power-PC SPE

[bugzilla at busybox.net]

https://bugs.busybox.net/show_bug.cgi?id=12631

            Bug ID: 12631
           Summary: glibc support Power-PC SPE
           Product: buildroot
           Version: 2020.02
          Hardware: Other
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P5
         Component: Outdated package
          Assignee: unassigned at buildroot.uclibc.org
          Reporter: joerg.hering at macgregor.com
                CC: buildroot at uclibc.org
  Target Milestone: ---

Created attachment 8396
  --> https://bugs.busybox.net/attachment.cgi?id=8396&action=edit
PPC Qoriq P2020 config file

hello colleagues,
it is possible in version LTS 2020.02 to additionally maintain glibc support
for Power-PC SPE (glibc 2.28 ...) ? Eventually depend on BR2_powerpc ,
BR2_powerpc_8548 and BR2_POWERPC_SOFT_FLOAT. Our systems are based on Qoriq
P2020 and we use the systemd -> glibc and many other packages (qt ...). It
would be a great pity if we had to stop at LTS 2019.02 . Do you have any
suggestions?

Greetings from germany's biggest island R?gen
J?rg


p.s 
we had already adapted the file 

toolchain/toolchain-buildroot/Config.in 
for our SPE demands

config BR2_TOOLCHAIN_BUILDROOT_GLIBC
        bool "glibc"
        depends on BR2_arm         || BR2_armeb      || BR2_aarch64 || \
                   BR2_aarch64_be  || BR2_i386       || BR2_mips    || \
                   BR2_mipsel      || BR2_mips64     || BR2_mips64el|| \
                   BR2_powerpc     || BR2_powerpc64  || BR2_powerpc64le || \
                   BR2_riscv       || BR2_sh         || BR2_sparc64     || \
                   BR2_x86_64      || BR2_microblaze || BR2_nios2       || \
                   (BR2_arcle && BR2_ARC_ATOMIC_EXT)
        depends on BR2_USE_MMU
        depends on !BR2_STATIC_LIBS
        depends on BR2_TOOLCHAIN_HEADERS_AT_LEAST_3_2
        depends on BR2_TOOLCHAIN_HEADERS_AT_LEAST_3_10 || !BR2_powerpc64le
        depends on BR2_TOOLCHAIN_HEADERS_AT_LEAST_4_5 || !BR2_MIPS_NAN_2008
        depends on !BR2_powerpc_SPE || (BR2_powerpc_SPE &&
BR2_POWERPC_SOFT_FLOAT)
        depends on BR2_RISCV_ISA_RVA || !BR2_riscv

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Buildroot] [Bug 12631] glibc support Power-PC SPE

[bugzilla at busybox.net]

https://bugs.busybox.net/show_bug.cgi?id=12631

--- Comment #1 from romain.naour at gmail.com ---
Hi,

I would recommend to build your toolchain using Buildroot 2019.02.x using the
internal toolchain backend and import the toolchain in Buildroot 2020.02 using
the external toolchain backend.

See "6.1.3. Build an external toolchain with Buildroot"
http://nightly.buildroot.org/manual.html#_cross_compilation_toolchain

But Buildroot doesn't support powerpc-spe since [1] (2014-05-30)

[1]
https://git.buildroot.net/buildroot/commit/?id=5777e3ffd99132a57e3d29659850eec14b1625f8

Note: The powerpc spe has been removed recently from gcc 9 and glibc 2.30.

Best regards,
Romain

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Buildroot] [Bug 12631] glibc support Power-PC SPE

[bugzilla at busybox.net]

https://bugs.busybox.net/show_bug.cgi?id=12631

Thomas Petazzoni <thomas.petazzoni@free-electrons.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |WONTFIX
             Status|NEW                         |RESOLVED

--- Comment #2 from Thomas Petazzoni <thomas.petazzoni@free-electrons.com> ---
Since PowerPC SPE support has been removed from upstream gcc, it doesn't seem
very relevant for Buildroot to start supporting it more widely, as we will have
to remove it in the near future as we upgrade to newer gcc versions.

See
https://github.com/gcc-mirror/gcc/commit/b31d0348ddada49453e3edaaf93a423fdc61dc79

-- 
You are receiving this mail because:
You are on the CC list for the bug.