[Qemu-devel] compiling qemu on intel mac?
Perhaps this question is better addressed to the users group, but after some searching there I found no help. Forgive and redirect me at your pleasure. I'm trying to compile QEMU on an intel Mac. OSX 10.4.10 (not Leopard). The problem is that this machine comes with gcc-4.1. I used gcc_select to switch over to gcc-3.3 but that seems broken -- won't compile anything. I found some evidence on the web to indicate that pre-4.0 gcc on intel macs just doesn't work. God knows why this should be the case. I tried downloading and compiling gcc-3.3 from sources (which I've done before on Linux with success) but failed there. So before I spend many more hours trying to suss this out. Has anyone succeeded in compiling QEMU from source on an intel Mac with a pre-4.0 gcc. If so, please give me a quick tour? I spent an hour failing and would love some help... Tim Leek
[Qemu-devel] compiling qemu on ubuntu under parallels
Okay I'm having another go at you folk. Again, please feel free to shunt me off in the proper direction when I get annoying. According to Andreas, intel macs can't compile the QEMU source as- is. I'd need to use Q which only works because it has been patched to accommodate gcc-4. I've tried this and it works. A script applies a bunch of patches and the resulting Q app works properly. But I am a little worried about working with a forked source tree. We are building instrumentation for computer security research that will sit on top of QEMU. Thus, we'd like to have it as close and compatible as possible to the original QEMU source. So ... I tried compiling QEMU on an Ubuntu install running under Parallels. Yes, I know this sounds ridiculous. In many ways, it is ridiculous. But it should work,right? Compiled fine, once I forced it to use gcc-3.3. However, I was shocked when the resulting qemu executable didn't *run*. It complains about being unable to initialize SDL. So then I tried compiling and running the test programs provided with SDL (testalpha, e.g.). These also compile fine but don't run, generating the same SDL initialization error. Very annoying. What's up? Has anyone tried this perverse trick of trying to run QEMU under parallels? I think Parallels might use SDL somewhere under the curtain, but I'm not sure why this would mean user-space programs linked against libsdl would break. Perhaps I need to send this email to the Parallels people. On a similar note, has anyone tried to compile and run QEMU under VMWare on a mac? Thanks for all the help. -Tim Begin forwarded message: From: Tim Leek <[EMAIL PROTECTED]> Date: October 31, 2007 1:05:08 PM EDT To: Andreas Färber <[EMAIL PROTECTED]> Cc: Tim Leek <[EMAIL PROTECTED]> Subject: Re: [Qemu-devel] compiling qemu on intel mac? Thanks very much for your quick response. I think ... I'l just use the damn thing on linux under parallels. Ugh. Tim On Oct 31, 2007, at 11:34 AM, Andreas Färber wrote: Am 31.10.2007 um 15:00 schrieb Tim Leek: I'm trying to compile QEMU on an intel Mac. OSX 10.4.10 (not Leopard). The problem is that this machine comes with gcc-4.1. I used gcc_select to switch over to gcc-3.3 but that seems broken -- won't compile anything. I found some evidence on the web to indicate that pre-4.0 gcc on intel macs just doesn't work. God knows why this should be the case. I tried downloading and compiling gcc-3.3 from sources (which I've done before on Linux with success) but failed there. So before I spend many more hours trying to suss this out. Has anyone succeeded in compiling QEMU from source on an intel Mac with a pre-4.0 gcc. If so, please give me a quick tour? I spent an hour failing and would love some help... It does not work. You'll need patches - the best working solution I found was Q (kju-app.org), which patches QEMU 0.9.0 as part of its build process, but that fails against QEMU CVS HEAD. A newer GCC 4.x patch was proposed on this list the last months, but I haven't found the time for testing it on an Intel Mac yet, and last time I heard neither had the Q developers. So if you have some spare time to check I'd be happy to hear about your results. Andreas
Re: [Qemu-devel] compiling qemu on ubuntu under parallels
I tried using the gcc-3.3 that comes with Xcode 2.4. I don't have Leopard and so cannot try Xcode 3.0. It did not work on my intel mac. Also tried downloading gcc-3.3 and recompiling with configure --enable-languages=c --prefix=blah/blah make bootstrap This fails. My (limited) web searches indicated that Apple no longer supports gcc-3.3. Something to do with ABI. I didn't delve. If anyone has succeeded in compiling and running qemu on intel mac with either the gcc-3.3 that comes with it or with a gcc-3.3 they themselves compiled, I'd love to hear about it. On Oct 31, 2007, at 3:29 PM, Heikki Lindholm wrote: Tim Leek kirjoitti: Okay I'm having another go at you folk. Again, please feel free to shunt me off in the proper direction when I get annoying. According to Andreas, intel macs can't compile the QEMU source as-is. I'd need to use Q which only works because it has been patched to accommodate gcc-4. I've tried this and it works. A script applies a bunch of patches and the resulting Q app works properly. But I am a little worried about working with a forked source tree. We are building instrumentation for computer security research that will sit on top of QEMU. Thus, we'd like to have it as close and compatible as possible to the original QEMU source. What exactly is the problem building a darwin x86 gcc-3.4? I have built a darwin gcc x86 cross-compiler on a ppc host, which seems to create sane-looking executables, but have no intel mac, so... -- Heikki Lindholm
Re: [Qemu-devel] compiling qemu on ubuntu under parallels
Sorry. Here's more info. 1. SDL's test programs fail running on Ubuntu running under parallels as follows. % test/testalpha Couldn't initialize SDL: No available video device 2. Whereas the same test program runs fine on a real linux box running Ubuntu. Displays a cute little smiley face that waxes and wanes. 3. gcc-3.3 won't compile under intel osx. No I didn't try to tweak it or search extensively online to see if there are work-arounds. Possibly these exist. I have only copied the last 50-100 lines of output here. % tar xvf gcc-3.3.tar % cd gcc-3.3 % mkdir build % mkdir install % cd build % ../configure --enable-languages=c --prefix=/home/me/tmp/gcc-3.3/ install % make bootstrap ... echo timestamp > stage1_copy echo stage2_build > stage_last make CC=" stage1/xgcc -Bstage1/ -B/Users/timleek/Downloads/gcc-3.3/ install/i686-apple-darwin8.10.2/bin/" \ STAGE_PREFIX=stage1/ \ ADAC="\$(CC)" CFLAGS="-g -O2" LDFLAGS="" WARN_CFLAGS="\$ (GCC_WARN_CFLAGS)" STRICT_WARN="-Wtraditional -pedantic -Wno-long- long" libdir=/Users/timleek/Downloads/gcc-3.3/install/lib LANGUAGES="c gcov " MAKEOVERRIDES= OUTPUT_OPTION="-o \$@" stage1/xgcc -Bstage1/ -B/Users/timleek/Downloads/gcc-3.3/install/i686- apple-darwin8.10.2/bin/ -c -g -O2 -DIN_GCC -W -Wall -Wwrite- strings -Wstrict-prototypes -Wmissing-prototypes -Wtraditional - pedantic -Wno-long-long -DHAVE_CONFIG_H -DGENERATOR_FILE-I. -I. -I../../gcc -I../../gcc/. -I../../gcc/config -I../../gcc/../ include ../../gcc/gengenrtl.c -o gengenrtl.o /var/tmp//cc2Jaf3q.s:3000:indirect jmp without `*' /var/tmp//cc2Jaf3q.s:3017:indirect jmp without `*' /var/tmp//cc2Jaf3q.s:3034:indirect jmp without `*' /var/tmp//cc2Jaf3q.s:3051:indirect jmp without `*' /var/tmp//cc2Jaf3q.s:3068:indirect jmp without `*' /var/tmp//cc2Jaf3q.s:3085:indirect jmp without `*' /var/tmp//cc2Jaf3q.s:3102:indirect jmp without `*' /var/tmp//cc2Jaf3q.s:3119:indirect jmp without `*' /var/tmp//cc2Jaf3q.s:3136:indirect jmp without `*' /var/tmp//cc2Jaf3q.s:3153:indirect jmp without `*' stage1/xgcc -Bstage1/ -B/Users/timleek/Downloads/gcc-3.3/install/i686- apple-darwin8.10.2/bin/ -g -O2 -DIN_GCC -W -Wall -Wwrite-strings - Wstrict-prototypes -Wmissing-prototypes -Wtraditional -pedantic -Wno- long-long -DHAVE_CONFIG_H -DGENERATOR_FILE -o gengenrtl \ gengenrtl.o ../libiberty/libiberty.a xgcc: installation problem, cannot exec `c++filt3': No such file or directory /usr/bin/ld: Undefined symbols: __init_keymgr collect2: ld returned 1 exit status make[2]: *** [gengenrtl] Error 1 make[1]: *** [stage2_build] Error 2 make: *** [bootstrap] Error 2 On Oct 31, 2007, at 4:06 PM, andrzej zaborowski wrote: On 31/10/2007, Tim Leek <[EMAIL PROTECTED]> wrote: I tried using the gcc-3.3 that comes with Xcode 2.4. I don't have Leopard and so cannot try Xcode 3.0. It did not work on my intel mac. Also tried downloading gcc-3.3 and recompiling with configure --enable-languages=c --prefix=blah/blah make bootstrap This fails. Fails how? I think this is what Heikki was asking about. What were the errors? It would be also curious to see what SDL errors Ubuntu gave. A report like "This fails." is completely useless. Regards
