Qt ‘configure’ failed when attempting to test compile an oci.cpp file:

OCI auto-detection... ()
g++ -c -pipe -O2 -Wall -W -I../../../mkspecs/macx-g++ -I. -I../../../../oracle/instantclient_10_2/sdk/include -o oci.o oci.cpp
g++ -headerpad_max_install_names -o oci oci.o -L/Users/evadnoob/oracle/instantclient_10_2 -lnnz10 -lclntsh
ld: library not found for -lclntsh
collect2: ld returned 1 exit status
make: *** [oci] Error 1
OCI disabled.
Oracle (OCI) support cannot be enabled due to functionality tests!
Turn on verbose messaging (-v) to ./configure to see the final report.
If you believe this message is in error you may use the continue
switch (-continue) to ./configure to continue.


I noticed that I got no complaints from the linking of “nnz10″: -lnnz10. The only difference between -lclntsh and -lnnz10 where in the file names.


-rw-r--r--@ 1 evadnoob staff 288 Apr 1 2009 BASIC_LITE_README
-rw-r--r--@ 1 evadnoob staff 282 Apr 1 2009 SQLPLUS_README
-r--r--r--@ 1 evadnoob staff 1609607 Feb 2 2008 classes12.jar
-rwxr-xr-x@ 1 evadnoob staff 34168 Apr 1 2009 genezi*
-r-xr-xr-x@ 1 evadnoob staff 1525 Aug 30 2004 glogin.sql*
-rwxr-xr-x@ 1 evadnoob staff 25582048 Nov 25 21:19 libclntsh.dylib*
-rwxr-xr-x@ 1 evadnoob staff 25582048 Mar 31 2009 libclntsh.dylib.10.1*
-rwxr-xr-x@ 1 evadnoob staff 2062528 Mar 3 2009 libnnz10.dylib*
-rwxr-xr-x@ 1 evadnoob staff 1277896 Mar 3 2009 libocci.dylib.10.1*
-rwxr-xr-x@ 1 evadnoob staff 4305504 Apr 1 2009 libociicus.dylib*
-rwxr-xr-x@ 1 evadnoob staff 118672 Mar 25 2009 libocijdbc10.dylib*
-rwxr-xr-x@ 1 evadnoob staff 118672 Mar 25 2009 libocijdbc10.jnilib*
-rwxr-xr-x@ 1 evadnoob staff 1108736 Mar 25 2009 libsqlplus.dylib*
-rwxr-xr-x@ 1 evadnoob staff 1438288 Mar 3 2009 libsqlplusic.dylib*
-r--r--r--@ 1 evadnoob staff 1555682 Feb 2 2008 ojdbc14.jar
drwxr-xr-x 7 evadnoob staff 238 Apr 1 2009 sdk/
-rwxr-xr-x@ 1 evadnoob staff 8552 Mar 25 2009 sqlplus*

I’m using the instant client to build with. I copied libclntsh.dylib.10.1 to libclntsh.dylib and things ‘configure’ just fine.

1 row selected.

I thought, nxml-mode should be able to do this, but checking the function names provided with nxml didn’tyield anything useful as far as I could tell.  So I thought tidy should be able to do this.

For example, given this input xml, from a maven pom.xml where I purposefully de-formatted the xml:

<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"         xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd">
<parent><groupId>dmb</groupId><artifactId>dev</artifactId><version>{dev.version}</version></parent><modelVersion>4.0.0</modelVersion><groupId>dmb</groupId><artifactId>misc</artifactId>
<packaging>jar</packaging><name>miscellaneous</name><url>http://maven.apache.org</url><dependencies><dependency><groupId>org.jboss.cache</groupId><artifactId>jbosscache-core</artifactId><version>2.1.0.CR4</version></dependency><dependency><groupId>joda-time</groupId><artifactId>joda-time</artifactId><version>1.5.2</version></dependency><dependency><groupId>org.springframework</groupId><artifactId>spring-core</artifactId><version>{spring.version}</version></dependency><dependency><groupId>org.springframework</groupId><artifactId>spring-context</artifactId><version>{spring.version}</version></dependency><dependency><groupId>org.springframework</groupId><artifactId>spring-jdbc</artifactId><version>{spring.version}</version></dependency><dependency><groupId>commons-cli</groupId><artifactId>commons-cli</artifactId><version>1.1</version></dependency><dependency><groupId>google.com</groupId><artifactId>collections</artifactId><version>20071022</version><scope>compile</scope></dependency><dependency><groupId>org.apache.lucene</groupId><artifactId>lucene-core</artifactId><version>2.0.0</version></dependency><dependency><groupId>com.sleepycat</groupId><artifactId>je</artifactId><version>3.3.62</version></dependency></dependencies><build>
<plugins>
<plugin><groupId>org.apache.maven.plugins</groupId><artifactId>maven-shade-plugin</artifactId><executions><execution>
<phase>package</phase><goals><goal>shade</goal></goals><configuration><artifactSet><excludes><exclude>classworlds:classworlds</exclude><exclude>junit:junit</exclude><exclude>jmock:jmock</exclude><exclude>xml-apis:xml-apis</exclude><exclude>javax.jms:jms</exclude><exclude>org.testng:testng</exclude></excludes></artifactSet>
<transformers>
<transformer implementation="org.apache.maven.plugins.shade.resource.ComponentsXmlResourceTransformer"/></transformers></configuration></execution></executions></plugin>
<plugin><groupId>org.apache.maven.plugins</groupId><artifactId>maven-jar-plugin</artifactId><configuration><archive><manifestEntries><mainClass>dmb.Main</mainClass></manifestEntries></archive></configuration></plugin></plugins></build>
<profiles>
<profile><id>unit-test</id><activation><activeByDefault>false</activeByDefault></activation><build>
<plugins>
<plugin><groupId>org.apache.maven.plugins</groupId><artifactId>maven-surefire-plugin</artifactId><version>2.4</version><configuration><systemProperties><systemProperty><name>base.directory</name><value>xbasedir</value></systemProperty></systemProperties><useFile>false</useFile>
<trimStackTrace>false</trimStackTrace><useSystemClassLoader>true</useSystemClassLoader><groups>unit</groups></configuration></plugin></plugins></build></profile>
<profile><id>system-test</id><activation><activeByDefault>false</activeByDefault></activation><build>
<plugins>
<plugin><groupId>org.apache.maven.plugins</groupId><artifactId>maven-surefire-plugin</artifactId><version>2.4</version><configuration><skip>false</skip><systemProperties><systemProperty><name>base.directory</name><value>xbasedir</value></systemProperty></systemProperties><useFile>false</useFile>
<trimStackTrace>false</trimStackTrace><useSystemClassLoader>true</useSystemClassLoader><groups>system</groups></configuration></plugin></plugins></build></profile>
<profile><id>default-tests</id><activation><activeByDefault>true</activeByDefault></activation><build>
<plugins>
<plugin><groupId>org.apache.maven.plugins</groupId><artifactId>maven-surefire-plugin</artifactId><version>2.4</version><configuration><skip>false</skip><systemProperties><systemProperty><name>base.directory</name><value>xbasedir</value></systemProperty></systemProperties><useFile>false</useFile>
<trimStackTrace>false</trimStackTrace><useSystemClassLoader>true</useSystemClassLoader></configuration></plugin></plugins></build></profile></profiles><repositories><repository><id>repository.jboss.org</id><url>http://repository.jboss.org/maven2</url></repository><repository><id>snapshots.jboss.org</id><url>http://snapshots.jboss.org/maven2</url></repository><repository><id>java.net</id><url>http://download.java.net/maven/1</url><layout>legacy</layout></repository><repository><releases><enabled>true</enabled><updatePolicy>always</updatePolicy><checksumPolicy>warn</checksumPolicy></releases><snapshots><enabled>true</enabled><updatePolicy>never</updatePolicy><checksumPolicy>fail</checksumPolicy></snapshots><id>oracleReleases</id><name>Oracle Released Java Packages</name><url>http://download.oracle.com/maven</url><layout>default</layout></repository></repositories>
<properties><spring.version>2.5.1</spring.version></properties></project>

I ran tidy like this:

