Operating System - OpenVMS
1753906 Members
9137 Online
108810 Solutions
New Discussion юеВ

Re: C++ and XML compile problems - could not open source file

 
SOLVED
Go to solution
Steve Porter_2
Occasional Advisor

Re: C++ and XML compile problems - could not open source file

Hi Martin,

Yes, I do have V7.3-1. However, when we upgraded, there was no apparent need for any ODS-5 enabled drives. The HP XML kit requires ODS-5 (among other things), so I modified only the drive where I located the XML kit. So it seems what you are saying is that at least the system drive should be ODS-5 enabled, if not all the drives. Is that true?

Steve
Martin P.J. Zinser
Honored Contributor

Re: C++ and XML compile problems - could not open source file

Hello Steve,

no, just having the system disk on ODS-5 is not the solution (my test system at home has this and I get the same error).

Can you try to have a

#include and see if this is found?

Greetings, Martin
Steve Porter_2
Occasional Advisor

Re: C++ and XML compile problems - could not open source file

Nope, that did not do it.

Steve
Steve Porter_2
Occasional Advisor

Re: C++ and XML compile problems - could not open source file

So I have good news and bad news. I modified the XML build script to print out the process characteristics right before the compile, and someplace buried in there it changes the process to /case_lookup=blind. So the good news is that this change allows almost everything to compile, with the exception of the files that include the XML headers. Now I get

#include

..............................^

%CXX-E-SRCFILNOOPEN, could not open source file "xercesc/dom/DOM.hpp"

at line number 44 in file NGV03:[PORTER.TCP_CE_API.TCPCEAPICXX]TcpXML.HPP;2


The compile switches are the same as before.

Thanks, Steve
Martin P.J. Zinser
Honored Contributor
Solution

Re: C++ and XML compile problems - could not open source file

Do you have a logical xercesc? If yes how is it defined? What does dir xercesc:[dom]dom.hxx result in? The logical needs to be rooted to work.
Steve Porter_2
Occasional Advisor

Re: C++ and XML compile problems - could not open source file

There is a rooted logical xerces-c$root that is created by the XML kit, but not for xercesc. When I created it, the files I compiled manually work fine. However, my mms script still does not.

A question I still have though is how does the XML build script work. That does not define any logical (rooted or non-rooted) for xercesc. The only thing I can see is that when I do a sho proc/all in the middle of the script, the value for Default file spec is defined to be the same directory where I defined the xercesc root to be. Can you explain to me why?

Thanks, Steve
Steve Porter_2
Occasional Advisor

Re: C++ and XML compile problems - could not open source file

I modified my mms script to define the xercesc rooted logical for the job (define/job).

Thanks for all your help.

Steve
BGubenko
New Member

Re: C++ and XML compile problems - could not open source file

Apparently, /case_lookup=sensitive breaks processing of CRTL header files
in DECC$RTLDEF.TLB, at least angle bracketed form of inclusion, for both
C and C++. I'll post it in turris::cxxc_bugs notes file to make sure, that
this is either fixed or documented as a restriction.

Boris

x.c
---
#include

ALTOS::_1> cc/ver
Compaq C V6.5-001 on OpenVMS Alpha V7.3-1
ALTOS::_1> cxx/ver
Compaq C++ V6.5-004 for OpenVMS Alpha V7.3-1
ALTOS::_1>

ALTOS::_1> set process/parse=traditional

ALTOS::_1> set process/case_lookup=blind
ALTOS::_1> cc/noobj x.c
ALTOS::_1> cxx/noobj x.c
ALTOS::_1>

ALTOS::_1> set process/case_lookup=sensitive
ALTOS::_1> cc/noobj x.c

#include
.^
%CC-F-NOINCLFILEF, Cannot find file specified in #include directive.

ALTOS::_1> cxx/noobj x.c

#include
...................^
%CXX-E-SRCFILNOOPEN, could not open source file "limits.h"
ALTOS::_1>