You are viewing a plain text version of this content. The canonical link for it is here.
Posted to fop-dev@xmlgraphics.apache.org by "Peter B. West" <pb...@powerup.com.au> on 2000/12/18 05:20:20 UTC
Another build failure
Linux localhost 2.2.16-3
xml-fop 14:07$ echo $CLASSPATH
/opt/xalan/xalan.jar:/opt/xalan/bsf.jar:/opt/xalan/bsfengines.jar:/opt/xalan/samples/xalansamples.jar:/opt/xalan/xdocs/xalanjdoc.jar:/opt/xerces/xerces.jar:/opt/xerces/xercesSamples.jar:/usr/local/src/xml-fop/lib/ant.jar:/usr/local/src/xml-fop/lib/w3c.jar:/usr/local/src/xml-fop/lib:/usr/local/src/xml-fop/build/fop.jar
cvs update
Initial problem:
cvs update: in directory src/org/apache/fop/fo/properties:
cvs update: cannot open CVS/Entries for reading: No such file or
directory
cvs [update aborted]: cannot write <CVS/Template file>: No such file or
directory
This is fixed by removing the link
/usr/local/src/xml-fop/src/org/apache/fop/fo/properties ->
../../../../../build/src/org/apache/fop/fo/properties
This link I installed in my early attempts to get a compile to work. I
asked whether it was needed, but no-one replied.
When I then build.sh clean, build.sh, the build fails when it runs out
of error allowance.
If I restore the link, the build fails with *only* the following errors:
compile:
Compiling the sources
[javac] Compiling 515 source files to
/usr/local/src/xml-fop/build/classes
[javac]
/usr/local/src/xml-fop/build/src/org/apache/fop/fo/pagination/SimplePageMaster.java:122:
Incompatible type for method. Explicit cast needed to convert
org.apache.fop.layout.RegionArea to
org.apache.fop.layout.BodyRegionArea.
[javac]
this.pageMaster.addBody(getRegion(RegionBody.REGION_CLASS).makeRegionArea(contentRectangleXPosition,contentRectangleYPosition,contentRectangleWidth,contentRectangleHeight));
[javac]
^
[javac]
/usr/local/src/xml-fop/build/src/org/apache/fop/render/pdf/PDFRenderer.java:634:
Incompatible type for =. Can't convert
org.apache.fop.layout.BodyAreaContainer to
org.apache.fop.layout.AreaContainer.
[javac] body = page.getBody();
[javac] ^
[javac]
/usr/local/src/xml-fop/build/src/org/apache/fop/render/awt/AWTRenderer.java:291:
Incompatible type for =. Can't convert
org.apache.fop.layout.BodyAreaContainer to
org.apache.fop.layout.AreaContainer.
[javac] body = page.getBody();
[javac] ^
[javac]
/usr/local/src/xml-fop/build/src/org/apache/fop/render/xml/XMLRenderer.java:308:
Incompatible type for =. Can't convert
org.apache.fop.layout.BodyAreaContainer to
org.apache.fop.layout.AreaContainer.
[javac] body = page.getBody();
[javac] ^
[javac]
/usr/local/src/xml-fop/build/src/org/apache/fop/layout/SpanArea.java:95:
Method renderSpanArea(org.apache.fop.layout.SpanArea) not found in
interface org.apache.fop.render.Renderer.
[javac] renderer.renderSpanArea(this);
[javac] ^
[javac]
/usr/local/src/xml-fop/build/src/org/apache/fop/layout/BodyAreaContainer.java:124:
Method renderBodyAreaContainer(org.apache.fop.layout.BodyAreaContainer)
not found in interface org.apache.fop.render.Renderer.
[javac] renderer.renderBodyAreaContainer(this);
[javac] ^
[javac] 6 errors
BUILD FAILED
So it seems that the link is necessary, but that it results in error
messages (and an abort, I think) from the cvs update. What is the
source of the above six errors? How do I determine a working cvs label
to rebuild from when this sort of thing happens?
Yours faithfully,
Peter
--
Peter B. West pbwest@powerup.com.au http://powerup.com.au/~pbwest
"Lord, to whom shall we go?"
Re: Another build failure
Posted by "Peter B. West" <pb...@powerup.com.au>.
Arved Sandstrom wrote:
>
> At 02:47 PM 12/18/00 +1000, Peter B. West wrote:
>
> [ snip ]
> >Of course, that should be ...with only the... I am chronically
> >bad-tempered these days. The "another" in the subject refers back to a
> >build problem report I saw earlier today.
>
> I think you had the misfortune to get caught up in a mass flurry of CVS
> commits. One error message in your previous post suggests that strongly. The
> dust should have settled by later on today, although Fotis Jannidis reports
> that things already built for him.
>
> Hey, you should see me when I'm trying to track down an arcane J2EE
> distributed transaction related bug at work. :-) No Mr Happy then.
Arved,
I just did an update and built OK. How should the
src/org/apache/fop/fo/properties link be handled?
Peter
--
Peter B. West pbwest@powerup.com.au http://powerup.com.au/~pbwest
"Lord, to whom shall we go?"
Re: Another build failure
Posted by Arved Sandstrom <Ar...@chebucto.ns.ca>.
At 02:47 PM 12/18/00 +1000, Peter B. West wrote:
[ snip ]
>Of course, that should be ...with only the... I am chronically
>bad-tempered these days. The "another" in the subject refers back to a
>build problem report I saw earlier today.
I think you had the misfortune to get caught up in a mass flurry of CVS
commits. One error message in your previous post suggests that strongly. The
dust should have settled by later on today, although Fotis Jannidis reports
that things already built for him.
Hey, you should see me when I'm trying to track down an arcane J2EE
distributed transaction related bug at work. :-) No Mr Happy then.
Arved Sandstrom
Fairly Senior Software Type
e-plicity (http://www.e-plicity.com)
Wireless * B2B * J2EE * XML --- Halifax, Nova Scotia
Page size
Posted by "Peter B. West" <pb...@powerup.com.au>.
I use fop to build PDF files, specifying my page size like so:
<fo:simple-page-master master-name="ofseason"
height="29.7cm" width="21cm"
margin-top="75pt"
margin-bottom="50pt"
margin-left="60pt"
margin-right="60pt">
<fo:region-body/>
</fo:simple-page-master>
When I view the output using Acrobat in Netscape 4.75 under linux, the
page size is reported as 8x11. Is this a problem with Communicator,
Acrobat or FOP?
Peter
--
Peter B. West pbwest@powerup.com.au http://powerup.com.au/~pbwest
"Lord, to whom shall we go?"
Re: Another build failure
Posted by "Peter B. West" <pb...@powerup.com.au>.
"Peter B. West" wrote:
>
> Linux localhost 2.2.16-3
>
> xml-fop 14:07$ echo $CLASSPATH
> /opt/xalan/xalan.jar:/opt/xalan/bsf.jar:/opt/xalan/bsfengines.jar:/opt/xalan/samples/xalansamples.jar:/opt/xalan/xdocs/xalanjdoc.jar:/opt/xerces/xerces.jar:/opt/xerces/xercesSamples.jar:/usr/local/src/xml-fop/lib/ant.jar:/usr/local/src/xml-fop/lib/w3c.jar:/usr/local/src/xml-fop/lib:/usr/local/src/xml-fop/build/fop.jar
>
The xalan and xerces are both 1.2.1.
> When I then build.sh clean, build.sh, the build fails when it runs out
> of error allowance.
>
> If I restore the link, the build fails with *only* the following errors:
Of course, that should be ...with only the... I am chronically
bad-tempered these days. The "another" in the subject refers back to a
build problem report I saw earlier today.
Peter
--
Peter B. West pbwest@powerup.com.au http://powerup.com.au/~pbwest
"Lord, to whom shall we go?"