Gordon’s Ramblings

Another lesson related to giros. Present were Danny, Ruben, Marisa, Vani, DongMing, and Zannah. We worked on the code (left and right for the lady), without too much worry about what the guy did. I emphasized the fact that one should recognized when one reaches the second step of the basic in parellel foot (the side step). The various turned we worked on always ended up with the cross in the base. We also worked on two successive front crosses, and then on the combination: base in parallel foot. From front cross, forward cross of the lady going to the right, and then a second front cross, but turning to the left of the man, followed by a side step to the left and out to the basic in parallel position.

We worked on walking straight several steps and following that with a side step (left or right turn), but without breaking stride. Stop in two ways: 1) with equal weight on each foot, and 2) with full weight on receiving leg. Then repeat the exercise moving backward followed by a side step. Once the ladies get used to doing this, it becomes much easier for the man to lead them. Then the next issue is to slow the ladies down. Good exercise for the man as well for energy control.

Two excercises for next week:

1. Start from front cross (end of base for lady). Go from left foot front cross to right foot front cross. Do not open the knees at all. Good for balance.
2. Walk on jello: heels do not touch the ground. One leg straight, one bent, change feet, and go slowly. This is good for balance.

Today was the first tango lesson of the spring semester. Four students present: DongMing, Marisa, Ruben and Danny. Good for them! Dubravko came for a while to watch and participate as needed.
Here is what we worked on:

I first introduced what we learned last semester and discussed the objectives: learn to do giros to the left and right from anywhere, whether in cross or parallel systems. We started to work on open turns: side step followed by a front cross, to the left and to the right. First in dance position, then with the lady’s hands on the man’s chest, and then without hands. I discussed how to lead a side step without hands at all, and then to distinguish small from large lady side steps. This involved a stomach suck in.

We worked for about an hour on front and back cross techniques. I want the ladies to stop on during the back cross when the feet are together. I devised a new excercise: stand upright, forward lean, toes open, heels together. feel the heels against each other. Twist the body to the left, then eventually, release the right foot (no weight). Turn both feet, keeping the angle constant with no weight on the right foot. This models the left ocho. Do the same (to the left) with weight on the right foot, and no weight on the left foot, and this models the back ocho. It is difficult to maintain balance. Repeat both combinations turning to the right.

We also worked on taking the side step to back ocho. Take a side step (lead with body, land on straight foot). As the weight shifts to the supporting foot, turn to the left (if supporting foot is RF), and turn to the right (if supporting foot is LF). Turn very slight amount (5 degrees). Keep balance. Increase the amount of turn gradually up to 180 degrees.

As promised, I taught 2 hours Monday and Wednesday, covering basically the same material. Monday, we had Vani, Marissa, Ruben, Chai, Danny. Wednesday, we lost Vani, and added Tim and Nancy. We first discussed walking, first on two tracks to the beat (landing on the beat), then on a single track. I worked with how the body controls foot movement (probably too early to do this, do not know yet). I discussed keeping the weight on the forward part of the foot, emphasized that the foot simply drops to prevent one from falling. The body leads everything. I talk about all this to make sure I do not have to change my tune later on. I realize that the students retain almost nothing. But, slowly, the information will seep into the subconscious.

We worked on simple side steps, trying to stay facing the partner, and followed this by teaching the man to step to the left further than the lady, in preparation for the basic outside step to the right of the woman (from the woman’s perspective). Then we did several forward crosses in place (step 3 of the base), just to get the feel. This also forms the basis of the rock step. I then put the side step and the forward step together. Putting multiple forward steps together allows the man to walk (without cruzada of the lady) to the lady’s right. I emphasized that the man should place his foot beside the lady’s foot for added connection as he walks, on a single track. When he is ready for the lady to do a cross, he will step with a longer step, making the lady do a longer step with her right foot, and cross.

When walking, I differentiate two sections: 1) the man steps, keeping weight on both feet evenly,
and 2) he put his entire weight on the front foot. In part 1), the man’s back foot stays with the toe in place, while lifting the heel (for counter-balance), which makes the lady move back to neutral position (feet together, slightly open at the toes), and part 2) makes the lady continue her step back. Thus, I am immediately teaching the man to let the lady initiate the step first, and that this is done through indication from his body. This is very hard material for a first lesson, but might as well jump in.

