You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@xalan.apache.org by "Olivier Epicoco (JIRA)" <xa...@xml.apache.org> on 2004/12/25 22:53:03 UTC

[jira] Created: (XALANC-446) XALAN_C 1.9 or current do not build on Fedora core 3

XALAN_C 1.9 or current do not build on Fedora core 3
----------------------------------------------------

         Key: XALANC-446
         URL: http://nagoya.apache.org/jira/browse/XALANC-446
     Project: XalanC
        Type: Bug
    Versions: 1.9    
 Environment: Fedora core 3,
gcc (GCC) 3.4.2 20041017 (Red Hat 3.4.2-6.fc3)
Xalan-C_1_9_0-src.tar.gz & Xalan-C_current-src.tar.gz
untarred via tar zxvf file...
./runConfigure -plinux -cgcc -xg++ -rpthread

    Reporter: Olivier Epicoco
    Priority: Blocker


Two types of errors:
1- runConfigure and configure are not executable (I had to 'chmod -R a+x *configure' to start the compilation)

2- Cannot compile the source: XPath/XPathEvaluator.cpp 
because XPath/ElementPrefixResolverProxy.hpp contains an unimplemented copy constructor

See below more details:


g++ -O2 -DNDEBUG     -fno-elide-constructors -Wall -fPIC -DLINUX -D_REENTRANT -D XALAN_INMEM_MSG_LOADER -c -I/opt/local/xml-xalan/c/src -I/opt/local/xml-xalan/c/ include -I../../nls/include -I/opt/local/xerces-c-src_2_6_0/src/ -I/opt/local/xe rces-c-src_2_6_0/include/xercesc -I/opt/local/xerces-c-src_2_6_0/include/  -o .. /../obj/XPathEnvSupportDefault.o /opt/local/xml-xalan/c/src/xalanc/XPath/XPathEn vSupportDefault.cpp
g++ -O2 -DNDEBUG     -fno-elide-constructors -Wall -fPIC -DLINUX -D_REENTRANT -D XALAN_INMEM_MSG_LOADER -c -I/opt/local/xml-xalan/c/src -I/opt/local/xml-xalan/c/ include -I../../nls/include -I/opt/local/xerces-c-src_2_6_0/src/ -I/opt/local/xe rces-c-src_2_6_0/include/xercesc -I/opt/local/xerces-c-src_2_6_0/include/  -o .. /../obj/XPathEvaluator.o /opt/local/xml-xalan/c/src/xalanc/XPath/XPathEvaluator. cpp
/opt/local/xml-xalan/c/src/xalanc/XPath/ElementPrefixResolverProxy.hpp: In membe r function `xalanc_1_9::XObjectPtr xalanc_1_9::XPathEvaluator::evaluate(xalanc_1 _9::DOMSupport&, xalanc_1_9::XalanNode*, const xalanc_1_9::XalanDOMChar*, const xalanc_1_9::XalanElement*)':
/opt/local/xml-xalan/c/src/xalanc/XPath/ElementPrefixResolverProxy.hpp:89: error : `xalanc_1_9::ElementPrefixResolverProxy::ElementPrefixResolverProxy(const xala nc_1_9::ElementPrefixResolverProxy&)' is private
/opt/local/xml-xalan/c/src/xalanc/XPath/XPathEvaluator.cpp:279: error: within th is context
/opt/local/xml-xalan/c/src/xalanc/XPath/ElementPrefixResolverProxy.hpp: In membe r function `xalanc_1_9::XObjectPtr xalanc_1_9::XPathEvaluator::evaluate(xalanc_1 _9::DOMSupport&, xalanc_1_9::XalanNode*, const xalanc_1_9::XPath&, const xalanc_ 1_9::XalanElement*)':
/opt/local/xml-xalan/c/src/xalanc/XPath/ElementPrefixResolverProxy.hpp:89: error : `xalanc_1_9::ElementPrefixResolverProxy::ElementPrefixResolverProxy(const xala nc_1_9::ElementPrefixResolverProxy&)' is private
/opt/local/xml-xalan/c/src/xalanc/XPath/XPathEvaluator.cpp:299: error: within th is context
/opt/local/xml-xalan/c/src/xalanc/XPath/ElementPrefixResolverProxy.hpp: In membe r function `xalanc_1_9::XPath* xalanc_1_9::XPathEvaluator::createXPath(const xal anc_1_9::XalanDOMChar*)':
/opt/local/xml-xalan/c/src/xalanc/XPath/ElementPrefixResolverProxy.hpp:89: error : `xalanc_1_9::ElementPrefixResolverProxy::ElementPrefixResolverProxy(const xala nc_1_9::ElementPrefixResolverProxy&)' is private
/opt/local/xml-xalan/c/src/xalanc/XPath/XPathEvaluator.cpp:348: error: within th is context
/opt/local/xml-xalan/c/src/xalanc/XPath/ElementPrefixResolverProxy.hpp: In membe r function `xalanc_1_9::XPath* xalanc_1_9::XPathEvaluator::createXPath(const xal anc_1_9::XalanDOMChar*, xalanc_1_9::DOMSupport&, const xalanc_1_9::XalanElement* )':
/opt/local/xml-xalan/c/src/xalanc/XPath/ElementPrefixResolverProxy.hpp:89: error : `xalanc_1_9::ElementPrefixResolverProxy::ElementPrefixResolverProxy(const xala nc_1_9::ElementPrefixResolverProxy&)' is private
/opt/local/xml-xalan/c/src/xalanc/XPath/XPathEvaluator.cpp:361: error: within th is context
gmake[1]: *** [../../obj/XPathEvaluator.o] Error 1
gmake[1]: Leaving directory `/opt/local/xml-xalan/c/src/xalanc'
gmake: *** [all] Error 2


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://nagoya.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xalan-dev-help@xml.apache.org


[jira] Commented: (XALANC-446) XALAN_C 1.9 or current do not build on Fedora core 3

Posted by "Olivier Epicoco (JIRA)" <xa...@xml.apache.org>.
     [ http://issues.apache.org/jira/browse/XALANC-446?page=comments#action_57149 ]
     
Olivier Epicoco commented on XALANC-446:
----------------------------------------

Compiles OK 
Ran a few sample programs - OK
Thanks

> XALAN_C 1.9 or current do not build on Fedora core 3
> ----------------------------------------------------
>
>          Key: XALANC-446
>          URL: http://issues.apache.org/jira/browse/XALANC-446
>      Project: XalanC
>         Type: Bug
>     Versions: 1.9
>  Environment: Fedora core 3,
> gcc (GCC) 3.4.2 20041017 (Red Hat 3.4.2-6.fc3)
> Xalan-C_1_9_0-src.tar.gz & Xalan-C_current-src.tar.gz
> untarred via tar zxvf file...
> ./runConfigure -plinux -cgcc -xg++ -rpthread
>     Reporter: Olivier Epicoco
>     Priority: Blocker
>      Fix For: CurrentCVS

>
> Two types of errors:
> 1- runConfigure and configure are not executable (I had to 'chmod -R a+x *configure' to start the compilation)
> 2- Cannot compile the source: XPath/XPathEvaluator.cpp 
> because XPath/ElementPrefixResolverProxy.hpp contains an unimplemented copy constructor
> See below more details:
> g++ -O2 -DNDEBUG     -fno-elide-constructors -Wall -fPIC -DLINUX -D_REENTRANT -D XALAN_INMEM_MSG_LOADER -c -I/opt/local/xml-xalan/c/src -I/opt/local/xml-xalan/c/ include -I../../nls/include -I/opt/local/xerces-c-src_2_6_0/src/ -I/opt/local/xe rces-c-src_2_6_0/include/xercesc -I/opt/local/xerces-c-src_2_6_0/include/  -o .. /../obj/XPathEnvSupportDefault.o /opt/local/xml-xalan/c/src/xalanc/XPath/XPathEn vSupportDefault.cpp
> g++ -O2 -DNDEBUG     -fno-elide-constructors -Wall -fPIC -DLINUX -D_REENTRANT -D XALAN_INMEM_MSG_LOADER -c -I/opt/local/xml-xalan/c/src -I/opt/local/xml-xalan/c/ include -I../../nls/include -I/opt/local/xerces-c-src_2_6_0/src/ -I/opt/local/xe rces-c-src_2_6_0/include/xercesc -I/opt/local/xerces-c-src_2_6_0/include/  -o .. /../obj/XPathEvaluator.o /opt/local/xml-xalan/c/src/xalanc/XPath/XPathEvaluator. cpp
> /opt/local/xml-xalan/c/src/xalanc/XPath/ElementPrefixResolverProxy.hpp: In membe r function `xalanc_1_9::XObjectPtr xalanc_1_9::XPathEvaluator::evaluate(xalanc_1 _9::DOMSupport&, xalanc_1_9::XalanNode*, const xalanc_1_9::XalanDOMChar*, const xalanc_1_9::XalanElement*)':
> /opt/local/xml-xalan/c/src/xalanc/XPath/ElementPrefixResolverProxy.hpp:89: error : `xalanc_1_9::ElementPrefixResolverProxy::ElementPrefixResolverProxy(const xala nc_1_9::ElementPrefixResolverProxy&)' is private
> /opt/local/xml-xalan/c/src/xalanc/XPath/XPathEvaluator.cpp:279: error: within th is context
> /opt/local/xml-xalan/c/src/xalanc/XPath/ElementPrefixResolverProxy.hpp: In membe r function `xalanc_1_9::XObjectPtr xalanc_1_9::XPathEvaluator::evaluate(xalanc_1 _9::DOMSupport&, xalanc_1_9::XalanNode*, const xalanc_1_9::XPath&, const xalanc_ 1_9::XalanElement*)':
> /opt/local/xml-xalan/c/src/xalanc/XPath/ElementPrefixResolverProxy.hpp:89: error : `xalanc_1_9::ElementPrefixResolverProxy::ElementPrefixResolverProxy(const xala nc_1_9::ElementPrefixResolverProxy&)' is private
> /opt/local/xml-xalan/c/src/xalanc/XPath/XPathEvaluator.cpp:299: error: within th is context
> /opt/local/xml-xalan/c/src/xalanc/XPath/ElementPrefixResolverProxy.hpp: In membe r function `xalanc_1_9::XPath* xalanc_1_9::XPathEvaluator::createXPath(const xal anc_1_9::XalanDOMChar*)':
> /opt/local/xml-xalan/c/src/xalanc/XPath/ElementPrefixResolverProxy.hpp:89: error : `xalanc_1_9::ElementPrefixResolverProxy::ElementPrefixResolverProxy(const xala nc_1_9::ElementPrefixResolverProxy&)' is private
> /opt/local/xml-xalan/c/src/xalanc/XPath/XPathEvaluator.cpp:348: error: within th is context
> /opt/local/xml-xalan/c/src/xalanc/XPath/ElementPrefixResolverProxy.hpp: In membe r function `xalanc_1_9::XPath* xalanc_1_9::XPathEvaluator::createXPath(const xal anc_1_9::XalanDOMChar*, xalanc_1_9::DOMSupport&, const xalanc_1_9::XalanElement* )':
> /opt/local/xml-xalan/c/src/xalanc/XPath/ElementPrefixResolverProxy.hpp:89: error : `xalanc_1_9::ElementPrefixResolverProxy::ElementPrefixResolverProxy(const xala nc_1_9::ElementPrefixResolverProxy&)' is private
> /opt/local/xml-xalan/c/src/xalanc/XPath/XPathEvaluator.cpp:361: error: within th is context
> gmake[1]: *** [../../obj/XPathEvaluator.o] Error 1
> gmake[1]: Leaving directory `/opt/local/xml-xalan/c/src/xalanc'
> gmake: *** [all] Error 2

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xalan-dev-help@xml.apache.org


