Re: Linuxulator: running one's own small Linux in FreeBSD?

2021-02-08 Thread Alexander Leidinger via freebsd-emulation
Quoting Thomas Mueller (from Mon, 08 Feb 2021 02:51:55 +): Is it possible to run one's own little Linux in FreeBSD by null-mounting directory or partition on /compat/linux? Short answer: most probably yes. [...] Would the Linux C library have to be glibc, or could it be uClibc-ng

Re: Linuxulator: running one's own small Linux in FreeBSD?

2021-02-08 Thread Patrick M. Hausen
Good morning, Am 08.02.2021 um 03:51 schrieb Thomas Mueller : > Is it possible to run one's own little Linux in FreeBSD by null-mounting > directory or partition on /compat/linux? > I am thinking in particular of my own cross-compiled version (from FreeBSD or > NetBSD on amd64 aka x86_64) still

[Bug 253335] emulators/qemu-user-static php segfault building devel/pear for armv7

2021-02-08 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=253335 --- Comment #4 from Renato Botelho --- FYI, Same problem doesn't happen on a system running 12.2-STABLE and qemu-user-static version 3.1.0_1. `FreeBSD buildbot1-nyi.netgate.com 12.2-STABLE FreeBSD 12.2-STABLE acaac0eefa1(stable/12)

[Bug 253335] emulators/qemu-user-static php segfault building devel/pear for armv7

2021-02-08 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=253335 --- Comment #5 from Kyle Evans --- (In reply to Renato Botelho from comment #4) Given the timing, I'd suspect the recent elfload hacks that I did to try and fix kyua and direct-exec rtld. -- You are receiving this mail because: You are

[maqulator] FreeBSD running macOS binaries :-)

2021-02-08 Thread Tomasz CEDRO
Hello world :-) There is a nice QUCS [1] electronics simulation program (SPICE with GUI that works out of thebox). It is based on QT4 so it was removed from ports in March 2019. People use macOS binary with no problem. The question is - if we can somehow run Linux and Linux64 binaries - why

Re: [maqulator] FreeBSD running macOS binaries :-)

2021-02-08 Thread Theron
On 2/8/21 10:29 AM, Tomasz CEDRO wrote: The question is - if we can somehow run Linux and Linux64 binaries - why don't we run macOS binaries??? These are also ELF, macOS uses lots of FreeBSD stuff, and the packages are self contained with all libraries, so it should be even easier than

Re: Linuxulator: running one's own small Linux in FreeBSD?

2021-02-08 Thread JB via freebsd-emulation
‐‐‐ Original Message ‐‐‐ On Monday, February 8th, 2021 at 4:00 AM, wrote: > Message: 4 > > Date: Mon, 08 Feb 2021 02:51:55 + > > From: "Thomas Mueller" mueller6...@twc.com > > To: freebsd-emulation@freebsd.org > > Subject: Linuxulator: running one's own small Linux in FreeBSD? > >

[Bug 253335] emulators/qemu-user-static php segfault building devel/pear for armv7

2021-02-08 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=253335 --- Comment #6 from Renato Botelho --- (In reply to Kyle Evans from comment #5) Luiz (loos@) also mentioned he built some aarch64 stuff on that box and he saw issues with lots of other binaries, it's not only PHP. We also see some

Re: [maqulator] FreeBSD running macOS binaries :-)

2021-02-08 Thread freebsd
Dne 2021-02-08 16:29, Tomasz CEDRO napsal: Hello world :-) There is a nice QUCS [1] electronics simulation program (SPICE with GUI that works out of thebox). It is based on QT4 so it was removed from ports in March 2019. People use macOS binary with no problem. The question is - if we can

[Bug 253335] emulators/qemu-user-static php segfault building devel/pear for armv7

2021-02-08 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=253335 Mark Johnston changed: What|Removed |Added Status|New |Open

[Bug 253335] emulators/qemu-user-static php segfault building devel/pear for armv7

2021-02-08 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=253335 --- Comment #8 from Mark Johnston --- Using truss on the host I can see that we are mprotecting the last page (containing the address in question) of that range to PROT_READ | PROT_EXEC. It doesn't show up in qemu's strace output, so

[Bug 253335] emulators/qemu-user-static php segfault building devel/pear for armv7

2021-02-08 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=253335 --- Comment #11 from Kyle Evans --- (In reply to Mark Johnston from comment #10) Heh, I just arrived at the same conclusion, but hadn't yet found the logs where we were talking about this. IMO we should reapply the change, but correctly

[Bug 253335] emulators/qemu-user-static php segfault building devel/pear for armv7

2021-02-08 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=253335 --- Comment #12 from Kyle Evans --- (In reply to Kyle Evans from comment #11) (I suspect I was somehow looking at the wrong trap type values and steered the previous discussion amiss. :-() -- You are receiving this mail because: You are

[Bug 253335] emulators/qemu-user-static php segfault building devel/pear for armv7

2021-02-08 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=253335 Mark Johnston changed: What|Removed |Added CC||i...@freebsd.org --- Comment #10

[Bug 253335] emulators/qemu-user-static php segfault building devel/pear for armv7

2021-02-08 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=253335 --- Comment #13 from Mark Johnston --- (In reply to Kyle Evans from comment #12) Yeah, I couldn't really understand the T_ALIGNFLT check. I can submit a patch tomorrow, but feel free to fix it if you prefer. I have another

[Bug 253337] Linuxulator: glibc's pthread_getattr_np reports stack size as 124K

2021-02-08 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=253337 Mark Linimon changed: What|Removed |Added Assignee|b...@freebsd.org|emulat...@freebsd.org -- You are

[Bug 253335] emulators/qemu-user-static php segfault building devel/pear for armv7

2021-02-08 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=253335 --- Comment #9 from Mark Johnston --- qemu is doing the mprotect here: Thread 1 hit Catchpoint 1 (call to syscall mprotect), 0x6049f48a in ?? () (gdb)