$ tidy -q -i -xml << EOF
</repositories>
<properties><spring.version>2.5.1</spring.version></properties></project>
> EOF
<project xmlns="http://maven.apache.org/POM/4.0.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd">
<parent>
<groupId>dmb</groupId>
<artifactId>dev</artifactId>
<version>{dev.version}</version>
</parent>
<modelVersion>4.0.0</modelVersion>
<groupId>dmb</groupId>
<artifactId>misc</artifactId>
<packaging>jar</packaging>
<name>miscellaneous</name>
<url>http://maven.apache.org</url>
<dependencies>
<dependency>
<groupId>org.jboss.cache</groupId>
<artifactId>jbosscache-core</artifactId>
<version>2.1.0.CR4</version>
</dependency>
<dependency>
<groupId>joda-time</groupId>
<artifactId>joda-time</artifactId>
<version>1.5.2</version>
</dependency>
<dependency>
<groupId>org.springframework</groupId>
<artifactId>spring-core</artifactId>
<version>{spring.version}</version>
</dependency>
<dependency>
<groupId>org.springframework</groupId>
<artifactId>spring-context</artifactId>
<version>{spring.version}</version>
</dependency>

This works even better directly from within emacs by running shell-command-on-region(M-|), tidy -q -i -xml :

I customized the name of the prj.el file:

(custom-set-variables
   '(jde-project-file-name ".jde.project"))

I’ve really only started to use flymake-mode after I also began using maven. Thanks to pom-parser I can configure my projects directly from pom.xml, no need to manually setup multiple classpaths, pom-parser takes care of this.

Here’s the steps:

• setup your pom.xml
• setup a simple prj.el like this:

(jde-project-file-version "1.0")
(jde-set-variables
  '(jde-compile-option-command-line-args
     (quote ("-Xlint:all" "-Xlint:-serial"))))
(require 'pom-parser)
(with-pom ()
  (pom-set-jde-variables *pom-node*))

• You’ll need to download the eclipse compiler. At the time of this writing I’m using 3.3.2, the latest eclipse. Save the ecj.jar some place convenient. I like to put mine with the emacs config so I can easily locate the correct version of the jar.
• Enable flymake mode: M-x flymake-mode, or bind it to a key for a mode that makes sense: <tt>(define-key jde-mode-map [f11] ‘flymake-mode)</tt>
• That’s it. Pretty easy.

Here’s rest of my flymake settings:

(custom-set-variables
   '(flymake-allowed-file-name-masks
        (cons '("\\.java\\'"  . (jde-ecj-server-flymake-init jde-ecj-flymake-cleanup))
              flymake-allowed-file-name-masks  ))
    '(flymake-no-changes-timeout 2.0)
    '(flymake-log-level 3)
    '(flymake-start-syntax-check-on-newline nil)
    '(jde-compiler '(("eclipse java compiler server" "~/emacs/ecj-3.3M6.jar")))
    '(jde-ecj-command-line-args (quote ("-d" "none" "-1.5" "-warn:unused,semicolon" "-maxProblems" "50" "-g")))
  )

http://maven.apache.org/plugins/maven-dependency-plugin/build-classpath-mojo.html#cpFile

So I tried the outputFile and that didn’t work either, for me output always goes to stdout, never to the file.

I’m using the latest pom-parser.el from http://svn.grumblesmurf.org/svn/pom-el/trunk/pom-parser.el , GNU Emacs 23.0.60.1, and maven 2.0.8

I took a shot at parsing the output to capture the classpath. I was thinking that this function,or a better one could parse the output of the two goals( effective pom and the dependency classpath) instead of two temp files in ‘pom-parse-pom’.