Re: Changes, bugs, etc. between 1.8 and 1.9

Posted by da...@us.ibm.com.
Hi Brian,

> > Can you be more specific about what you mean when you say "without a 
> > stylesheet'?  Do you mean the code path where the processor looks in 
the 
> > source document for any stylesheet PIs?
> 
> Sorry, yes. In Xalan 1.8, if no stylesheet was explicitly specified and 
> the XML source document didn't contain a processing instruction, then a 
> ProcessorError was raised. In Xalan 1.9, a warning is generated. The 
> exception was more convient for me

Weird -- that should still be an error.  We'll have to fix it.

> > You said: "when a call to write() on the output stream is called". I'm 

> > not sure I understand.  Do you mean  a call to write() is failing, and 
no 
> > error is returned?  That would definitely be a bug.
> 
> My InputSource's write method raises an exception everytime it is 
> called (this is part of my test suite). In Xalan 1.8, the exception 
> propogated back to the top. In Xalan 1.9 the exception is caught at 
> some point, not re-raised and no errors or warning messages are 
generated.

OK, that's definitely a problem.

By the way, I tried to verify the other bug you posted about calling 
non-existent XPath functions, but couldn't reproduce it (although I did 
find another bug with the resulting error message).  Can you please create 
a Jira report and attach the necessary files to reproduce it?

