search for: ppc64el

The R 4.0.0 package migration on Debian is being held back by a failed build on ppc64el [1]. We can see from the history of builds logs [2] that it used to build, briefly failed, worked again and then failed leading to R 4.0.0's release. (And my bad for missing how the alpha1/alpha2/beta/rc builds failed.) I have however neither changed anything, nor did I ever have to accomodate...

Hi, On Fri, May 23, 2014 at 10:57:31AM -0300, Mauricio Faria de Oliveira wrote: > > The ppc64el port needs klibc's static binaries, like ppc64. This segfaulting is a bug in klibc that needs investigation. > This patch enables the ARCH=ppc64 make env var in debian/rules, in order > for 'debian/patches/ppc64-static.patch' to take effect on ppp64el too. I have no problem to...

...trace and a clue about where it is looping. Diddling optimization options can also sometimes provide a clue. -pd > On 29 Apr 2020, at 01:17 , Dirk Eddelbuettel <edd at debian.org> wrote: > > > The R 4.0.0 package migration on Debian is being held back by a failed build > on ppc64el [1]. We can see from the history of builds logs [2] that it used > to build, briefly failed, worked again and then failed leading to R 4.0.0's > release. (And my bad for missing how the alpha1/alpha2/beta/rc builds failed.) > > I have however neither changed anything, nor did I eve...

...ad; you replied (~ 26 hours ago) to my message adding that "sysdata.rda in 'tools' hanging was wrong". It gets to the next stage, which is 'compiler'. We know by now (thanks to Bryan and Tomas) that src/main/machar.c is the real culprit due to the long double behaviour on ppc64el. I presume 'compiler' calls into platform.c and hence machar.c for calibration or setup. On the Debian side, I just shipped an updated source package which will skip long double support on this platform. That should allow builds to complete, hopefully, so that we can look into get the bu...

