), the first impression was that the Linux emulator
worked much better, in fact it runs Acu Cobol 6.0 for Linux flawlessly!
There are still some minor details that don't work as expected
(ACPI-S1 and cardbus) and some that stopped working (snd_pcm). These
will probably require delving
Dan Nelson writes:
In the last episode (Feb 04), Walter C. Pelissero said:
A side note. What is the impact of this IPC_64 flag on the FreeBSD
code? Can we ignore it, or does it mean that the Linux emulator is
outdated regarding this new flag?
Linux IPC_64 support was added to the
I tried linux_kdump (from ports) and things seem to clarify a bit.
I concentrated on acushare, which is the daemon that supervises
inter-process locking (locking on file access) and licence
verification. Whereas acushare seems to start properly, an attempt to
kill it through the recommended
In the last episode (Feb 03), Walter C. Pelissero said:
I tried linux_kdump (from ports) and things seem to clarify a bit.
I concentrated on acushare, which is the daemon that supervises
inter-process locking (locking on file access) and licence
verification. Whereas acushare seems to start
Dan Nelson writes:
If you do have sysvmsg loaded, you may have to start adding printfs in
linux_msgctl() to trace which call is failing and why.
Thanks. With your hints I made an interesting discovery that allowed
me to improve the situation dramatically.
In Linux's /usr/include/linux/ipc.h
In the last episode (Feb 04), Walter C. Pelissero said:
A side note. What is the impact of this IPC_64 flag on the FreeBSD
code? Can we ignore it, or does it mean that the Linux emulator is
outdated regarding this new flag?
Linux IPC_64 support was added to the 5.x tree over a year ago but
I realised that the ktrace log was rubbish; most of the syscalls names
were not properly mapped.
I tried to track down the exact spot were the Linux executable gets
the SEGV signal, running strace on a Debian system and comparing the
values passed to the system calls. Here is an extract:
Jerry McAllister writes:
[apparently the first message didn't get through; this is a repost]
Your previous post got through.
Probably the presumed answer is that no-one who saw it has
tried this or feels competent to respond.
Sorry for the duplicate. It wasn't the lack of answer but
[apparently the first message didn't get through; this is a repost]
Did enybody try to run AcuCobol 6.0 for Linux on FreeBSD's linulator?
I tried a couple of times (with old Debian libraries and more recently
Gentoo libraries) but runcbl keeps on getting a SIGSEGV right away.
ccbl (the compiler)
[apparently the first message didn't get through; this is a repost]
Your previous post got through.
Probably the presumed answer is that no-one who saw it has
tried this or feels competent to respond.
You might some response if you could find a way to break the
problem down a little more and
Did enybody try to run AcuCobol 6.0 for Linux on FreeBSD's linulator?
I tried a couple of times (with old Debian libraries and more recent
Gentoo libraries) but runcbl keeps on getting a SIGSEGV right away.
ccbl (the compiler) seems to work, though.
Any clue?
--
walter pelissero
11 matches
Mail list logo