similar to: building virt-builder still seems to fail.

Hi, I have been trying to catch up my Debian packages to the current 1.27 branch of libguestfs (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],

If configured with --without-ocaml, the build might fail because the fix added in df5bd5741b37da9cf97d7a76ac2805557aa630db was not active. According to the automake documentation, it should be enough to set BUILT_SOURCES. --- builder/Makefile.am | 10 +--------- 1 file changed, 1 insertion(+), 9 deletions(-) diff --git a/builder/Makefile.am b/builder/Makefile.am index e3d37667b..3c7113eee 100644

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. -pd > On 29 Apr 2020, at 01:17 , Dirk Eddelbuettel <edd at

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 ppc64el (as

* Hilko Bengen: > commit df5bd5741b37da9cf97d7a76ac2805557aa630db > 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. The affected tree is one that had

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

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

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

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

--- src/kernel.ml | 2 ++ src/utils.ml | 2 ++ 2 files changed, 4 insertions(+) diff --git a/src/kernel.ml b/src/kernel.ml index 356ac4b..9b0e8a2 100644 --- a/src/kernel.ml +++ b/src/kernel.ml @@ -30,6 +30,8 @@ let patt_of_cpu host_cpu = | "ppc" | "powerpc" | "powerpc64" -> ["ppc"; "powerpc"; "powerpc64"] |

On 30 April 2020 at 09:11, luke-tierney at uiowa.edu wrote: | On Thu, 30 Apr 2020, Dirk Eddelbuettel wrote: | Maybe I missed something. How is the 'compiler' package involved? See the other email thread; 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

I hate to bother the list with this potentially minor issue but.... I just wonder if it's a symtom of some other problem. Every time I make a call the BT-102, with the latest firmware, she just keeps the LED display lit and the timer counting after hangup. I check the CLI and the hangup is being executed, I certainly was concerned it might be keeping the line open but that doesn't seem

Hi Lists, I currently have the issue of wanting to use emu-system-x86_64 on a ppc64le platform. It is imperative to pass the "-accel tcg,thread=multi” parameter to qemu when starting an instance, as without that, it will only use one thread and hence of limited/no use. The problem is, that libvirt itself, passes “-machine q35,accel=tcg” to qemu, which is a different parameter, that

https://bugzilla.mindrot.org/show_bug.cgi?id=2658 Bug ID: 2658 Summary: Make integrity tests more robust against timeouts Product: Portable OpenSSH Version: 7.4p1 Hardware: Other OS: Linux Status: NEW Severity: enhancement Priority: P5 Component: Regression tests Assignee:

On 4 August 2023 at 00:06, Jeroen Ooms wrote: | On Thu, Aug 3, 2023 at 9:16?PM Vivian Kong <vivkong at ca.ibm.com> wrote: | > | > Hello, | > | > Are there any plans to add R packages for Ubuntu on other architectures in addition to amd64? We are looking for s390x packages as the version from the distro's package manger is 4.2.2. I'm happy to help in any way I can. | |

As you may know, I look after the R package for Debian. My fellow Debianers make me follow a specific protocol -- a so-called "transition" in which all dependent packages on an identified potential breakge are rebuilt under the new (potentially breaking) change. We started adding an r-api-3.4 tag last (major) release. Now it is r-api-3.5 and the transition got started with the green

Getting this error when hitting update. NoMethodError in Article#update You have a nil object when you didn''t expect it! You might have expected an instance of ActiveRecord::Base. The error occured while evaluating nil.update_attributes Source code. def create @article = Article.new(params[:article]) @article.user = @session[''user''] if @article.save

Hi Dirk, thanks for the report. Access to the test system is not necessary, the memory requirements of the byte-code compiler are usually platform-independent and specifically with this package I can reproduce they are very high. We'll have a look what we can do, certainly there should at least be a way to recover and use the uncompiled version when memory allocation fails, this is

Hi all, I'm very close to having a working setup after blundering through a couple of typing errors that cost me several days of my life, with the following config: Samba 3.0.14a as a PDC Suse 9.2 Professional LDAP (eDirectory 8.7.3) passwd backend Idealx scripts Windows XP SP1 I can connect to any of the samba shares just fine using any of the users I've created, from XP and from linux

-----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