Hopefully, the students will not get discouraged. I’ll have to do some basic steps the next time with less technique.

Here is a summary of two sequences that Dubravko helped me with.

Sequence 1:

Preparation step: LFF, lady RFB. Then I step to the side with RF along the same line. The entire sequence is executed along a straight line. It is similar to the standard change of front. Then, man LFB, RFB (diag right). Now is the key point. Instead of initiating a turn, step back while bringing the lady into you. Use a large step. Let the lady take a second step forward, then turn 180 degrees and go forward.

A slight variation that Dubravko came up with yesterday, consists on taking that final large step
backward for the man, and making it smaller. Let the lady take a second step forward, and just as a feet cross each other, turn so that her feet cross and continue forward.

Dubravko points out that the issue is how the steps relate one to another, or respect to the body, but of course, they can be done in a circular motion.

Sequence 2

Finally, we worked on Tete’s step that starts off with the lady doing a back cross to the right (her left). The key point for me is to bring her to me, and as she steps forward with her RF, to take a large step back with a LFC (left foot cross) while she takes a small step, and a second large step with my RF along the same line. Make sure the lady does not turn.

It is time to create a new web site for Scientific Programming. I will start with the web site for ACS1-2008 since it has improvements over last years’s scientific programming site. Last year Rails on Dreamhost was at version 2.0.2 . One year later, the version has not changed.
One can find information about which methods no longer work on the internet.

Older sites (prior to rails 2.0) must have envirnoment.rb edited so that rails can start up. Add the following line:
config.action_controller.session = {
:session_key => “_sci-prog.gorerle.com_session”,
:secret => “5d02d2049ecc42ca9fe6c5e0e584ef0a”
}

I have purchased for $9 a book describing the changes in Rails 2.0 with respect to Rails 1.0 Rails 2.1, New Features for Your Applications by Ryan Daigle.

