Hi,
My experience with this “issue” is very much different. Basically v5-26-00e works without a hitch using
./configure macosx64 --enable-roofit --enable-unuran --enable-minuit2 --with-fftw3-incdir=/opt/local/include --with-fftw3-libdir=/opt/local/lib --with-python-incdir=/opt/local/Library/Frameworks/Python.framework/Versions/2.6/include/python2.6 --with-python-libdir=/opt/local/lib
but v5-28-00 crashed with the X-related stack trace. After reading this thread, I configured v5-28-00 with
./configure macosx64 --enable-roofit --enable-unuran --enable-minuit2 --with-fftw3-incdir=/opt/local/include --with-fftw3-libdir=/opt/local/lib --with-python-incdir=/opt/local/Library/Frameworks/Python.framework/Versions/2.6/include/python2.6 --with-python-libdir=/opt/local/lib --with-x11-libdir=/opt/local/lib/ --with-xpm-libdir=/opt/local/lib/ --with-xft-libdir=/opt/local/lib/ --with-xext-libdir=/opt/local/lib/ --with-opengl-libdir=/opt/X11/lib
and now TH1::Draw has not crashed (I have not tried GL, though).
So: as far as I can tell it is not an X11 setup problem, but rather something changed in the configure.in between v5-26-00e and v5-28-00 which broke the Mac OS X out of the boxness for those of us with MacPorts.
Cheers,
Andre