Thanks!

Dave

---------------------------------------------------------------------
To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xalan-dev-help@xml.apache.org


Re: Changes, bugs, etc. between 1.8 and 1.9

Posted by Brian Quinlan <br...@sweetapp.com>.
david_n_bertoni@us.ibm.com wrote:
> Can you be more specific about what you mean when you say "without a 
> stylesheet'?  Do you mean the code path where the processor looks in the 
> source document for any stylesheet PIs?

Sorry, yes. In Xalan 1.8, if no stylesheet was explicitly specified and 
the XML source document didn't contain a processing instruction, then a 
ProcessorError was raised. In Xalan 1.9, a warning is generated. The 
exception was more convient for me

>>o XSLError is no longer raised when a call to write() on the output
>>  stream is called (seems like a bug; an exception would be best
>>   but at least an error or warning should be generated)
> 
> 
> You said: "when a call to write() on the output stream is called".  I'm 
> not sure I understand.  Do you mean  a call to write() is failing, and no 
> error is returned?  That would definitely be a bug.

My InputSource's write method raises an exception everytime it is 
called (this is part of my test suite). In Xalan 1.8, the exception 
propogated back to the top. In Xalan 1.9 the exception is caught at 
some point, not re-raised and no errors or warning messages are generated.

Cheers,
Brian

