as far as i remember i had to put the same code into softmmu_header.h to
get "correct" results.
i found it easiest to do this in the ld/st macros in these files (~6
places in code)
This probably sounds stupid but whats the best way to get debug
output? Due to the code generation magic qemu does,
This patch adds a dummy function which fixes a
linker error (missing symbol) for Windows.
Regards
Stefan Weil
Index: block-raw.c
===
RCS file: /sources/qemu/qemu/block-raw.c,v
retrieving revision 1.10
diff -u -b -B -r1.10 block-raw.c
Am Montag, den 18.12.2006, 00:56 -0800 schrieb Diwaker Gupta:
> > as far as i remember i had to put the same code into softmmu_header.h to
> > get "correct" results.
> > i found it easiest to do this in the ld/st macros in these files (~6
> > places in code)
>
> This probably sounds stupid but wha
Anthony Liguori wrote:
@@ -6826,9 +6833,59 @@ int main(int argc, char **argv)
case QEMU_OPTION_no_reboot:
no_reboot = 1;
break;
+ case QEMU_OPTION_daemonize:
+ daemonize = 1;
}
The indenting is off here a
In Xen, we use a single top level Makefile to build everything. This
means we automatically kick off the configure script. It would be nice
if QEMU's configure did a better job of finding existing GCC 3.x
installs so that the user didn't have to manually specific the location.
The attached p
On Tuesday 19 December 2006 02:25, Anthony Liguori wrote:
> +gcc3_list="gcc32 gcc33 gcc34 gcc-3.2 gcc-3.3 gcc-3.4"
Shouldn't we be preferring newer compilers?
> + echo "Looking for gcc 3.x"
We shouldn't do this if if the user explicitly specified a compiler.
Replacing explicit user setting
Paul Brook wrote:
On Tuesday 19 December 2006 02:25, Anthony Liguori wrote:
+gcc3_list="gcc32 gcc33 gcc34 gcc-3.2 gcc-3.3 gcc-3.4"
Shouldn't we be preferring newer compilers?
Attached patch changes order plus improves the initial GCC 4 check a bit.
+ echo "Looking for gcc
> If they explicitly specific an invalid --cc=, the checks will get
> triggered (but in the past, we would have bailed).
That's what I'm objecting to. If I do:
./configure --cc=gcc4
I expect configure to either use gcc4 or fail with an error. Preferably the
latter, but I'm open to persuasion.
On Mon, Nov 13, 2006 at 02:30:27PM -0500, Daniel Jacobowitz wrote:
> I was trying to run GDB remote debug tests through a -redir socket
> today. It crawled unbelievably. Paul guessed that slirp wasn't using
> TCP_NODELAY, and Nagle was to blame.
>
> He was even righter than usual. Adding TCP_NO
Paul Brook wrote:
If they explicitly specific an invalid --cc=, the checks will get
triggered (but in the past, we would have bailed).
That's what I'm objecting to. If I do:
./configure --cc=gcc4
I expect configure to either use gcc4 or fail with an error. Preferably the
latter, but I'm
CVSROOT:/sources/qemu
Module name:qemu
Changes by: Paul Brook 06/12/19 03:31:34
Modified files:
. : configure
Log message:
Look for gcc3 (Anthony Liguori).
CVSWeb URLs:
http://cvs.savannah.gnu.org/viewcvs/qemu/configure?cvsroot=qemu&r1=1.112&r2=
Hello,
Hi Stefan,
I have applied your eepro100 emulator for vitsta RTM guest, and met
some problems.
Vista complaints :
The device is not configured correctly.(Code 1). There is no
driver selected for the device information set or element.
And Hardware Ids in device m
12 matches
Mail list logo
