We’re looking whether this can be fixed on the glibc side currently.
** Changed in: qemu
Status: Expired => Incomplete
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1796520
Title:
autogen
It works with sudo, but that can’t be the fix…
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1891748
Title:
qemu-arm-static 5.1 can't run gcc
Status in QEMU:
Fix Released
Status in Juju Charms
Heh, even if I omit -static …
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1891748
Title:
qemu-arm-static 5.1 can't run gcc
Status in QEMU:
Fix Released
Status in Juju Charms Collection:
New
$ qemu-arm --version
qemu-arm version 5.2.0 (Debian 1:5.2+dfsg-6)
Copyright (c) 2003-2020 Fabrice Bellard and the QEMU Project developers
I’m seeing this error on a totally different file:
I’ve made a short test program (hello world-ish) and compiled it with
the OpenWrt toolchain but added
On Tue, 3 Mar 2020, Daniel P. Berrangé wrote:
> AFAICT, this is not the case. On both my Fedora & Debian installs,
> x11vnc is just a binary that attaches to an existing X11 server
Huh, weird. Perhaps this changed over the years and distro releases.
> $ ls -al /usr/bin/vncserver
$ realpath
On Mon, 2 Mar 2020, Daniel P. Berrangé wrote:
> There's two translations happening
>
> * The scancode emitted by the kernel and/or hardware device,
>and then translated/mangled by X11 and reported as the
>hardware keycode
>
> * The keysym which is the mapping from the hardware keycode
On Mon, 2 Mar 2020, Daniel P. Berrangé wrote:
> "x11vnc" suggests you had a regular X11 desktop session, and are
> exporting it via VNC ?
No, x11vnc is a standalone VNC server.
> Can you tell me a bit more detail about how you launch this all.
Sure:
$ vncserver -geometry 1000x768 -name nowm
I got this while running qemu under VNC, and was told to report it.
including the following information:
- Operating system
Debian GNU/Linux sid/x32
- X11 Server
x11vnc 0.9.16-3
- xprop -root
_NET_ACTIVE_WINDOW(WINDOW): window id # 0x1400010
Hi Salvatore,
>p.s.: my earlier reply to you seem to have been rejected and never
> reached you, hope this one does now.
if you sent from Googlemail, it may reach me in the next weeks or
never *shrug* they don’t play nice with greylisting. The -submitter
or @d.o works, though. I’m following
Note that mksh is virtually a superset of OpenBSD ksh and accepts this
construct, for a quick fix.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1525682
Title:
configure: fix POSIX compatibility
Hi all!
Thanks for this:
Commit ID: 100548597A713CD6746
CVSROOT: /cvs
Module name: src
Changes by:t...@herc.mirbsd.org2014/12/08 12:20:42 UTC
Modified files:
bin/mksh : Build.sh
Log message:
port this to GNU bash 1.12.1 from
enh dixit:
[ mksh testsuite ]
have you considered using sh instead? :-)
Not pure sh, that’s nowhere near enough. Maybe mksh. But if
the one just built has issues, that may mask it. If another,
you’ve got hen/egg problems.
Maybe C. But then, (cross-)building a C program to test another
one just
12 matches
Mail list logo