---------------------------------------------------------------------
To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xalan-dev-help@xml.apache.org


Re: Changes, bugs, etc. between 1.8 and 1.9

Posted by da...@us.ibm.com.
> I've just rebuilt one of my projects against 1.9 and rerun the test 
> suite. Here are some of the semantic changes that I've found. Would it 
> be possible for someone to tell me which of these I should file as bugs 
> and which are desired changes?
> 
> o No ProcessorError is raised when a transformation is done on an XML
>    document without a stylesheet (a warning is generated; this behavior
>    is arguably correct)

Can you be more specific about what you mean when you say "without a 
stylesheet'?  Do you mean the code path where the processor looks in the 
source document for any stylesheet PIs?

> o XSLError is no longer raised when a call to write() on the output
>   stream is called (seems like a bug; an exception would be best
>    but at least an error or warning should be generated)

You said: "when a call to write() on the output stream is called".  I'm 
not sure I understand.  Do you mean  a call to write() is failing, and no 
error is returned?  That would definitely be a bug.

> o Calls to non-existant XPath functions do longer generate an exception
>    (seems like bug)

That's absolutely a bug!

> o Invalid XPath expressions based as top level arguments do not generate
>    exceptions e.g. "foo()" or "((((" (seems like a bug)

Bug for sure.