I will create the new rail site in the same account erlebach_sciprog@sci-prog.gorerle.com .
But the class sites will be different (I would have to update mysql to have a year column to be able to differentiate years and semesters, and every entry would have to have this year and semester (hidden from the user and done in a way to avoid tampering). I have not done this yet.

I could simply add new tables to mysql database with 2008_spring in the names. But then all my controllers would have to have their names changed unless I careate name associations, which is not practical. So for now, I will simply create a new mysql table.

Installation appeared simple. I used the Passenger option on the Dreamhost panel when i created new subdomain (sci-prog08.gorerle.com/) and the directory sci-prog08.gorerle.com/public as a subdirectory for Rails. I tared the site for acs1-2008 and untarred it in sci-prog08.gorerle.com/ . That was it. Now I must change my mysql database, and change the config/constants.yml which allows me to set site parameters.

I know that Passenger is running by doing “ps -elf”

4 S erlebac 20910 870 0 74 0 – 1202 wait4 04:09 pts/0 00:00:00 -bash
4 S erlebac 23425 24064 0 71 2 – 8177 select 05:00 ? 00:00:01 /usr/bin/ruby1.8 dispatch.fcgi
5 S erlebac 10681 9889 0 71 2 – 9355 unix_s 05:13 ? 00:00:01 Passenger ApplicationSpawner: /home/.begira/erlebach_sciprog/sci-prog08.gorerle.com
1 S erlebac 3507 1 0 71 2 – 9799 select 05:22 ? 00:00:00 Rails: /home/.begira/erlebach_sciprog/sci-prog08.gorerle.com

Tonight I worked with Ruben, Marissa, Vanilda and Chai. We continue to make progress. Subjects included walking, forced crosses, exercises to change weight as one does forward or backward crosses. Exercises are the same for men and women done on their own. We worked on smoothing out the side step. We covered two types of crosses in the basic salida: cross and parallel systems. That gives four possibilities. How to “lead” this cross? The diagonal cross is used to initiate a left turn. In that case, use the right arm as a barrier. Indicate the cross through leftward rotation of the body. When doing the cross in back of the lady, simply move forward and she crosses automatically. Left her body sligthly with slight indication of rotation with your body, and she does the back cross (as opposed to the forced
cruzada).

We discussed giros, specifically to the left from highway one, and a turn to the right from highway three (by symmetry). We concentrated on getting Ruben to stay in front of the women, use some body dissociation. This was not easy.

I came to a dead end on the mac because Avizo requires Qt 3.3.6 and Leopard is not consistent with that version. I could not get the moc compiler to work. I tried the moc compiler of qt 4.4 and also tried to compile the moc compiler for 3.3.7 (no success).

I am now working on linux. First i changed Shawn’s method of dealing with include files. I created in mylineset/, an include/ directory with subdirectory hxlines/. I use #include . This approach ensures that I do not need to modify the include structure of the original Amira source, which will simplify integration into Amira later on. I no longer have include files in mylineset/ . In the GNUMakefile, I must put full path of the include directory location. Do not know why.

Everything compiled ok (I had to apply moc compiler by hand).

When starting Avizox (development version), I get errors related to the resource file. Do not know why.

qt-mac-free-3.3.7.tar.gz could not be compiled on Leopard. I am trying 3.3.8, uploaded to the Trolltech site in 2008, so might be more current (qt-mac-free-3.3.8b.tar.gz).

Equally bad. When running ./configure, I get
Creating qmake. Please wait…
c++ -c -o project.o -pipe -DQT_MACOSX_VERSION= -I. -Igenerators -Igenerators/unix -Igenerators/win32 -Igenerators/mac -I/Users/erlebach/Documents/src/qt-mac-free-3.3.8b/include/qmake -I/Users/erlebach/Documents/src/qt-mac-free-3.3.8b/include -I/Users/erlebach/Documents/src/qt-mac-free-3.3.8b/include -DQT_NO_TEXTCODEC -DQT_NO_UNICODETABLES -DQT_NO_COMPONENT -DQT_NO_STL -DQT_NO_COMPRESS -I/Users/erlebach/Documents/src/qt-mac-free-3.3.8b/mkspecs/macx-g++ -DHAVE_QCONFIG_CPP project.cpp
In file included from /Users/erlebach/Documents/src/qt-mac-free-3.3.8b/include/qtl.h:45,
from /Users/erlebach/Documents/src/qt-mac-free-3.3.8b/include/qvaluelist.h:45,
from /Users/erlebach/Documents/src/qt-mac-free-3.3.8b/include/qstringlist.h:45,
from project.h:42,
from project.cpp:39:
/Users/erlebach/Documents/src/qt-mac-free-3.3.8b/include/qglobal.h:190:6: error: #error “This version of Mac OS X is unsupported”
make: *** [project.o] Error 1
qmake failed to build. Aborting.

——–

I included a collection of include files provided by Shawn. that greatly reduced the numer of errors.
I also had to add -msse to the CXXFLAGS in Avizo500.app/Contents/MacOS/makearch-MacX.cfg to prevent SSE errors.

More errors:
from /Users/erlebach/Documents/src/avizo_local/src/mylines/HxLineSetEditor.cpp:146:
/Developer/SDKs/MacOSX10.4u.sdk/System/Library/Frameworks/CoreServices.framework/Frameworks/CarbonCore.framework/Headers/MachineExceptions.h:255: error: ?~@~X__m128i?~@~Y does not name a type

In file included from /Developer/SDKs/MacOSX10.4u.sdk/System/Library/Frameworks/CoreServices.framework/Frameworks/CarbonCore.framework/Headers/DriverServices.h:32,
from /Developer/SDKs/MacOSX10.4u.sdk/System/Library/Frameworks/CoreServices.framework/Frameworks/CarbonCore.framework/Headers/CarbonCore.h:125,
from /Developer/SDKs/MacOSX10.4u.sdk/System/Library/Frameworks/CoreServices.framework/Headers/CoreServices.h:24,
from /Developer/SDKs/MacOSX10.4u.sdk/System/Library/Frameworks/Carbon.framework/Headers/Carbon.h:20,
from /Developer/SDKs/MacOSX10.4u.sdk/System/Library/Frameworks/AGL.framework/Headers/agl.h:23,
from /Applications/Avizo500.app/Contents/MacOS/include/Amira/hxgl.h:46,
from /Applications/Avizo500.app/Contents/MacOS/include/Amira/HxViewer.h:66,
from /Users/erlebach/Documents/src/avizo_local/src/mylines/HxLineSetEditor.cpp:146:
/Developer/SDKs/MacOSX10.4u.sdk/System/Library/Frameworks/CoreServices.framework/Frameworks/CarbonCore.framework/Headers/MachineExceptions.h:255: error: ?~@~X__m128i?~@~Y does not name a type

MORE:
/Developer/SDKs/MacOSX10.4u.sdk/System/Library/Frameworks/Carbon.framework/Frameworks/HIToolbox.framework/Headers/CarbonEventsCore.h:1763: error: conflicting declaration ?~@~Xtypedef struct __EventLoopTimer* EventLoopTimerRef?~@~Y
/Users/erlebach/Documents/src/avizo_local/shawn/qt/qwindowdefs.h:94: error: ?~@~XEventLoopTimerRef?~@~Y has a previous declaration as ?~@~Xtypedef struct OpaqueEventLoopTimerRef* EventLoopTimerRef?~@~Y

These errors relate to the graphic subsystem on the mac (at least the Carbon-related ones do). These will be hard to deal with.

Conflicting variables (multiply defined):

from /Users/erlebach/Documents/src/avizo_local/src/mylines/HxLineSetEditor.cpp:146:
/Developer/SDKs/MacOSX10.4u.sdk/System/Library/Frameworks/Carbon.framework/Frameworks/HIToolbox.framework/Headers/Menus.h:807: error: conflicting declaration ?~@~Xtypedef struct OpaqueMenuRef* MenuRef?~@~Y
/Users/erlebach/Documents/src/avizo_local/shawn/qt/qwindowdefs.h:96: error: ?~@~XMenuRef?~@~Y has a previous declaration as ?~@~Xtypedef struct OpaqueMenuHandle* MenuRef?~@~Y

I will simply comment out the variable in qtwindowdefs.h for now. A better solution would be better #ifdefs.

OK, no more conflicting variables. Errors are decreasing. More …

In file included from /Applications/Avizo500.app/Contents/MacOS/include/Amira/HxMain.h:50,
from /Users/erlebach/Documents/src/avizo_local/src/mylines/HxLineSetEditor.cpp:139:
/Users/erlebach/Documents/src/avizo_local/shawn/qt/qmenubar.h:174: error: ?~@~XMenuRef?~@~Y has not been declared
/Users/erlebach/Documents/src/avizo_local/shawn/qt/qmenubar.h:175: error: ?~@~XMenuRef?~@~Y does not name a type
/Users/erlebach/Documents/src/avizo_local/shawn/qt/qmenubar.h:184: error: ?~@~XMenuRef?~@~Y has not been declared
/Users/erlebach/Documents/src/avizo_local/shawn/qt/qmenubar.h:187: error: ?~@~XMenuRef?~@~Y has not been declared
/Users/erlebach/Documents/src/avizo_local/shawn/qt/qmenubar.h:188: error: ?~@~XMenuRef?~@~Y has not been declared

Perhaps the error is different
MenuRef has not been declared. I am searching.

// Notice my changes in shawn/qtwindows.h

#if defined(Q_WS_MAC)
#if QT_MACOSX_VERSION < 0x1020
// typedef struct OpaqueEventLoopTimerRef* EventLoopTimerRef; // GE (in Carbon include files)
// in /Developer/SDKs/MacOSX10.4u.sdk/System/Library/Frameworks/Carbon.framework/Frameworks/HIToolbox.framework/Headers/CarbonEventsCore.h:

// from /Users/erlebach/Documents/src/avizo_local/src/mylines/HxLineSetEditor.cpp:146:
// Developer/SDKs/MacOSX10.4u.sdk/System/Library/Frameworks/Carbon.framework/Frameworks/HIToolbox.framework/Headers/Menus.h:807: error: conflicting declaration ?~@~Xtypedef struct OpaqueMenuRef* MenuRef?~@~Y
// /Users/erlebach/Documents/src/avizo_local/shawn/qt/qwindowdefs.h:96: error: ?~@~XMenuRef?~@~Y has a previous declaration as ?~@~Xtypedef struct OpaqueMenuHandle* MenuRef?~@~Y

//typedef struct OpaqueMenuHandle *MenuRef; // ORIG
typedef struct OpaqueMenuRef* MenuRef; // GE (to avoid conflict) in /Developer/SDKs/MacOSX10.4u.sdk/System/Library/Frameworks/Carbon.framework/Frameworks/HIToolbox.framework/Headers/Menus.h
#else
//typedef struct __EventLoopTimer* EventLoopTimerRef; // GE
typedef struct OpaqueMenuRef* MenuRef;
#endif

========

Final error for HxLineSetEditor.cpp

In file included from /Developer/SDKs/MacOSX10.4u.sdk/System/Library/Frameworks/CoreServices.framework/Frameworks/CarbonCore.framework/Headers/DriverServices.h:32,
from /Developer/SDKs/MacOSX10.4u.sdk/System/Library/Frameworks/CoreServices.framework/Frameworks/CarbonCore.framework/Headers/CarbonCore.h:125,
from /Developer/SDKs/MacOSX10.4u.sdk/System/Library/Frameworks/CoreServices.framework/Headers/CoreServices.h:24,
from /Developer/SDKs/MacOSX10.4u.sdk/System/Library/Frameworks/Carbon.framework/Headers/Carbon.h:20,
from /Developer/SDKs/MacOSX10.4u.sdk/System/Library/Frameworks/AGL.framework/Headers/agl.h:23,
from /Applications/Avizo500.app/Contents/MacOS/include/Amira/hxgl.h:46,
from /Applications/Avizo500.app/Contents/MacOS/include/Amira/HxViewer.h:66,
from /Users/erlebach/Documents/src/avizo_local/src/mylines/HxLineSetEditor.cpp:146:/Developer/SDKs/MacOSX10.4u.sdk/System/Library/Frameworks/CoreServices.framework/Frameworks/CarbonCore.framework/Headers/MachineExceptions.h:255: error: ?~@~X__m128i?~@~Y does not name a type/Developer/SDKs/MacOSX10.4u.sdk/System/Library/Frameworks/CoreServices.framework/Frameworks/CarbonCore.framework/Headers/MachineExceptions.h:256: error: ?~@~X__m128d?~@~Y does not name a type

I included in HxLineSetEditor.cpp (had no effect)
// GE for Mac only (related to SSE vectorized library)
#include // GE
SHould have worked since this include file defines __m128i

—–
Solution: enable sse2 and not ss3 (-msse2 on the g++ compiler). I found this using the “locate” command in linux/OSX. I found the definition in /usr/local/lib/gcc/i386-apple-darwin9.0.0/4.3.0/include/mmintrin.h . __m128i is a “long long”.
——
Makefile works all the way up to using the moc compiler, which is assumed to be in
/Applications/Avizo500.app/Contents/MacOS/bin/arch-MacX-Optimize
It is not. Therefore, I did: sudo ln -s /usr/bin/moc, and I hope this will work.

The moc compiler for qt4.4 appers to require “include for it to work. This is no in the original include files provided by Shawn.

I need a version of moc for Qt 3.3.6, otherwise I will not be able to compile. The way QObject includes has changed.

I want to install qt manually; otherwise, it might mix incorrectly with current version (4.4).
3.3.6 versions of Qt cannot even be found on the Trolltech website. I did find it there, under “previous versions”: ftp://ftp.trolltech.com/qt/source/qt-mac-free-3.3.7.tar.gz
—–

make generates the following error:

Compiling HxBSpline.cpp …
g++ -I/Users/erlebach/Documents/src/avizo_local/src -I/Users/erlebach/Documents/src/avizo_local/src/amiraKernel/mclib -I/Users/erlebach/Documents/src/avizo_local/include/arch-MacX/ -I/Users/erlebach/Documents/src/avizo_local/include/arch-MacX/qt -I/Users/erlebach/Documents/src/avizo_local/include/arch-MacX/oiv -I/Users/erlebach/Documents/src/avizo_local/include -I/Applications/Avizo500.app/Contents/MacOS/include -I/Applications/Avizo500.app/Contents/MacOS/include/mclib -I/Applications/Avizo500.app/Contents/MacOS/include/arch-MacX -I/Applications/Avizo500.app/Contents/MacOS/include/arch-MacX/qt -I/Applications/Avizo500.app/Contents/MacOS/include/arch-MacX/oiv -dynamiclib -fPIC -fno-common -DQT_THREAD_SUPPORT -DQT_CLEAN_NAMESPACE -DSOQT -DTGS_OIV -I/System/Library/Frameworks/Carbon.framework/Headers -I/System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonCore.framework/Versions/A/Headers -I/System/Library/Frameworks/AGL.framework/Headers/ -I/Users/erlebach/Documents/src/avizo_local/include/arch-MacX/globus -DQT_THREAD_SUPPORT -Wall -Wno-unknown-pragmas -pipe -arch i386 -arch ppc -isysroot /Developer/SDKs/MacOSX10.4u.sdk -D_REENTRANT -DHX_OS_MACX -DNEWSTYLE_IOSTREAM -DFORTRAN_UNDERLINE -DHX_NO_MATHF -DHX_HAS_STD -DHX_HAS_STDCOMPLEX -DHX_HAS_STDIOSTREAM -DHX_NO_X11 -include “mclib/McConfigMacX.h” -g -DPACKAGEID=amirapackage_mylines -c /Users/erlebach/Documents/src/avizo_local/src/mylines/HxBSpline.cpp -o HxBSpline.o
cc1plus: error: unrecognized command line option “-arch”
cc1plus: error: unrecognized command line option “-arch”

How can this be? I am using G++ 4.3.0 on my mac. There is -march=… . Same is true with g++ on lLinux with version 4.1.2 .

I changed, in /Applications/Avizo500.app/Contents/MacOS/make the file arch-MacX.cfg

#HX_ARCH_FLAGS=-arch i386 -arch ppc
# GErlebacher
#HX_ARCH_FLAGS=-march=i386 -march=ppc
HX_ARCH_FLAGS=-march=i386

I get the following errors (many of them) (include paths not found):
In file included from /Users/erlebach/Documents/src/avizo_local/src/mylines/HxBSpline.cpp:3:
/Users/erlebach/Documents/src/avizo_local/src/mylines/HxBSpline.h:4:21: error: HxCurve.h: No such file or directory

For some reason, the GNUMakefile does NOT include -I. , so I included it manually:

INCLUDES += \
-I.
-I$(AMIRA_LOCAL)/src

(THIS OBVIOUSLY WAS NOT TESTED BY Mercury).

The “-I.” did not work. However, -I/Users/erlebach/Documents/src/avizo_local/src/mylines \
did work (full path). WHY? Do not know.

Compiled ok: HxBSpline.cpp, HxComputeContours.cpp, HxCurve.cpp, HxCurveEditor.cpp, HxCurveToLineSetInterface.cpp, HxDisplayLineSet.cpp, HxLineSet.cpp,

Error in HxLineSetEditor.cpp . All related to not having the required qt include files, which do not seem to be Avizo-related. So I will work on this. Must use moc compiler, etc. for Mac.

/Users/erlebach/Documents/src/avizo_local/src/mylines/HxLineSetEditor.cpp:128:21: error: qdialog.h: No such file or directory
/Users/erlebach/Documents/src/avizo_local/src/mylines/HxLineSetEditor.cpp:129:23: error: qlineedit.h: No such file or directory
/Users/erlebach/Documents/src/avizo_local/src/mylines/HxLineSetEditor.cpp:130:26: error: qbuttongroup.h: No such file or directory
/Users/erlebach/Documents/src/avizo_local/src/mylines/HxLineSetEditor.cpp:131:25: error: qpushbutton.h: No such file or directory
/Users/erlebach/Documents/src/avizo_local/src/mylines/HxLineSetEditor.cpp:132:20: error: qlabel.h: No such file or directory
/Users/erlebach/Documents/src/avizo_local/src/mylines/HxLineSetEditor.cpp:133:21: error: qlayout.h: No such file or directory
/Users/erlebach/Documents/src/avizo_local/src/mylines/HxLineSetEditor.cpp:134:23: error: qcheckbox.h: No such file or directory

I added to include files in GNUMakefile:

-I/Library/Frameworks/QtCore.framework/Versions/4/Headers/ \
-I/Library/Frameworks/QtGui.framework/Versions/4/Headers/ \

Yet, still cannot find qscrollview.h . WHY NOT?

The proper way to use Qt on the mac is using frameworks, which this Makefile is not doing.

I got qscrollview.h from the internet (Qt 3.3.7) and put it in my home directory.
http://doc.trolltech.com/3.3/qscrollview-h.html

More errors:
from /Users/erlebach/Documents/src/avizo_local/src/mylines/HxLineSetEditor.cpp:146:
/usr/local/lib/gcc/i386-apple-darwin9.0.0/4.3.0/include/xmmintrin.h:35:3: error: #error “SSE instruction set not enabled” and many more. Of course, I have not used moc yet.

Why does Amira still use Qt 3.3.6 and not something more recent?