New architecture ppc64el on Debian

Hi, Now that PowerPC was announced to have Little Endian support, I'd like to enable it on Debian, as a ppc64el architecture. I have been working internally at IBM on a Debian rootfs that runs on this architecture. As a plan, I am looking, in general, to have this architecture included on sid,

Re: New architecture ppc64el on Debian

On 09/21/2013 03:22 PM, Bastian Blank wrote: On Sat, Sep 21, 2013 at 02:42:53PM -0300, Breno Leitao wrote: Now that PowerPC was announced to have Little Endian support, I'd like to enable it on Debian, as a ppc64el architecture. Can you please describe the advantages of this new port

Re: New architecture ppc64el on Debian

On 09/21/2013 03:54 PM, Jan-Benedict Glaw wrote: On Sat, 2013-09-21 14:42:53 -0300, Breno Leitao bren...@br.ibm.com wrote: Now that PowerPC was announced to have Little Endian support, I'd like to enable it on Debian, as a ppc64el architecture. I have been working internally at IBM

Re: New architecture ppc64el on Debian

Hi Bastian, On 09/21/2013 03:22 PM, Bastian Blank wrote: Can you please describe the advantages of this new port? This is going to be part of the OpenPower consortium. This article[1] describe a little bit about the about the architecture. What versions of the Linux kernel, gcc, glibc are

Re: New architecture ppc64el on Debian

On 09/23/2013 11:43 AM, Lennart Sorensen wrote: On Sun, Sep 22, 2013 at 06:08:12PM +0900, Joel Rees wrote: I suppose I'm not really one privileged to express these reactions, but I tend to be a loose cannon sometimes. ??? (Checking my calendar. Nope, I haven't suddenly slipped back to the

Re: New architecture ppc64el on Debian

Hi Hiroyuki, On 09/22/2013 01:05 AM, Hiroyuki Yamamoto wrote: I have been working internally at IBM on a Debian rootfs that runs on this architecture. As a plan, I am looking, in general, to have this architecture included on sid, first, and then being moving towards stable. I think it good

Re: New architecture ppc64el on Debian

Back to this email, I finally got the binaries public, and we are tracking this port on following wiki page: https://wiki.debian.org/ppc64el On 09/21/2013 02:42 PM, Breno Leitao wrote: Hi, Now that PowerPC was announced to have Little Endian support, I'd like to enable it on Debian

Re: Missing packages in the ppc64el unstable repository

Hi Vitor, Thanks for using our ppc64el image. We have been working to enable these components on our public repo, and I believe that most of them are there at the moment. We just added a bunch of new packages over there. On 04/10/2014 04:05 PM, Vitor de Lima wrote: Hi, There are a few

Debian/ppc64el development machine available

Hi, I would like to announce that there is a development machine ready for developers to work on Debian pp64el port. Feel free to ask for an account at: https://wiki.debian.org/ppc64el#Development_machines Thanks Breno -- Breno Leitão -- To UNSUBSCRIBE, email to

ppc64el status