> o Possible memory leak with InputSource objects returned by
>    EntityResolvers (need to investige more; i've called wolf on this
>    before)

That's probably a Xerces-C issue, if you can reproduce it.

Feel free to file any or all of these as bugs.  Thanks!

Dave

---------------------------------------------------------------------
To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xalan-dev-help@xml.apache.org


Changes, bugs, etc. between 1.8 and 1.9

Posted by Brian Quinlan <br...@sweetapp.com>.
I've just rebuilt one of my projects against 1.9 and rerun the test 
suite. Here are some of the semantic changes that I've found. Would it 
be possible for someone to tell me which of these I should file as bugs 
and which are desired changes?

o No ProcessorError is raised when a transformation is done on an XML
   document without a stylesheet (a warning is generated; this behavior
   is arguably correct)
o XSLError is no longer raised when a call to write() on the output
   stream is called (seems like a bug; an exception would be best
   but at least an error or warning should be generated)
o Calls to non-existant XPath functions do longer generate an exception
   (seems like bug)
o Invalid XPath expressions based as top level arguments do not generate
   exceptions e.g. "foo()" or "((((" (seems like a bug)
o Possible memory leak with InputSource objects returned by
   EntityResolvers (need to investige more; i've called wolf on this
   before)

Cheers,
Brian

---------------------------------------------------------------------
To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xalan-dev-help@xml.apache.org


[jira] Resolved: (XALANC-446) XALAN_C 1.9 or current do not build on Fedora core 3

