[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] -icount changes physical address assignments in QEMU 2.
From: |
alarson |
Subject: |
Re: [Qemu-devel] -icount changes physical address assignments in QEMU 2.10/2.11 |
Date: |
Fri, 6 Apr 2018 15:08:22 -0500 |
"Peter Maydell" <address@hidden> wrote on 04/06/2018 12:21:37
PM:
> On 6 April 2018 at 18:06, <address@hidden> wrote:
> >
> > FWIW, the compile had some anomalous behavior:
> >
> > .../qemu-2.12.0-rc2/scripts/feature_to_c.sh: line 71: /usr/bin/sed:
> > Invalid argument
> >
> > line 71 is:
> > arrayname=xml_feature_$(echo $input | sed 's,.*/,,; s/[-.]/_/g')
> >
> > Not sure what the problem is, but I always use "-e" before scripts.
>
> That's a bit odd. (POSIX allows both "-e script" and just "script".)
> What version of sed is this, and what version of /bin/sh ?
I don't know what the issue is. When I execute that command from my
normal bash shell, it works just fine. This is current Cygwin, so:
qemu$ sed --version
sed (GNU sed) 4.4
Packaged by Cygwin (4.4-1) ...
qemu$ /bin/sh --version
GNU bash, version 4.4.12(3)-release (x86_64-unknown-cygwin) ...
Perhaps I misread the sed manual, but I thought when you used a character
other
than "/", you had to preface the character with a backslash, e.g.,
sed 's\,.*,,;'
But, the above is all just speculation. I don't know what the real
problem is.
FWIW, I rebuilt twice more and the error didn't show up again, but I did
get some other spurious errors, one from GCC "invalid argument" and
another:
/bin/sh: /usr/bin/x86_64-w64-mingw32-gcc: Device or resource busy
make: ***
[/cygdrive/c/scm/Deos/products/qemu/branches/2.12/output/qemu-2.12.0-rc2/rules.mak:66:
stubs/notify-event.o] Error 126
So perhaps it is just normal Cygwin "fork" errors, or my use of "make
-j8".
I think you can ignore this. Sorry for the spam.
- Re: [Qemu-devel] -icount changes physical address assignments in QEMU 2.10/2.11, (continued)
- Re: [Qemu-devel] -icount changes physical address assignments in QEMU 2.10/2.11, Peter Maydell, 2018/04/05
- Re: [Qemu-devel] -icount changes physical address assignments in QEMU 2.10/2.11, alarson, 2018/04/05
- Re: [Qemu-devel] -icount changes physical address assignments in QEMU 2.10/2.11, Peter Maydell, 2018/04/06
- Re: [Qemu-devel] -icount changes physical address assignments in QEMU 2.10/2.11, Stefan Weil, 2018/04/06
- Re: [Qemu-devel] -icount changes physical address assignments in QEMU 2.10/2.11, alarson, 2018/04/06
- Re: [Qemu-devel] -icount changes physical address assignments in QEMU 2.10/2.11, Peter Maydell, 2018/04/06
- Re: [Qemu-devel] -icount changes physical address assignments in QEMU 2.10/2.11, Peter Maydell, 2018/04/06
- Re: [Qemu-devel] -icount changes physical address assignments in QEMU 2.10/2.11, Peter Maydell, 2018/04/06
- Re: [Qemu-devel] -icount changes physical address assignments in QEMU 2.10/2.11, alarson, 2018/04/06
- Re: [Qemu-devel] -icount changes physical address assignments in QEMU 2.10/2.11, Peter Maydell, 2018/04/06
- Re: [Qemu-devel] -icount changes physical address assignments in QEMU 2.10/2.11,
alarson <=
- Re: [Qemu-devel] -icount changes physical address assignments in QEMU 2.10/2.11, Mark Cave-Ayland, 2018/04/06
- Re: [Qemu-devel] -icount changes physical address assignments in QEMU 2.10/2.11, alarson, 2018/04/06