I'm using DrRacket on the newest version of OS X, Yosemite, but when I open DrRacket the systems tells me that "DrRacket quit unexpectedly". I've already tried restarting the computer, and I'm sure the I have the 64-bit version of Racket, so what's going wrong here?
This is a known bug with Pango. Depending on whether you're using the 64-bit or 32-bit version of Racket, download the updated libraries:
64-bit
32-bit
You will need to grab all the libraries that contain pango in the name (libpango, libpangocairo, and libpangoft2) and overwrite the files in /Applications/Racket v6.1/lib.
Fixed in Version 6.1.1 which has been release on November 2014
Related
After I have updated my Emacs from 24.3 to 24.5 version, my 1.1 version of cedet (highlight, auto completion and summary function) has stopped working for c mode. When I trying to load these semantic mode individually, I got the following messages:
Buffer myfile.cpp was not set up for parsing
I think someone has asked a similar question in the past:
cedet-semantic error "Idle Service Error semantic-idle-summary-idle-function - Arithmetic error" when parsing linux kernel file "jiffies.h"
However, I am not sure which snapshot version he has downloaded & how to install a snapshot CEDET version. Can someone please help me with that?
After struggled for a while, I figured out something trivial but hard to see. Hopefully this answer will help others who has experienced the same problem.
When I started to use emacs version 24.3 I didn't know the Cedet version 2.0 was already a built-in package at that time. I downloaded Cedet 1.1 version from
Cedet SourceForge website.
And configured that according to some tutorial online by loading my downloaded 1.1 cedet.el file.
Surprisingly this Cedet 1.1 package is still compatible with emacs 24.3 version. Unfortunately this is not the case for emacs 24.5 version, the semantic mode encountered some problem with c mode. Therefore the best solution is to switch back to the built-in Cedet 2.0 version.
If you have used the older version of Cedet, it's possible that the old saved .semanticdb files are not compatible with latest Cedet semanticdb. You can do
rm -rf ~/.semanticdb/
So the new version semanticdb can create and use the new version of semanticdb (my friend helped me with that subtle problem so I can get the built-in Cedet 2.0 up and running).
I am running NetBeans 8.0.2 on a 64-bit Windows 7 PC. I was trying to follow Geertjan Wielenga's instructions for getting up and running with Scala in NetBeans 8.x.
The first instruction starts, "In the Terminal window, ..." so I selected Window > IDE Tools > Terminal. Instead of being a useable terminal window, the tab's content area was completely gray. I noticed that there seemed to be text flashing in the window before it went gray, so I clicked on the "Create New Local Terminal Tab" button multiple times until I was able to read the disappearing text:
Unable to start pty process
Searching for this phrase yielded results for C/C++ projects and the "Run" command, but I'm not doing a C/C++ project. How can I get the terminal window to a state where I can interact with it?
The NetBeans Terminal Emulator requires Cygwin. Importantly, the bitness of NetBeans must match the bitness of Cygwin. If you are using a 64-bit version of NetBeans, then you must use a 64-bit version of Cygwin; likewise 32-bit and 32-bit.
This comment by Andrew Krazny on NetBeans bug 234221 says:
A bitness of jdk/netbeans is important. Possible options are:
32-bit NB and only 32-bit cygwin is installed
32-bit NB and only 64-bit cygwin is installed
32-bit NB and both 32/64-bit cygwin are installed
64-bit NB and only 32-cygwin is installed
64-bit NB and only 64-cygwin is installed
64-bit NB and both 32/64-bit cygwin are installed
Cases 1) and 5) are 'ideal' - in this case everything should work and it is highly recommended that bitness of NB/cygwin match. This means that if one tries to use cygwin64 (s)he should install 64-bit java and run 64-bit version of NetBeans (netbeans64.exe).
Case 2) is almost nonfunctional. It requires cygwin64/bin to be in %Path%; compilation will work, but run is possible in 'External Terminal' only.
Case 3) NB will detect 32-bit cygwin and will use it by default. IF user tries to add cygwin64 as a toolchain and compile his code in 64-mode, run in 'Output Window' will not work. 32-bit toolchain is OK in this case
Case 4) is almost nonfunctional. It requires cygwin/bin to be in %Path%; compilation will work, but run is possible in 'External Terminal' only.
Case 6) 64-bit compilation/run will work, 32-bit run will fail.
In my case, I was using 32-bit Cygwin with 64-bit NetBeans. I installed 64-bit Cygwin, added a CYGWIN_HOME environment variable, and added %CYGWIN_HOME%\bin to the end of my path¹, and now I have a functioning terminal window.
¹which I hate doing because there are command names that overlap
I am using the eclipse PTP IDE to develop MPI code, I want to be able to compile MPI on windows, it seems to provide c++ and c binding, but I am writing using fortran and gfortran compiler and would like to work in windows, the current problem doesn't exist on linux because there it is possible to compile the libraries locally in linux and use the .mod modules.
I wanted to compile the modules using cygwin but the GNU gfortran version on cygwin is too old, and I wasn't successful openMPI or MPICH2 on windows using miniGW
any suggestions? maybe using c++ binding in fortran 2003, I write my code in fortran 2003 so it support this feature.
Documentation on this issue is lacking.
Thank you.
According to the MPICH2 Installer's Guide MPICH2 can be built under cygwin (see section 9.3 of the same document), so the version of gfortran shouldn't be an issue. Have you followed the instructions in this document (in particular section 2)?
Is there a clear or easy way to check over the command line if the installed JRE is 64 bit on a Sparc machine?
I am used to seeing this in:
java -version
however it appears that Solaris only says what version and build of java is installed.
Run java -d64 -version. It will complain if a 64 bit JVM isn't installed.
If d ( in lower case) does not work, put D in Upper case.
I have created an application in linux with GTK2 as GUI. It uses some linux-specific headers (e.g. arpa/inet.h) so to run under Windows I have to compile it with Cygwin. I downloaded the latest installer and choose to install GTK2 and its dependencies. My program compiled fine. But it needs X server to be running! I has old-style, ugly graphics and it doesn't open in a different window, like all Windows' applications do, but inside X server's window. Because of this it can't be portable. I found that guide, which is exactly what I need, but I get an error when I run "make" for GTK2 (undefined reference for _IID_IFilePersist, although I have uuid installed - also tried it with gtk2.20). Can you suggest what to do to build my application with cygwin? Or what do I need to install for the "_IID_IFilePersist" error? Thanks in advance!
There's prebuilt packages for windows that doesn't rely on X. http://gtk-win.sourceforge.net/home/index.php/Downloads
If you don't want X server to be running, then you're going to have to port the linux-specific parts of your code and compile with MinGW rather than Cygwin.