Posted by "David Bertoni (JIRA)" <xa...@xml.apache.org>.
     [ http://nagoya.apache.org/jira/browse/XALANC-446?page=history ]
     
David Bertoni resolved XALANC-446:
----------------------------------

     Resolution: Fixed
    Fix Version: CurrentCVS

Changes are in CVS.  Can you please verify?  Thanks!

> XALAN_C 1.9 or current do not build on Fedora core 3
> ----------------------------------------------------
>
>          Key: XALANC-446
>          URL: http://nagoya.apache.org/jira/browse/XALANC-446
>      Project: XalanC
>         Type: Bug
>     Versions: 1.9
>  Environment: Fedora core 3,
> gcc (GCC) 3.4.2 20041017 (Red Hat 3.4.2-6.fc3)
> Xalan-C_1_9_0-src.tar.gz & Xalan-C_current-src.tar.gz
> untarred via tar zxvf file...
> ./runConfigure -plinux -cgcc -xg++ -rpthread
>     Reporter: Olivier Epicoco
>     Priority: Blocker
>      Fix For: CurrentCVS

>
> Two types of errors:
> 1- runConfigure and configure are not executable (I had to 'chmod -R a+x *configure' to start the compilation)
> 2- Cannot compile the source: XPath/XPathEvaluator.cpp 
> because XPath/ElementPrefixResolverProxy.hpp contains an unimplemented copy constructor
> See below more details:
> g++ -O2 -DNDEBUG     -fno-elide-constructors -Wall -fPIC -DLINUX -D_REENTRANT -D XALAN_INMEM_MSG_LOADER -c -I/opt/local/xml-xalan/c/src -I/opt/local/xml-xalan/c/ include -I../../nls/include -I/opt/local/xerces-c-src_2_6_0/src/ -I/opt/local/xe rces-c-src_2_6_0/include/xercesc -I/opt/local/xerces-c-src_2_6_0/include/  -o .. /../obj/XPathEnvSupportDefault.o /opt/local/xml-xalan/c/src/xalanc/XPath/XPathEn vSupportDefault.cpp
> g++ -O2 -DNDEBUG     -fno-elide-constructors -Wall -fPIC -DLINUX -D_REENTRANT -D XALAN_INMEM_MSG_LOADER -c -I/opt/local/xml-xalan/c/src -I/opt/local/xml-xalan/c/ include -I../../nls/include -I/opt/local/xerces-c-src_2_6_0/src/ -I/opt/local/xe rces-c-src_2_6_0/include/xercesc -I/opt/local/xerces-c-src_2_6_0/include/  -o .. /../obj/XPathEvaluator.o /opt/local/xml-xalan/c/src/xalanc/XPath/XPathEvaluator. cpp
> /opt/local/xml-xalan/c/src/xalanc/XPath/ElementPrefixResolverProxy.hpp: In membe r function `xalanc_1_9::XObjectPtr xalanc_1_9::XPathEvaluator::evaluate(xalanc_1 _9::DOMSupport&, xalanc_1_9::XalanNode*, const xalanc_1_9::XalanDOMChar*, const xalanc_1_9::XalanElement*)':
> /opt/local/xml-xalan/c/src/xalanc/XPath/ElementPrefixResolverProxy.hpp:89: error : `xalanc_1_9::ElementPrefixResolverProxy::ElementPrefixResolverProxy(const xala nc_1_9::ElementPrefixResolverProxy&)' is private
> /opt/local/xml-xalan/c/src/xalanc/XPath/XPathEvaluator.cpp:279: error: within th is context
> /opt/local/xml-xalan/c/src/xalanc/XPath/ElementPrefixResolverProxy.hpp: In membe r function `xalanc_1_9::XObjectPtr xalanc_1_9::XPathEvaluator::evaluate(xalanc_1 _9::DOMSupport&, xalanc_1_9::XalanNode*, const xalanc_1_9::XPath&, const xalanc_ 1_9::XalanElement*)':
> /opt/local/xml-xalan/c/src/xalanc/XPath/ElementPrefixResolverProxy.hpp:89: error : `xalanc_1_9::ElementPrefixResolverProxy::ElementPrefixResolverProxy(const xala nc_1_9::ElementPrefixResolverProxy&)' is private
> /opt/local/xml-xalan/c/src/xalanc/XPath/XPathEvaluator.cpp:299: error: within th is context
> /opt/local/xml-xalan/c/src/xalanc/XPath/ElementPrefixResolverProxy.hpp: In membe r function `xalanc_1_9::XPath* xalanc_1_9::XPathEvaluator::createXPath(const xal anc_1_9::XalanDOMChar*)':
> /opt/local/xml-xalan/c/src/xalanc/XPath/ElementPrefixResolverProxy.hpp:89: error : `xalanc_1_9::ElementPrefixResolverProxy::ElementPrefixResolverProxy(const xala nc_1_9::ElementPrefixResolverProxy&)' is private
> /opt/local/xml-xalan/c/src/xalanc/XPath/XPathEvaluator.cpp:348: error: within th is context
> /opt/local/xml-xalan/c/src/xalanc/XPath/ElementPrefixResolverProxy.hpp: In membe r function `xalanc_1_9::XPath* xalanc_1_9::XPathEvaluator::createXPath(const xal anc_1_9::XalanDOMChar*, xalanc_1_9::DOMSupport&, const xalanc_1_9::XalanElement* )':
> /opt/local/xml-xalan/c/src/xalanc/XPath/ElementPrefixResolverProxy.hpp:89: error : `xalanc_1_9::ElementPrefixResolverProxy::ElementPrefixResolverProxy(const xala nc_1_9::ElementPrefixResolverProxy&)' is private
> /opt/local/xml-xalan/c/src/xalanc/XPath/XPathEvaluator.cpp:361: error: within th is context
> gmake[1]: *** [../../obj/XPathEvaluator.o] Error 1
> gmake[1]: Leaving directory `/opt/local/xml-xalan/c/src/xalanc'
> gmake: *** [all] Error 2

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://nagoya.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xalan-dev-help@xml.apache.org