#21309 closed defect (fixed)
dom4j fails to build on Snow Leopard
Reported by: | nerdling (Jeremy Lavergne) | Owned by: | jberry@… |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | |
Keywords: | jdk6 | Cc: | nox@…, scooper@… |
Port: | dom4j |
Description
Attachments (2)
Change History (13)
Changed 15 years ago by nerdling (Jeremy Lavergne)
comment:1 Changed 15 years ago by nox@…
Cc: | nox@… added |
---|
Changed 15 years ago by nox@…
Attachment: | dom4j-JDK-1.6.diff added |
---|
A patch to make it work on Snow Leopard
comment:2 Changed 15 years ago by nox@…
Keywords: | jdk6 added |
---|---|
Summary: | dom4j fails to build → dom4j fails to build on Snow Leopard |
Version: | 1.8.99 |
I've just attached a patch which implements the missing abstract methods, making the build with JDK 1.6 running smoothly.
comment:4 Changed 15 years ago by scooper@…
The patch doesn't seem to work too well. I get the following output:
---> Fetching dom4j ---> Attempting to fetch dom4j-1.6.1.tar.gz from http://downloads.sourceforge.net/dom4j ---> Verifying checksum(s) for dom4j ---> Extracting dom4j ---> Applying patches to dom4j Error: Target org.macports.patch returned: shell command " cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_java_dom4j/work/dom4j-1.6.1" && /usr/bin/patch -p0 < '/opt/local/var/macports/sources/rsync.macports.org/release/ports/java/dom4j/files/patch-JDK-1.6.diff'" returned error 1 Command output: (Stripping trailing CRs from patch.) patching file src/java/org/dom4j/dom/DOMAttribute.java Hunk #1 FAILED at 15. Hunk #2 FAILED at 180. 2 out of 2 hunks FAILED -- saving rejects to file src/java/org/dom4j/dom/DOMAttribute.java.rej (Stripping trailing CRs from patch.) patching file src/java/org/dom4j/dom/DOMDocument.java Hunk #1 FAILED at 15. Hunk #2 FAILED at 303. 2 out of 2 hunks FAILED -- saving rejects to file src/java/org/dom4j/dom/DOMDocument.java.rej (Stripping trailing CRs from patch.) patching file src/java/org/dom4j/dom/DOMDocumentFactory.java Hunk #1 FAILED at 174. 1 out of 1 hunk FAILED -- saving rejects to file src/java/org/dom4j/dom/DOMDocumentFactory.java.rej (Stripping trailing CRs from patch.) patching file src/java/org/dom4j/dom/DOMElement.java Hunk #1 FAILED at 16. Hunk #2 FAILED at 391. 2 out of 2 hunks FAILED -- saving rejects to file src/java/org/dom4j/dom/DOMElement.java.rej (Stripping trailing CRs from patch.) patching file src/java/org/dom4j/tree/AbstractCharacterData.java Hunk #1 FAILED at 10. Hunk #2 FAILED at 43. 2 out of 2 hunks FAILED -- saving rejects to file src/java/org/dom4j/tree/AbstractCharacterData.java.rej (Stripping trailing CRs from patch.) patching file src/java/org/dom4j/tree/AbstractNode.java Hunk #1 FAILED at 20. Hunk #2 FAILED at 233. 2 out of 2 hunks FAILED -- saving rejects to file src/java/org/dom4j/tree/AbstractNode.java.rej Error: The following dependencies failed to build: jaxen dom4j jdom xom saxpath Error: Status 1 encountered during processing.
comment:7 Changed 15 years ago by nox@…
Mmh, something must have been wrong between the time when I write this patch from the SVN repository and when I committed it after having migrated to git-svn. The patch ended up with DOS line endings oO. r61185
comment:9 Changed 15 years ago by scooper@…
Better, but it looks like you missed one:
---> Applying patches to dom4j Error: Target org.macports.patch returned: shell command " cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_java_dom4j/work/dom4j-1.6.1" && /usr/bin/patch -p0 < '/opt/local/var/macports/sources/rsync.macports.org/release/ports/java/dom4j/files/patch-build.xml.diff'" returned error 1 Command output: patching file build.xml Reversed (or previously applied) patch detected! Assume -R? [n] Apply anyway? [n] Skipping patch. 1 out of 1 hunk ignored -- saving rejects to file build.xml.rej Error: The following dependencies failed to build: jaxen dom4j jdom xom saxpath Error: Status 1 encountered during processing.
comment:10 Changed 15 years ago by nox@…
I haven't touched this one. Run sudo port clean dom4j
and try again.
Note: See
TracTickets for help on using
tickets.
Cc Me!