...quot;] | "sparc" | "sparc64" -> ["sparc"; "sparc64"] | "amd64" | "x86_64" -> ["amd64"; "x86_64"] + | "parisc" | "parisc64" -> ["hppa"; "hppa64"] + | "ppc64el" -> ["powerpc64le"] | _ when host_cpu.[0] = 'i' && host_cpu.[2] = '8' && host_cpu.[3] = '6' -> ["?86"] | _ when String.length host_cpu >= 5 && String.sub host_cpu 0 5 = "armv7" -> ["armmp&...

Hi maks, Adding Anton in CC (who submitted klibc ppc64le support upstream [1]), in case he can help. >> The ppc64el port needs klibc's static binaries, like ppc64. > > This segfaulting is a bug in klibc that needs investigation. > >> This patch enables the ARCH=ppc64 make env var in debian/rules, in order >> for 'debian/patches/ppc64-static.patch' to take effect on ppp64el too. &...

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA384 Mauricio Faria de Oliveira dixit: >> [...] Effort in making shared binary >> working too is appreciated. It is probably a wrong syscall API. > > Unfortunately I don't find myself in klibc expertise area. I can try, > but maybe it's not the effective way forward (not sure I'd be able to > devote the effort/time

https://bugzilla.mindrot.org/show_bug.cgi?id=3645 Bug ID: 3645 Summary: -fzero-call-used-regs=used detection seems to fail on Linux ppc64el Product: Portable OpenSSH Version: 9.6p1 Hardware: PPC64 OS: Linux Status: NEW Severity: normal Priority: P5 Component: Build system Assignee: unassigned-bugs at mindrot.org Reporter: cjwats...

On Thu, 30 Apr 2020 at 02:49, Dirk Eddelbuettel <edd at debian.org> wrote: > > > On 29 April 2020 at 11:22, peter dalgaard wrote: > | Hum, at least it is not Apple, so maybe you can attach a debugger to the running process? (gdb -p process_id or something like that --- haven't actually done it for a decade). Then at least we can get a stack trace and a clue about where it is

On Thu, 30 Apr 2020, Dirk Eddelbuettel wrote: > > On 30 April 2020 at 09:42, I?aki Ucar wrote: > | On Thu, 30 Apr 2020 at 02:49, Dirk Eddelbuettel <edd at debian.org> wrote: > | > And to keep the list abreast, this appears to be related to the long double > | > issue on powerpc where needed an extra #define to ensure compilation. That > [...] > | Which reminds me

On 29 April 2020 at 11:22, peter dalgaard wrote: | Hum, at least it is not Apple, so maybe you can attach a debugger to the running process? (gdb -p process_id or something like that --- haven't actually done it for a decade). Then at least we can get a stack trace and a clue about where it is looping. Diddling optimization options can also sometimes provide a clue. (Missed this earlier as

On 30 April 2020 at 09:42, I?aki Ucar wrote: | On Thu, 30 Apr 2020 at 02:49, Dirk Eddelbuettel <edd at debian.org> wrote: | > And to keep the list abreast, this appears to be related to the long double | > issue on powerpc where needed an extra #define to ensure compilation. That [...] | Which reminds me that [1] was required for v3.6.2. Could be related? Yes, that is what I refered

...(and uploaded those packages to experimental), but apparently the build was broken for architectures where no native OCaml compiler is available because make wanted to build .cmx files -- see <https://buildd.debian.org/status/package.php?p=libguestfs&suite=experimental>. So far mips[1], ppc64el[2], and s390x[3] builds have failed with the same error. It looks like this commit ,---- | commit a3881445efd04d5fe6da29db8b2d62a30088b9d1 | Author: Richard W.M. Jones <rjones@redhat.com> | Date: Mon Sep 1 22:24:14 2014 +0100 | | Use ocamldep -all option. `---- caused the build to b...

...Author: Richard W.M. Jones <rjones@redhat.com> Date: Tue Apr 29 15:43:20 2014 +0100 builder: Fix parallel builds of index-parse.o. there is a small chance that a build may go wrong with the described symtom, missing "do_parse" symbol. It just happened to me on Debian's ppc64el buildd[1] and I could not reproduce the issue on a ppc64el porterbox -- the whole build worked just fine. Cheers, -Hilko [1] <https://buildd.debian.org/status/fetch.php?pkg=libguestfs&arch=ppc64el&ver=1%3A1.36.6-3&stamp=1506377176&raw=0>

...got started with the green light from the release team last Friday. Now one build failure occurred for one of the (old, effectively litte maintained) RMetrics packages: fBasics. It blows up at the byte-compilation step on at least four (older, smaller) architectures: mips, mipsel, arm64 (ubuntu), ppc64el. More at https://bugs.debian.org/900756 where we also worked out the "solution" of suppressing byte-compilation at installation. Luke, Tomas, ...: Would it help you to get access to such hardware? We may get you some sort of "guest pass" access to porter machines. Else I coul...

...bug? I’m running: # uname -a Linux tiger-v4 5.7.0-1-powerpc64le #1 SMP Debian 5.7.6-1 (2020-06-24) ppc64le GNU/Linux # apt-cache policy libvirt-daemon libvirt-daemon: Installed: 6.5.0-1 Candidate: 6.5.0-1 Version table: *** 6.5.0-1 500 500 http://deb.debian.org/debian testing/main ppc64el Packages # apt-cache policy qemu-system-x86 qemu-system-x86: Installed: 1:5.0-14 Candidate: 1:5.0-14 Version table: *** 1:5.0-14 500 500 http://deb.debian.org/debian testing/main ppc64el Packages Do you need any more information? Feel free to only continue on the list that matters...

https://bugzilla.mindrot.org/show_bug.cgi?id=3673 Bug ID: 3673 Summary: -fzero-call-used-regs=used detection fails on Linux m68k with GCC 13 Product: Portable OpenSSH Version: 9.7p1 Hardware: 68k URL: https://bugs.debian.org/1067243 OS: Linux Status: NEW Severity: normal

...settings", and | there you can select which architectures to build. By default only | amd64 is enabled, but you can enable any from the following: | | AMD x86-64 (amd64) | ARM ARMv8 (arm64) | ARM ARMv7 Hard Float (armhf) | Intel x86 (i386) | PowerPC (powerpc) | PowerPC64 Little-Endian (ppc64el) | IBM System z (s390x) | | Now you just upload the r-base source packages to the PPA and they get | built for all these architectures. You can do this from the command | line, but you can even simply copy them from Michael Rutter's | backports ppa: | | Go to https://launchpad.net/~marutter/...

...tachment.cgi?id=2924&action=edit Make integrity tests more robust against timeouts If the first test in a series for a given MAC happens to modify the low bytes of a packet length, then ssh will time out and this will be interpreted as a test failure. I'm seeing this in practice on Ubuntu ppc64el (e.g. https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-zesty/zesty/ppc64el/o/openssh/20161231_121729_ebc8a@/log.gz). Fortunately there was already an XXX comment indicating what might be going wrong here, and although I haven't been able to...

...een light from the release team last Friday. > > Now one build failure occurred for one of the (old, effectively litte > maintained) RMetrics packages: fBasics. It blows up at the byte-compilation > step on at least four (older, smaller) architectures: mips, mipsel, arm64 > (ubuntu), ppc64el. More at https://bugs.debian.org/900756 where we also > worked out the "solution" of suppressing byte-compilation at installation. > > Luke, Tomas, ...: Would it help you to get access to such hardware? > > We may get you some sort of "guest pass" access to porte...