similar to: qemu-user-static: mis-emulates something to do with process/signal handling (m68k, s390x, …)

On Tue, 2022-02-01 at 16:23 +0000, Thorsten Glaser wrote: > retitle 925358 qemu-user-static: mis-emulates something to do with process/signal handling (m68k, s390x, ?) > affects 925358 klibc-dev > thanks > > This still happens. (And retitling because I almost filed a bug > against klibc again? oops?) > > Look for ?mtest-external? (second occurrence) in: >

Dixi quod? >Builtins work fine, calling external programmes does >not. It seems to hang in jobs.c:j_waitj() and sending >it SIGCHLD seems to not trigger jobs.c:j_sigchld() >at all. This is probably some kind of signals being >not delivered correctly ? see here for a bug with the >same symptoms: http://dev.haiku-os.org/ticket/5567 >http://dev.haiku-os.org/changeset/35836 >

Hi, after a year, I decided to hack on klibc again. I?ve reworked both the patch to add mkstemp(), discussing to use AT_RANDOM as cheap entropy source on IRC (if there will ever be another entropy consumer, I can quickly write a minimal arc4random() seeded from it, as it has only 16 octets), capable of making a working mksh (static and shared) on amd64/xen, and the m68k support code, leading to

Hello, I'm trying to port RPL/2 (http://www.rpl2.net) to OS/2 and I don't understand OS/2 semget(). RPL/2 uses POSIX semaphores. I have written a minimal library that emulates POSIX semaphores with SysV ones. I have tested this library on several Unix systems without any trouble. On OS/2, semget() always returns -1 and I don't understand my mistake. int sem_init_SysV(sem_t

I work for a multi-billion dollar international organization currently using Novell technology for F&P/Directory/etc... A project has just arisen to develop several potential replacement proofs of concept. Several solutions are being evaluated, including: * Microsoft CIFS * Some NAS device using AD or eDirectory * Linux/Samba I was chosen as part of the Linux/Samba team and I'd like to

Hi, http://programmers-blog.com/2010/12/21/quick-start-to-seo-for-ruby-on-rails What do you think about this guys? I looked through the whole Internet ;) and found nothing simple that would suit my simple needs. So I did these things on my own and wrote about the process. Thanks for any comments! Regards, M&W. -- Posted via http://www.ruby-forum.com/. -- You received this message

Hello all. I have a question about setting up samba to serve windows printing. I have been trying to research this but keep coming up with conflicting howto's. Can someone give me directions to an up-to-date print howto? It would be greatly appreciated as I am stuck on this. Cheers, Tony -- ------------------------------- Tony Ricker Technology Coordinator SLUCare - P.M.O. St. Louis

Hi, after changing mksh to no longer use mkstemp, I decided to try and build mksh-static with klcc on most platforms, in Debian. Here are the results by Debian architecture: alpha (4) fails amd64 works armel works armhf (3) fails i386 works ia64 works m68k (1) workaround mips works mipsel works powerpc (2) fails ppc64 works (!) s390 works s390x works sparc works Architectures not listed either

Binary distributions of R-0.49 for NEXTSTEP (Intel and M68k) are now available on CRAN: http://www.ci.tuwien.ac.at/R/bin/i386-nextstep/R.0.49.I.b.tar.gz http://www.ci.tuwien.ac.at/R/bin/m68k-nextstep/R.0.49.N.b.tar.gz Because NEXTSTEP doesn't support dynamic loading, I've compiled in a number of additional functions (mostly from the user contributed section of CRAN) which I find

found by Christian T. Steigies <cts@debian.org> usr/klibc/arch/m68k/crt0.o: In function `_start': usr/klibc/arch/m68k/crt0.S:(.text+0xe): undefined reference to `___libc_init' too many '_'. never seen jbsr, converted that to jsr. Signed-off-by: maximilian attems <maks@sternwelten.at> diff --git a/usr/klibc/arch/m68k/crt0.S b/usr/klibc/arch/m68k/crt0.S index

found by Christian T. Steigies <cts@debian.org> usr/include/arch/m68k/klibc/archstat.h:12: error: syntax error before '__dev64' better use __stdev64 defined in klibc/stathelp.h Signed-off-by: maximilian attems <maks@sternwelten.at> diff --git a/usr/include/arch/m68k/klibc/archstat.h b/usr/include/arch/m68k/klibc/archstat.h index 89c0341..dce25f9 100644 ---

On Wed, Jan 15, 2014 at 9:26 AM, Michael S. Tsirkin <mst at redhat.com> wrote: > As a result of backporting a bugfix, virtio_net started passing void * > to page_address, assuming that it will get silently converted to struct > page *. But this does not happen on architectures where page_address is > a macro, the result is build failure as the macro tries to dereference >

On Wed, Jan 15, 2014 at 9:46 AM, Michael S. Tsirkin <mst at redhat.com> wrote: > On Wed, Jan 15, 2014 at 09:36:13AM +0100, Geert Uytterhoeven wrote: >> On Wed, Jan 15, 2014 at 9:26 AM, Michael S. Tsirkin <mst at redhat.com> wrote: >> > As a result of backporting a bugfix, virtio_net started passing void * >> > to page_address, assuming that it will get

I have a few weeks of downtime between jobs coming up and I was considering trying to put together a m68k backend for LLVM. I have some experience with compiler front ends; I've maintained a couple of DSL implementations in the past, but I have relativly little knowledge of code generation. I know that there have been a few attempts in the past, but I cannot find any evidence that they made

Hello Kenneth, I don't know of any 68k backend and would certainly appreciate it if somebody took up the task! I'm working on a frontend for compatibility with the old Amos BASIC on the Amiga and was going to have to start a new backend for the classic models. That being said, I don't think 3 or 4 weeks would be enough unless you're really good with both 68k Assembly and

Hi. I am searching for hints, documents, or a discussion for how to properly model registers. As an experiment to learn llvm I am trying to do a M68k backend by following and modifying the Cpu0 tutorial by Chem Chung-Shu and Anoushe Jamshidi. The M68k registers are 32bit and comes in two classes data (d0-d7) and address (a0-a7). Similar to X86 target a subset of the registers can be accessed

http://bugzilla.mindrot.org/show_bug.cgi?id=718 Summary: Compilation error on m68k-next-openstep 4.0 Product: Portable OpenSSH Version: 3.6.1p2 Platform: Other OS/Version: other Status: NEW Severity: normal Priority: P1 Component: Build system AssignedTo: openssh-bugs at mindrot.org

Split out subsystem specific changes for easier reviews. This will be squashed with main commit. Signed-off-by: Krzysztof Kozlowski <k.kozlowski at samsung.com> --- arch/m68k/kernel/dma.c | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/arch/m68k/kernel/dma.c b/arch/m68k/kernel/dma.c index cbc78b4117b5..8cf97cbadc91 100644 --- a/arch/m68k/kernel/dma.c +++

Hi Min! On 11/3/20 6:10 PM, Min-Yih Hsu wrote: > Showing the prerequisites to become an experimental target and eventually, > an official target. We're currently struggling on setting up the buildbot > but I believe Adrian (CC-ed) is working on that. So I hope the patches can > be sorted out while waiting for the buildbot. The m68k machine is actually already up and running, I

Hello! On 11/3/20 6:10 PM, Min-Yih Hsu wrote: > Just a quick update on the Motorola 6800 backend: Based on the feedback, > "M68k" (with lowercase "k") will now be the canonical target name and > "m68k" be the target triple name. I've updated all the patches under review > to reflect this change. Are there any news on this? The M68k buildbot is ready