Hi, I would like to report the latest status of the ppc64el port on Debian. A lot of patches were sent to Debian and already integrated into the packages to support ppc64el. We have an internal buildd machine that were able to build around 8K source packages from source (without any additional

Re: Alternative java/JVM working on armel/powerpc?

Hi Rogério, On 07/09/2014 11:13 PM, Rogério Brito wrote: Hi there. I would like to run some programs that require a JVM on alternative platforms, like armel/powerpc (these are arches for which I have hardware running Debian, but others might also be of interest). (Please, feel free to

Re: Debian/ppc64el feasiability to become an official architecture

Hi Peter, Thank you for your reply. On 07/24/2014 08:14 PM, peter green wrote: Note: this is the perspective of a dd who is not directly involved with powerc though I have come across some of your bug reports, nor am I a member of the ftp or release teams. It's probablly mostly right but

Re: Fixing buildd issues on ppc64el

Hi Aurelien, On 08/21/2014 11:26 AM, Aurelien Jarno wrote: On Thu, Aug 21, 2014 at 03:55:49PM +0200, Frédéric Bonnard wrote: Hi all/Aurelien, Hi, I'd like to help fixing issues found during buildd of packages on ppc64el :

Re: Fixing buildd issues on ppc64el

Aurelien, This is a list of the packages that I just mapped to bugs. On 08/24/2014 07:04 PM, Breno Leitao wrote: libg15 - 758539 xfsprogs - 757455 libnfo - 718062 opencore-amr - 755830 libverto - 757953 libranlip - 758031 regina-rexx - 756354 libsigc++-1.2 - 751371 dircproxy - 745154

Re: Fixing buildd issues on ppc64el

Hi Aurelien, On 08/26/2014 12:51 AM, Aurelien Jarno wrote: On Mon, Aug 25, 2014 at 04:12:01PM -0300, Breno Leitao wrote: Aurelien, This is a list of the packages that I just mapped to bugs. Thanks I have imported it. On a slightly related thing, it seems we will need webkitgtk soon

Unique ppc64el virtual machines available for free

Folks, You can be able to get access to a unique ppc64el virtual machine on the openPower mini cloud. This is an easy, free and fast way to have access to the ppc64el unique virtual machine. At the moment, you can request access to have a Debian, Ubuntu and Fedora OS virtual machines.

Re: Alternative java/JVM working on armel/powerpc?

On 09/03/2014 12:36 PM, Lennart Sorensen wrote: On Wed, Sep 03, 2014 at 07:29:50AM -0700, Chris Tillman wrote: I see where powerpc support has been _removed_ from avian on Apr 30: https://github.com/ReadyTalk/avian/commit/41adb74eb1895c662920fdfb7467ce415d9fa0b7 This would explain why it

Re: Fixing buildd issues on ppc64el

hi, On 09/08/2014 09:37 AM, Andreas Barth wrote: mutt #752831 build-dep on gpgme1.0 which ftbfs (libtool) Also fixed. The next major offender seems to be cmake and I am confused about it. For example, a lot of packages doesn-t build because depends on cmake-data, as the package

Re: Fixing buildd issues on ppc64el

Hi Aurelien, On 09/11/2014 12:03 PM, Aurelien Jarno wrote: So powerpc64le-linux-gnu is wrongly detected as elf64ppc (instead of elf64lppc). This value is then passed to ld to check if it supports shared libraries. The above binutils change make this check to succeed. This value is not used

Re: Fixing buildd issues on ppc64el

On 09/12/2014 05:58 AM, Aurelien Jarno wrote: On Thu, Sep 11, 2014 at 04:52:04PM -0300, Breno Leitao wrote: Right. This is going to help all those shared-library-issue bugs to be 'solved'. Btw, did you mark all the failed/build-attempted to rebuild, so, we can find what packages are going

Re: d-i installation manual bits for arm64 and ppc64el

Hi Samuel, On 11/29/2014 10:01 AM, Samuel Thibault wrote: Hello, I can only repeat what I have posted a couple of months ago: we do need documentation in the manual about the arm64 and ppc64el new architectures. I am working on the ppc64el part. If I understand correct, you want to update

Re: d-i installation manual bits for arm64 and ppc64el

Hi Samuel, On 11/29/2014 10:01 AM, Samuel Thibault wrote: Hello, For ppc64el === For now, ppc64el is just like powerpc, I guess it may be useful to distinguish them so as to drop the documentation for elder hardware? en/hardware/hardware-supported.xml will have to be updated. At

Re: python3.4 test results on ppc64el

Hi Mathias, On 12/04/2014 07:08 AM, Matthias Klose wrote: Please see https://buildd.debian.org/status/fetch.php?pkg=python3.4arch=ppc64elver=3.4.2-3stamp=1417544125 failing the test_signal and test_tar tests. I assume this is some buildd setup issue, but would like to have the ppc64el

Re: python3.4 test results on ppc64el

Hi Doko, On 12/04/2014 03:37 PM, Breno Leitao wrote: Hi Mathias, On 12/04/2014 07:08 AM, Matthias Klose wrote: Please see https://buildd.debian.org/status/fetch.php?pkg=python3.4arch=ppc64elver=3.4.2-3stamp=1417544125 failing the test_signal and test_tar tests. I assume this is some

Re: d-i installation manual bits for arm64 and ppc64el

Hi, On 12/04/2014 03:14 PM, Breno Leitao wrote: Hi Samuel, On 11/29/2014 10:01 AM, Samuel Thibault wrote: Hello, For ppc64el === For now, ppc64el is just like powerpc, I guess it may be useful to distinguish them so as to drop the documentation for elder hardware? en/hardware

Re: wanted: old G5 hardware for use on the ppc64 port

Hi Konstantinos, Thanks for being interested in it. I am also willing to help. Why not using a remote VM on a new POWER machine hosted at Unicamp? You have been doing so using the IBM POWER mini cloud[1], and the mini cloud will continue to exist for long. In fact, the minicloud has some idle

porterbox (pastel) is now bigger

Hi, I would like to announce that ppc64el porterbox (pastel) is much bigger now, I just resized the disk to have a plenty of more space, added more CPUs (16 cores in total) and added 128Gb of memory, so, things should compile much faster there now. OTOH, If you still want a private Debian VM

Re: qemu-system-ppc64: usb kbd not working

hi Konstantinos, On 03/04/2015 11:14 AM, Konstantinos Margaritis wrote: Hi all, Tried to boot some ppc64 d-i image that I created for testing[1], and can't get past the language chooser, as usb kbd doesn't seem to be working on qemu-system-ppc64. The input buffer seems to fill quickly and

Re: LXQT

Hi Herminio, On 05/08/2015 01:18 PM, Herminio Hernandez, Jr. wrote: I just watch an Lubuntu talk on LXQT development and was wonder when would we see this in Debian? Can anyone tell me if it is Sid or experimental for PowerPC? Would someone need to install from source? Any help would be

Re: Help with the arm64 and ppc64el installation-guides needed

Hi Samuel, On 04/10/2015 07:24 PM, Samuel Thibault wrote: Hello, Breno Leitao, le Fri 10 Apr 2015 17:44:01 -0300, a écrit : On 04/09/2015 01:13 PM, Karsten Merker wrote: Hello everybody, the release date for Jessie is near, but the installation-guide does not seem to contain any arm64

Re: Help with the arm64 and ppc64el installation-guides needed

hi Karsten, On 04/09/2015 01:13 PM, Karsten Merker wrote: Hello everybody, the release date for Jessie is near, but the installation-guide does not seem to contain any arm64/ppc64el-specific information yet. We have created this installation guide, but unfortunatelly it was not integrated

Re: ppc64 and ppc64el virtual machines available for developers

Hi Mathieu, On 06/11/2015 10:31 AM, Mathieu Malaterre wrote: Could you please clarify this statement ? sudo is not installed on the machine and password for root is not in sync with the user setup (AFAIK). Are you saying that you have access to a VM on this cloud and there is no 'sudo'

ppc64 and ppc64el virtual machines available for developers

, Breno Leitao wrote: Folks, You can be able to get access to a unique ppc64el virtual machine on the openPower mini cloud. This is an easy, free and fast way to have access to the ppc64el unique virtual machine. At the moment, you can request access to have a Debian, Ubuntu and Fedora OS

PowerPC notebooks

It seems a new a new 4-core 64-bits PPC laptop is coming. It will be using a Freescale e6500 processor. http://www.powerpc-notebook.org/en/ This processor is based on V2.06 ISA, but it is still not clear for me if only PPC64 is supported, or, if ppc64el might run on these machines.

Re: Debian/ppc64el images being tested daily

Hello, On 06/02/2016 03:50 PM, Programmingkid wrote: > When you install is done, do you see a login screen that is just a > command-line, or do you see a display manager with a login prompt? We just see the command line after the installation is done, i.e, we do not have a X window running in

Re: Debian/ppc64el images being tested daily

On 06/03/2016 10:46 AM, Lennart Sorensen wrote: > On Fri, Jun 03, 2016 at 12:28:53AM -0400, Programmingkid wrote: >> I was wondering if someone could change the PowerPC KDE iso so it can have a >> display manager running at startup by default. They are a lot easier to use >> than a command-line.

Re: ppc64el netinst will not boot

Hello, On 06/06/2016 12:52 AM, Herminio Hernandez Jr. wrote: > I agree. > > Sent from my iPhone > >> On Jun 5, 2016, at 7:44 PM, Programmingkid wrote: >> >> >>> On Jun 5, 2016, at 10:35 PM, Lennart Sorensen wrote: >>> On Fri, Jun 03, 2016 at 05:40:10PM -0400,

Re: Debian/ppc64el images being tested daily

Hello, On 06/03/2016 06:37 PM, Programmingkid wrote: > > On Jun 3, 2016, at 12:35 PM, Breno Leitao wrote: > >> On 06/03/2016 10:46 AM, Lennart Sorensen wrote: >>> On Fri, Jun 03, 2016 at 12:28:53AM -0400, Programmingkid wrote: >>>> I was wondering if someone

Debian/ppc64el images being tested daily

We created an infrastructure, called Daily Automation Tool, that tests ppc64el images on Power environments. It downloads the daily images (testing and stretch), and install it on a KVM guest, PowerVM LPAR and Bare metal (Bare metal is still not fully functional). The automation tool also

POWER8-based Desktop machine

Just found on the web: Talos™ is the world's first ATX workstation-class mainboard for the new, open-source friendly IBM POWER8 processor and architecture. Raptor Engineering's Talos™ Secure Workstation brings unparalleled performance, security, and user control to the desktop. Designed for

POWER8 machine at OCP

There is a new POWER8 machine design at OCP under Open Compute Project Hardware License (OCPHL-P). The Open Compute Project (OCP) is a collaborative community focused on redesigning hardware technology to efficiently support the growing demands on compute infrastructure. This machine is named

Re: PPC64 port status

Hi, On 03/30/2016 02:13 PM, wbon...@theitmakers.com wrote: >> Do you mean setting "-mno-altivec" as a generic compiler flag for ppc64? > > Yes, that's what i mean. "-mno-altivec" and maybe some other "-mno-something" > flags, so it could run on any PPC64 cpu, even if it does not have >

Re: [RFC] dietlibc port to ppc64el

Hi Christian, On 04/04/2016 07:57 PM, Christian Seiler wrote: > Yeah, so CC='klcc' means that this mksh was built against klibc instead > of dietlibc. CC='diet gcc' or CC='diet cc' would indicate dietlibc... > So you just verified that mksh with klibc works. :-) Silly me. When I tried to but

Re: [RFC] dietlibc port to ppc64el

Hi Christian, On 04/06/2016 04:57 PM, Christian Seiler wrote: >> Do you know this problem? Is it related to something like: >> >> https://github.com/ensc/dietlibc/blob/87a59f2e6dc11d9f5b82c9d6eff09aae2daa1bbb/ppc64/setjmp.S#L3-L7 > > I believe I have fixed that recently independently of your

Re: Adding more ppc64 buildds from the POWER cloud

Hello Adrian, On 04/04/2016 06:57 PM, John Paul Adrian Glaubitz wrote: As long as Breno is fine with the fact, there is nothing from Debian's side that is going to stop you ;-). I don't see a problem also. By the way, the machine is now ready and you have sudo in the machine. Feel free to do

Re: [RFC] dietlibc port to ppc64el

Hi Christian, On 04/03/2016 04:36 PM, Christian Seiler wrote: > May be built via gbp buildpackage. If needed, I can also provide a .dsc > file if necessary. I tried to built it on my ppc64el machine using: $ git clone https://anonscm.debian.org/git/collab-maint/dietlibc.git -b ports/ppc64el

Re: Adding more ppc64 buildds from the POWER cloud

Hello Adrian, On 04/02/2016 06:53 PM, John Paul Adrian Glaubitz wrote: > Since I think that the buildds for the ppc64 (Big Endian) port are a bit > underpowered and actually have to rebuild the whole archive now (due > to the fact they want rebuild everything with Altivec disabled), I was >

Re: [RFC] dietlibc port to ppc64el

Hi Christian, On 04/03/2016 06:54 PM, Christian Seiler wrote: Is there another way to test it? Well, you can just compile any number of standard programs (that don't require external libraries) with it. Just use diet in front of gcc, e.g. Right. This is working fine. No problem found

Re: PPC64 port status

Hi Mathieu, On 03/30/2016 05:40 AM, Mathieu Malaterre wrote: >> So i would like to know what is the target, and if it is >> possible to consider supporting the "most generic PPC64 target", just >> like it is done for x86 archs ? Do you mean setting "-mno-altivec" as a generic compiler flag for

Re: PPC64 port status

Hi Lennart, On 03/30/2016 11:30 AM, Lennart Sorensen wrote: > Certainly. And getting access to one of the ones that causes trouble > by not having VMX seems even harder in fact. I am wondering if you cannot try to mimic this non-VMX CPU on QEMU using -cpu. Running "$ qemu-system-ppc -cpu

Re: Adding more ppc64 buildds from the POWER cloud

hi Adrian, On 04/03/2016 06:35 PM, John Paul Adrian Glaubitz wrote: Since the POWER8 machines are very powerful, it would probably make sense to create multiple buildd instances on the single cloud instance but that depends on the availability of cores and memory. Ok, since we will not even

Re: Performance difference 32bit/64bit userland

On 02/08/2017 12:08 PM, Mathieu Malaterre wrote: > On Wed, Feb 8, 2017 at 2:21 PM, Breno Leitao <bren...@br.ibm.com> wrote: >> On 02/07/2017 07:22 PM, Lennart Sorensen wrote: >>> ppc64el is different since it is targeting systems where the applications >>>

Re: Performance difference 32bit/64bit userland

Hi Adrian, On 02/08/2017 11:41 AM, John Paul Adrian Glaubitz wrote: > On 02/08/2017 02:21 PM, Breno Leitao wrote: >> Correct. And we can't do 32-bits userspace also, since we do not have a >> 32-bits little endian ABI. For ppc64el, bi-arch does not seem to be a valid >> fea

Re: Performance difference 32bit/64bit userland

On 02/07/2017 07:22 PM, Lennart Sorensen wrote: > ppc64el is different since it is targeting systems where the applications > are expected to need a lot of ram, and switching the little endian > improves performance when working with GPUs (which are all designed > for the x86 little endian world).

FTBFS on ppc64el

I would like to announce a small page we created to track the current packages that FTBFS on ppc64el. It also shows if the package only FTBFS on ppc64el, or if it FTBFS on other arches as well. As a bonus, we have a historical view of FTBFS in ppc64el.

Re: ppc64el porter situation

Hello Adrian, Let me share my view as the only DD listed as ppc64el porter. On Mon, Oct 17, 2016 at 10:50:01PM +0300, Adrian Bunk wrote: > Is a DM enough, if the only DD gets killed by a car [2] the day after > the release of stretch? The other DM is in the process of becoming a DD[1]. This

Re: ppc64(el) failure, haskell-zeromq4-haskell, Error: operand out of domain (2 is not a multiple of 4)

Hello Clint, On 11/12/2016 01:39 PM, Clint Adams wrote: > Hi Breno, > > It's unclear how to contact the ppc64el porters. Is there a mailing > list? Yes. We use the debian-powerpc mailing list. I am copying them to this email. > Something appears to have broken with GHC's PPC64 code

Re: QEMU ppc64el SIGILL in mkfs

On 11/23/2016 03:43 PM, Lennart Sorensen wrote: > On Wed, Nov 23, 2016 at 04:56:03PM +, Clint Adams wrote: >> I'm trying to install Debian within qemu-system-ppc64 using >> debian-stretch-DI-alpha8-ppc64el-netinst.iso >> >> Attempting to make a filesystem (either ext4 or btrfs) fails >> and

Re: QEMU ppc64el SIGILL in mkfs

On 11/23/2016 10:18 PM, Clint Adams wrote: > On Wed, Nov 23, 2016 at 12:43:49PM -0500, Lennart Sorensen wrote: >> Running qemu-system-ppc64 -cpu POWER8 (version 1:2.7+dfsg-3+b1) did not >> fail for me using debian-testing-ppc64el-netinst.iso > > Yes, indeed. I have no idea what the default is,

Debian/ppc64 available at Minicloud

Hello, Yesterday, at MiniDebConf Curitiba 2017, we announced that our free "POWER Minicloud" has support and images available for ppc64 port, besides the traditional ppc64el. The naming scheme is a little bit weird, but Debian 8 BE means ppc64, and LE means ppc64el.

Re: Bug#866122: slapd-mtread crash on ppc64{,el} in stretch/sid

hi Ryan, On 07/11/2017 02:58 AM, Ryan Tandy wrote: > Today I built Linux 4.12 from upstream source and the test program still > crashes. I was looking at your fixes to initialize load_{fp,tm,vec} as well > as someone else fixing the CONFIG_ALIVEC typo but none of those have helped. Right, I

Re: slapd-mtread crash on ppc64{,el} in stretch/sid

Ryan, > Nice. I was able to reproduce it and debug it further. The problem seems > to be related to a invalid branch/jump, the the next address is not > memory mapped, thus the segfault. The new address is completely random, > and definitely is wrong. I think I found the real case of the

Re: slapd-mtread crash on ppc64{,el} in stretch/sid

hi Ryan, On Sun, Jul 09, 2017 at 08:56:59AM -0700, Ryan Tandy wrote: > There seems to be a regression on powerpc64 (both endians) that can corrupt > the vector-scalar registers (VSRs) in a threaded program. > > I believe the bad commit is this one: > > 4.9.0: >

Re: slapd-mtread crash on ppc64{,el} in stretch/sid

Hey Adrian, On Thu, Jul 06, 2017 at 10:44:21PM +0200, John Paul Adrian Glaubitz wrote: > Hi Breno! > > On 07/06/2017 09:31 PM, Breno Leitao wrote: > > I think I found the real case of the problem here. There is an array > > being allocated, and initialized until 'i'. &

Re: slapd-mtread crash on ppc64{,el} in stretch/sid

Hi Ryan, On Mon, Jul 03, 2017 at 03:39:35PM -0700, Ryan Tandy wrote: > Hi debian-powerpc, > > Would a ppc64(el) porter be able to help me look at #866122? I have > requested a porterbox account but it's not gone through yet, and I am unable > to reproduce the issue at all in a qemu VM. You can

Re: Bootstrapped fpc for ppc64el

Hey Adrian, On 05/29/2017 06:17 PM, John Paul Adrian Glaubitz wrote: > Hi Debian Pascal team! > > I have just bootstrapped fpc for ppc64el, it can be downloaded from [1]. Nice. I just downloaded it an try to remember how to do some Pascal coding. Really nice to see fpc working on ppc64el.

Re: Bug#881772: ruby2.5: FTBFS on ppc64(el): stack level too deep

patch fixes the issue. commit aa11d386528bbeb0f138962b3073b01319e85678 Author: Breno Leitao <lei...@debian.org) Date: Mon Nov 27 10:47:00 2017 -0500 stack: align to 64kb This is a workaround for ppc64el which uses 64kb page size. This align the stack to the page size. It

Re: Bug#881772: ruby2.5: FTBFS on ppc64(el): stack level too deep

Hi Terceiro, On 11/15/2017 02:32 PM, Antonio Terceiro wrote: > Hi, > > On Tue, Nov 14, 2017 at 06:16:22PM -0500, Aaron M. Ucko wrote: >> Source: ruby2.5 >> Version: 2.5.0~preview1-1 >> Severity: important >> Tags: upstream >> Justification: fails to build from source >> User:

Re: Bug#881772: ruby2.5: FTBFS on ppc64(el): stack level too deep

) UNRELEASED; urgency=medium + + * Fixed FTBFS on ppc64el (Closes: 881772). + + -- Breno Leitao <lei...@debian.org> Tue, 05 Dec 2017 06:46:16 -0500 + ruby2.5 (2.5.0~preview1-1) unstable; urgency=medium [ Antonio Terceiro ] diff --git a/debian/patches/0006-Fix-FTBFS-on-ppc64el.patch b/debian/p

