search for: 6x86mx

...@@ config M386 config M486 bool "486" + depends on !X86_VMI help Select this for a 486 series processor, either Intel or one of the compatible processors from AMD, Cyrix, IBM, or Intel. Includes DX, @@ -55,6 +57,7 @@ config M486 config M586 bool "586/K5/5x86/6x86/6x86MX" + depends on !X86_VMI help Select this for an 586 or 686 series processor such as the AMD K5, the Cyrix 5x86, 6x86 and 6x86MX. This choice does not @@ -62,12 +65,14 @@ config M586 config M586TSC bool "Pentium-Classic" + depends on !X86_VMI help Select this for...

...@@ config M386 config M486 bool "486" + depends on !X86_VMI help Select this for a 486 series processor, either Intel or one of the compatible processors from AMD, Cyrix, IBM, or Intel. Includes DX, @@ -55,6 +57,7 @@ config M486 config M586 bool "586/K5/5x86/6x86/6x86MX" + depends on !X86_VMI help Select this for an 586 or 686 series processor such as the AMD K5, the Cyrix 5x86, 6x86 and 6x86MX. This choice does not @@ -62,12 +65,14 @@ config M586 config M586TSC bool "Pentium-Classic" + depends on !X86_VMI help Select this for...

...; make[2]: *** [truetype.o] Error 1 make[1]: *** [wineps/libwineps.so] Error 2 make: *** [dlls] Error 2 freetype2-2.0.1 and freetype2-devel-2.0.1 packages are installed (SuSE 7.1). configure didn't complain about wrong or missing files. System: - Kernel 2.4.5 - glibc 2.2 - gcc 2.95.2 - Cyrix 6x86MX @166 MHz - 128 MB RAM Seems, that wine looks for freetype headers in the wrong directory: gcc [...] -I/usr/local/include/freetype2 But it should be "-I/usr/include/freetype2". Why does it use the wrong directory, /usr/local/include/freetype2 doesn't exist. Bye, Manfred -- /&quo...

Unlike full virtualization in which the virtual machine provides the same platform interface as running natively on the hardware, paravirtualization requires modification to the guest operating system to work with the platform interface provided by the hypervisor. Xen was designed with performance in mind. Calls to the hypervisor are minimized, batched if necessary, and non-critical codepaths

Unlike full virtualization in which the virtual machine provides the same platform interface as running natively on the hardware, paravirtualization requires modification to the guest operating system to work with the platform interface provided by the hypervisor. Xen was designed with performance in mind. Calls to the hypervisor are minimized, batched if necessary, and non-critical codepaths