Datomic can't find Clojure.main - clojure

I've been learning Clojure for around a month now and I've decided to experiment with Datomic. I'm following the tutorial on the site exactly, but I can't even get past the first tutorial page (http://docs.datomic.com/first-db.html) because I get the following error on run:
run -m datomic.peer-server -p 8998 -a myaccesskey,mysecret -d firstdb,datomic:mem://firstdb
The system cannot find the path specified.
Error: Could not find or load main class clojure.main
I think this is just a classpath issue (I only picked up Java to work with Clojure), but looking at run.bat I think Datomic is set up to determine classpaths automatically, and I'd rather understand why it doesn't work out of the box (presumably a config issue on my machine, although I've tried another).
I've tried the latest version (0.9.5544) as well as the version explicitly mentioned in the tutorial (0.9.5530), as well as installing via Maven. Tried numerous other tutorials and forum-searches as well - plenty of general classpath advice, but nothing relevant to this. Please, send help!
Tom

Update - I seem to have resolved my issue. The instructions on the Datomic tutorial page appear to be incorrect (they say bin/run, but bin\run works). I worked around the bin/run error by running directly from the bin folder, but this obviously had the knock-on effect of making any relative paths incorrect.
I suspect I'm not great at Stack Exchange since I seem to have answered all of my own questions so far, but I hope someone else finds this useful!

Related

Why doesn't the commands to build openBR run?

When I run the commands specified in OpenBR page to build the library, I am getting the following error. Its coming when I execute the sub module update command.
Is it because the the repository is not available in that location? If that's not the case, why is it not running?
(At first I think it should be a comment but I cant).
I have the same issue like you when I install it. I believe the problem here is the link to repos of doc of openbr(it's not correct, maybe it's changed). You can continue with build process, this error dont have any effect in it and use the doc from official website. Good luck!

PyQt-win-gpl-4.11.1 installation

I saw there was a previous question about installing PyQt on a Mac, but unfortunately I'm not quite able to comment on the thread so I had to post a new question. Like that user, I have been having issues downloading QT 4.11.1. I downloaded SIP as well as PyQT4 (link to instructions), but when I try to run python configure-ng.py from my downloads folder, I keep getting the same error saying:
Error: Use the --qmake argument to explicitly specify a working Qt qmake.
Unfortunately I can't find the Qt settings which means I can't keep following the directions from the previous answer and I was hoping someone might be able to help walk me through how to download this module. Sorry for the duplication and thanks in advance.

How do I solve this OpenNi dependency error in PCL when using the Kinect?

Although I've just signed up for Stackoverflow, I've used answers.ros.org, pcl-users.org, and other similar sites. I'll try to give as much information as possible because although similar problems come up in Google searches I cannot find an answer to this.
I'm running Ubuntu 12.04 and I've installed PCL 1.7 via their set of instructions here: http:// pointclouds.org/downloads/linux.html
Following the tutorials I was able to get the "reader" and "writer" sample programs to work with the sample PCD's they give. I was also able to successfully use cmake to compile a more advanced program: http://pointclouds.org/documentation/tutorials/normal_distributions_transform.php#normal-distributions-transform
The problem begins whenever I try to make the iograbber or any other visualization programs that involve the Kinect. This is specifically the one I really want to use: http://pointclouds.org/documentation/tutorials/openni_grabber.php#openni-grabber Repeatedly, without fail, this has always been the warning I encounter when using cmake:
-- checking for module 'openni-dev'
-- package 'openni-dev' not found
-- Could NOT find openni (missing: OPENNI_INCLUDE_DIRS)
** WARNING ** io features related to openni will be disabled
It gives this warning several times in a row related to various components checking for it. Now you might say, "silly user, why don't you simply install openni-dev?"
Well when I initially did it with sudo apt-get install -y openni-dev (notice the -y which I soon learned about) it deleted most of my ROS/PCL files. Thread is here: http:// www.pcl-users.org/How-can-I-get-PCD-files-from-a-streaming-Kinect-td4033721.html It broke some packages and long story short I found out about aptitude and eventually I got myself back to square 1.
The thing is, I'm fairly sure I have openni 1.5.4 installed but somehow it isn't being found. When I go to my usr/lib folder it only shows an OpenNI2 folder, and not an OpenNI folder. I know there's a lot of issues with openni-dev popping up for PCL and ROS so I hope this answer will be able to help others as well. Before you ask, I'm copying/pasting the CMakeLists and C++ files exactly as I find it. I don't have a lot of programming experience so I hope I'm not missing something obvious.
If you use kinect v2, there's no OpenNI support.
So you can use this grabber:https://github.com/UnaNancyOwen/KinectGrabber/tree/Kinect2Grabber

OpenGL + GLUT using Ocaml

I have a problem with installing OpenGL (and GLut) and using it with Ocaml.
I have tried many different packages (under both Linux and Windows) and always got problems
about not found modules or other.
What will be easier : Linux or Windows? What should i exactly do? Which package of bindings is the best? ( are bindings is enough or i need to download some other things?)
Could anyone describe it step by step in a way that can be easy to follow?
Here are the exact steps :
sudo aptitude install liblablgl-ocaml-dev
cp /usr/share/doc/liblablgl-ocaml-dev/examples/simple.ml .
ocamlfind ocamlopt -linkpkg -package lablgl.togl simple.ml -o simple
./simple
I don't have the motivation to walk you through the installation process at the moment, but here are some (hopefully helpful) comments:
You generally want to use OCaml in *NIX because OCaml shows a very clear bias toward it. In particular, its debugger and profiler are not available in Windows.
One issue I randomly run into when installing new libraries in Linux (which may be a sign that I'm doing something dumb, come to think of it; oh, well) is permissions errors causing module loading errors. Try tracking down where the relevant libraries were installed and check that they're accessible (e.g. try lsing them as a user; seeing them in a directory is not enough).
For example, I recently installed OCamlMPI but was getting errors about it not being able to find modules even when I gave full paths to them.
It turned out that the directory it was stored in ($(ocamlc -where)/ocamlmpi) had a modmask of 0744 (i.e. drwxr--r--) when it should have had 0755 (i.e. drwxr-xr-x). After the permissions were changed, the modules loaded and worked just fine.
In fact, that's actually a problem I've run into when installing Python modules, too. Maybe I am doing something dumb somewhere.
Anyway, I hope that helps. :)

Anybody tried to compile Go on Windows?, It appears to now support generating PE Format binaries

http://code.google.com/r/hectorchu-go-windows/source/list
If you could compile it successfully, I like to know the procedures of how to.
Assuming you are using Hector's source tree:
Install MinGW and MSYS, along with MSYS Bison and any other tools you think you'll find useful (vim, etc).
Install ed from the GNUWin32 project.
Install Python and Mercurial.
Clone the [hectorchu-go-windows mercurial repository](https://hectorchu-go-windows.googlecode.com/hg/ hectorchu-go-windows) to C:\Go.
Run an MSYS shell (or rxvt). The rest of these are bash commands...
mkdir $HOME/bin
export PATH=$HOME/bin:$PATH
export GOROOT=C:\\Go
export GOARCH=386
export GOOS=mingw
cd /c/Go/src
./all.bash
Correct errors as it spits them out at you, repeat step 10 until it starts building.
It's the same idea as on Linux or MacOS, basically.
However, I still stand by what I said in my comment above: this isn't necessarily going to generate anything that actually works yet. You'd be better served by waiting until this effort has merged into the main Go tree before tackling it, unless your interest is in assisting with the porting effort.
Update: there is now a mostly-functional pre-built windows port available, for those not interested in building the compiler themselves. However, given the rate of change of the project, the lack of formal releases (other than the hg "release" tag), and the possibility of Hector's changes being merged into the main branch soon, keeping up with development via source builds is likely to produce better results over time.
Just FYI, there is seems official one now.
http://code.google.com/p/go-windows/
Hector said he was only able to get as far as being able to compile and run an empty main. See issue 107:
http://code.google.com/p/go/issues/detail?id=107
There is still a lot of work to do in porting that, especially since the code has lots of dependencies on ptrace and syscall, not to mention the different threading models between Linux/BSD and Windows.
Update:
There's a new thread on golang-nuts (started 26.03.2010) with a link to a recent build and some current building instructions (using MinGW+MSYS).