--- pom-parser-orig.el 2008-03-12 21:42:24.359375000 -0400
+++ pom-parser.el 2008-03-12 22:00:12.906250000 -0400
@@ -115,8 +115,7 @@
(cdr cached-pom-data)
(message "Calling %s help:effective-pom dependency:build-classpath..."
pom-maven-command)
-      (let ((temp-pom (make-temp-file temporary-file-directory))
-            (temp-cpfile (make-temp-file temporary-file-directory)))
+      (let ((temp-pom (make-temp-file (concat temporary-file-directory  "pom.") nil ".xml")))
(with-current-buffer *mvn-output-buffer*
(erase-buffer))
(if (> (let ((default-directory (file-name-directory pom-file)))
@@ -127,23 +126,39 @@
"dependency:build-classpath"
(concat "-Doutput=" temp-pom)
"-DincludeScope=compile"
-                               "-DincludeTypes=jar"
-                               (concat "-Dmaven.dep.cpFile=" temp-cpfile)))
+                               "-DincludeTypes=jar" ))
0)
(progn (display-buffer *mvn-output-buffer* t)
(error "%s call failed" pom-maven-command))
(let ((pom (pom-parse-pom-file temp-pom)))
-            (if (null pom)
+            (message "length pom: %s" (length pom))
+            (if (or (null pom) (= 0 (length pom )))
(error "Failed to parse effective POM; the contents of %s might help diagnose" temp-pom)
-              (let ((classpath (pom-parse-classpath-file temp-cpfile)))
+              (let ((classpath (pom-parse-classpath-buffer)))
+                (message "classpath: %s" classpath)
(push (cons 'pom:classpath classpath)
(nth 1 pom)))
(puthash pom-file (cons pom-file-last-mod-time pom)
*pom-cache*)
(delete-file temp-pom)
-              (delete-file temp-cpfile)
pom)))))))

+(defun pom-parse-classpath-buffer ()
+  ""
+  ;;(display-buffer *mvn-output-buffer*)
+  (with-current-buffer *mvn-output-buffer*
+    (goto-char (point-min))
+    (let ((line-before-classpath (search-forward "Dependencies classpath:" nil t)))
+      (message "line-before-classpath: %s" line-before-classpath )
+      (if line-before-classpath
+          (progn
+            (forward-line)
+            ;;buffer-substring
+            ;;(message "point-bol: %s point-eol: %s" (point-at-bol) (point-at-eol))
+            (let ((tmp-classpath (buffer-substring-no-properties (point-at-bol) (point-at-eol))))
+              (split-string tmp-classpath path-separator)))
+        (error "failed to find classpath in mvn dependency:build-classpath output")))))
+
(defun pom-parse-classpath-file (classpath-file)
(with-temp-buffer
(insert "(\"")

(jde-project-file-version "1.0")
(jde-set-variables
'(jde-compile-option-command-line-args
(quote ("-Xlint:all" "-Xlint:-serial"))))
(require 'pom-parser)
  (with-pom ()
  (pom-set-jde-variables *pom-node*))

I’ve been using the gud-jdb debugger for java. I’d like to see the gud-jdb behavior be more like edebug, where typing interacts with the debugger rather than modifying the source buffer.

Here’s a screenshot of debugging a simple defun:

I’ve had some problems with gud and jdb. Mainly it chokes on 1.5 syntax, import static makes parsing fail. Attaching to a remote vm, actually the easiest way to debug a complicated java application with multiple classloaders, only works when you have gud-jdb-use-classpath and gud-jdb-directories set. I typically run a quick command to get the directory containing the class I want to debug to gud-jdb-directries, like:

(add-to-list 'gud-jdb-directories (file-name-directory (buffer-file-name (current-buffer))))

I created a small function for adding a java(jde-mode) buffer to the gud-jdb-directories. This function let’s the debugger find a source file when you do a where.

<code>
(defun dmb-add-current-class-gud-jdb-directories()
“add the current buffers directory “
(interactive)
(if (not (eq major-mode ‘jde-mode))
(error “Must be a jde-mode buffer to add it to the debugger”))
(add-to-list ‘gud-jdb-directories (file-name-directory (buffer-file-name (current-buffer))))
)
</code>

(autoload 'ansi-color-for-comint-mode-on "ansi-color" nil t)(add-hook 'shell-mode-hook 'ansi-color-for-comint-mode-on)

But at first it looks like

I wasn’t very happy with that, so I decided to fiddle with the attributes, and came up with :

(custom-set-variables  '(ansi-color-names-vector (vector "black" "sienna" "DeepSkyBlue4" "yellow" "NavyBlue" "magenta" "cyan" "white"))  )

Which renders as:

Much better…