Re: Arch qualification for buster: call for DSA, Security, toolchain concerns

Hi Niels, On 06/27/2018 05:03 PM, Niels Thykier wrote: > List of concerns for architectures > == > > The following is a summary from the current architecture qualification > table. > > * Concern for ppc64el and s390x: we are dependent on sponsors for >

Re: Help needed for small assembler script for the iraf package

Just to keep this thread up to date, this discussion moved to githut, where Rogério, Gustavo and I experienced some ideas and created a proposed solution. https://github.com/leitao/zsvjmp On 01/04/2018 08:16 AM, Ole Streicher wrote: > Dear powerpc specialists, > > I just got the "IRAF"

Re: no quadmath.h on ppc64 ?

On 04/04/2018 07:01 PM, Dennis Clarke wrote: > So there we see "--disable-libquadmath --disable-libquadmath-support". This is also disabled on ppc64el and it should be enabled, so, put both ppc64 and ppc64el on your bug, please. Since ppc64 supports float128 I suppose this should be enabled by

Re: no quadmath.h on ppc64 ?

Hi Dennis, On 04/04/2018 03:31 PM, Dennis Clarke wrote: > > > Silly question. I tried to test a bit of _Float128 datatype stuff and so >  I installed the only libquadmath lib I could find. > > nix$ dpkg -L libquadmath0-ppc64el-cross Are you using ppc64 or ppc64el? This package you listed

Re: FTBFS on ppc64el

hi Erwan, On 10/23/2018 09:00 AM, Erwan Prioul wrote: > On Thu, 16 Feb 2017 16:49, Breno Leitao wrote: >> I would like to announce a small page we created to track the current >> packages that FTBFS on ppc64el. >> >> It also shows if the package only FTBFS on ppc64el,