Re: libxml building (2491 Views)
Reply
Advisor
AlexanderM
Posts: 19
Registered: ‎09-26-2013
Message 1 of 20 (2,738 Views)
Accepted Solution

libxml building

[ Edited ]

Hello to everybody.

  • Xml parser is required for using with c.
  • I have not admin privilegies => standard solution is not appropriate.
  • I've choose libxml
  • Sourses include .vms directory with .com file

The first problem is: how to run .com file.

I've tried to use @ for example @filename.com, but it has not worked.

Advisor
AlexanderM
Posts: 19
Registered: ‎09-26-2013
Message 2 of 20 (2,722 Views)

Re: libxml building

  • error
> @build_libxml.com
%DCL-W-UNDSYM, undefined symbol - check validity and spelling
\\
%DCL-W-NOCOMD, no command on line - reenter with alphabetic first character
%DCL-W-UNDSYM, undefined symbol - check validity and spelling
\\
%DCL-W-UNDSYM, undefined symbol - check validity and spelling
\WHOAMI\
%RMS-F-SYN, file specification syntax error
 
  • Readme file contains the next: 

- File attributes.  Having downloaded essentially a Unix distribution, some
  of the file attributes weren't correct... especially those in the [.VMS]
  subdirectory.  In EDT you could see line feeds and carriage returns as
  <LF><CR> etc.  To correct this use the command

    $ set file <filespec> /attr=rfm=stm

 

but this command does not work too:

set file build_libxml.com/attr=rfm=asmd
%DCL-W-IVKEYW, unrecognized keyword - check validity and spelling
\ASMD\
Frequent Advisor
Maurizio De Tommaso_
Posts: 42
Registered: ‎03-11-2004
Message 3 of 20 (2,709 Views)

Re: libxml building

[ Edited ]

The correct syntax of the "Set file /attrib" OpenVMS command is :

 

$ Set File /Attrib=(rfm:stm)  <filespec>

 

The following table lists the keywords and the relationship to both ACP-QIO and OpenVMS RMS File attributes:

 

Keyword            ACP-QIO File Attribute                                OpenVMS RMS FileAttribute

RFM:FIX             FAT$V_RTYPE=FAT$C_FIXED                    FAB$B_RFM=FAB$C_FIX
RFM:STM           FAT$V_RTYPE=FAT$C_STREAM               FAB$B_RFM=FAB$C_STM         <==
RFM:STMCR      FAT$V_RTYPE=FAT$C_STREAMCR          FAB$B_RFM=FAB$C_STMCR
RFM:STMLF      FAT$V_RTYPE=FAT$C_STREAMLF           FAB$B_RFM=FAB$C_STMLF
RFM:UDF           FAT$V_RTYPE=FAT$C_UNDEFINED         FAB$B_RFM=FAB$C_UDF
RFM:VAR          FAT$V_RTYPE=FAT$C_VARIABLE             FAB$B_RFM=FAB$C_VAR
RFM:VFC           FAT$V_RTYPE=FAT$C_VFC                        FAB$B_RFM=FAB$C_VFC

 

RFM:ASMD is not a valid file attibuite under OpenVMS.

 

As reported by the README, you should modify the file attribute of all vms specific files (only ascii format not binary), for example :

 

$ Set File/Attrib=RFM:STM [.vms]*.c,[.vms...]*.h,[.vms...]*.txt

 

But I don't exclude that you should modify also the file attribuite of other Source Codes of the libmxl distribution kit. Take a look into the libxml.com command procedure.

 

>>> I have not admin privilegies => standard solution is not appropriate

 

I suspect that your experiment will require also the "system" privileges...

 

Good luck,

/Maurizio

Advisor
AlexanderM
Posts: 19
Registered: ‎09-26-2013
Message 4 of 20 (2,686 Views)

Re: libxml building

Thanks)

Advisor
AlexanderM
Posts: 19
Registered: ‎09-26-2013
Message 5 of 20 (2,678 Views)

Re: libxml building

[ Edited ]

Is helps, but not compleatly. I've got an error in the next fragment of com file:

 
$whoami = f$parse(f$environment("PROCEDURE"),,,,"NO_CONCEAL")
$   procdir = f$parse(whoami,,,"DEVICE") + f$parse(whoami,,,"DIRECTORY")
$   set default 'procdir'
 

Is the 'smth'  the equivalent of $smth in linux i.e. is this an getting of variable smth value?
Frequent Advisor
Maurizio De Tommaso_
Posts: 42
Registered: ‎03-11-2004
Message 6 of 20 (2,659 Views)

Re: libxml building

[ Edited ]

Can you post the error that you observe when you run the command file ?

 

Your dcl code runs error free on my system (I inserted few lines only for the troubleshooting purposes)  :

 

$!  Test_alexander.com

$!
$   whoami  = f$parse(f$environment("PROCEDURE"),,,,"NO_CONCEAL")
$   write sys$output " "
$   write sys$output "whoami symbol = ''whoami'"
$   write sys$output " "
$   procdir = f$parse(whoami,,,"DEVICE") + f$parse(whoami,,,"DIRECTORY")
$   write sys$output " "
$   write sys$output "procdir symbol = ''procdir'"
$   write sys$output " "
$   set default 'procdir'
$!
$   Exit

 

$ sho def

    $2$DKA100:[000000]

 

$ @test_alexander

 

whoami symbol = $2$DKA100:[000000]test_alexander.com;1


procdir symbol = $2$DKA100:[000000]

 

$ sho def

    $2$DKA100:[000000]

 

Regards,

/Maurizio

Advisor
AlexanderM
Posts: 19
Registered: ‎09-26-2013
Message 7 of 20 (2,633 Views)

Re: libxml building

[ Edited ]

Sometimes I forget that there are no telepathists on this forum).

System: OpenVMS ALpha 8.3

The script is (I've inserted WRITE SYS$OUTPUT "tag" to locate the error):

$! BUILD_LIBXML.COM
$!
$! Build the LIBXML library
$!
$! Arguments:
$!
$!       "DEBUG"  - build everything in debug
$!
$! This procedure creates an object library XML_LIBDIR:LIBXML.OLB directory.
$! After the library is built, you can link LIBXML routines into
$! your code with the command
$!
$!      $ LINK your_modules,XML_LIBDIR:LIBXML.OLB/LIBRARY
$!
$! Change History
$! --------------
$! Command file author : John A Fotheringham (jaf@jafsoft.com)
$! Update history      : 19 March 2008  Tycho Hilhorst
$!                       - added module schematron.c (prevent xmllint errors)
$!                       - added /DEF and /INCLUDE options to cc_opts to tell
$!                         config.h is available, and where to find it
$!                     : 13 October 2003        Craig Berry (craigberry@mac.com)
$!                       more new module additions
$!                     : 25 April 2003          Craig Berry (craigberry@mac.com)
$!                       added xmlreader.c and relaxng.c to source list
$!                      : 28 September 2002       Craig Berry (craigberry@mac.com)
$!                       updated to work with current sources
$!                       miscellaneous enhancements to build process
$!
$!- configuration -------------------------------------------------------------
$!
$!- compile command.  If p1="nowarn" suppress the expected warning types
$!
$   cc_opts = "/DEF=HAVE_CONFIG_H/NAMES=(SHORTENED)/FLOAT=IEEE/IEEE_MODE=DENORM_RESULTS/INCLUDE=xml_srcdir"
$!
$   if p1.eqs."DEBUG" .or. p2.eqs."DEBUG"
$   then
$     debug = "Y"
$     cc_command = "CC''cc_opts'/DEBUG/NOOPTIMIZE/LIST/SHOW=ALL"
$   else
$     debug = "N"
$     cc_command = "CC''cc_opts'"
$   endif
$!
$!- list of sources to be built into the LIBXML library.  Compare this list
$!  to the definition of "libxml2_la_SOURCES" in the file MAKEFILE.IN.
$!  Currently this definition includes the list WITH_TRIO_SOURCES_TRUE
$!
$   sources = "SAX.c entities.c encoding.c error.c parserInternals.c"
$   sources = sources + " parser.c tree.c hash.c list.c xmlIO.c xmlmemory.c uri.c"
$   sources = sources + " valid.c xlink.c HTMLparser.c HTMLtree.c debugXML.c xpath.c"
$   sources = sources + " xpointer.c xinclude.c nanohttp.c nanoftp.c DOCBparser.c"
$   sources = sources + " catalog.c globals.c threads.c c14n.c xmlstring.c"
$   sources = sources + " xmlregexp.c xmlschemas.c xmlschemastypes.c xmlunicode.c"
$   sources = sources + " triostr.c trio.c xmlreader.c relaxng.c dict.c SAX2.c"
$   sources = sources + " xmlwriter.c legacy.c chvalid.c pattern.c xmlsave.c"
$   sources = sources + " schematron.c"
$!
$!- list of main modules to compile and link.  Compare this list to the
$!  definition of bin_PROGRAMS in MAKEFILE.IN
$!
$   bin_progs = "xmllint xmlcatalog"
$!
$!- list of test modules to compile and link.  Compare this list to the
$!  definition of noinst_PROGRAMS in MAKEFILE.
$!
$   noinst_PROGRAMS = "testSchemas testRelax testSAX testHTML testXPath testURI " -
                + "testThreads testC14N testAutomata testRegexp testReader"
$!
$!- set up build logicals -----------------------------------------------------\
$!
$!
$!- start from where the procedure is in case it's submitted in batch ----------\
$!
$   whoami = f$parse(f$environment("PROCEDURE"),,,,"NO_CONCEAL")
$   procdir = f$parse(whoami,,,"DEVICE") + f$parse(whoami,,,"DIRECTORY")
$ WRITE SYS$OUTPUT "tag1"
$   set default 'procdir'
$ WRITE SYS$OUTPUT "tag2"

 The error is:

Wx01> @build_libxml.com
tag1
%RMS-F-DIR, error in directory name

 After it the system lost an ability to resolve correctlu current path:

dir
%DIRECT-E-OPENIN, error opening $1$DGA123:[ALEXANDER.VAX_ESF.LIBXML2-2_9_1.V
MS]*.*;* as input
-RMS-E-DNF, directory not found
-SYSTEM-W-NOSUCHFILE, no such file

This is the error in sources from official libxml site.

I've found more specialized port of sources.

Now:

  1. I'll try to run script from Maurizio De Tommaso_.
  2. Build port of sources.

Results of experiment will be reported. May be it will be usefull for somebody else.

PS. Thanks for help and your time.

Honored Contributor
Volker Halle
Posts: 5,206
Registered: ‎04-26-2004
Message 8 of 20 (2,625 Views)

Re: libxml building

Alexander,

 

instead of WRITE SYS$OUTPUT "tag1", insert the following:

 

...

$   whoami = f$parse(f$environment("PROCEDURE"),,,,"NO_CONCEAL")
$   procdir = f$parse(whoami,,,"DEVICE") + f$parse(whoami,,,"DIRECTORY")
$ WRITE SYS$OUTPUT whoami

$ WRITE SYS$OUTPUT procdir
$   set default 'procdir'

...

 

Volker.

Advisor
AlexanderM
Posts: 19
Registered: ‎09-26-2013
Message 9 of 20 (2,620 Views)

Re: libxml building

[ Edited ]

I've run script from Maurizio De Tommaso_.
Script:

Spoiler
$!  test.com
$!
$   whoami  = f$parse(f$environment("PROCEDURE"),,,,"NO_CONCEAL")
$   write sys$output " "
$   write sys$output "whoami symbol = ''whoami'"
$   write sys$output " "
$   procdir = f$parse(whoami,,,"DEVICE") + f$parse(whoami,,,"DIRECTORY")
$   write sys$output " "
$   write sys$output "procdir symbol = ''procdir'"
$   write sys$output " "
$   set default 'procdir'
$!
$   Exit

 

 

Result:

WX01> @test.com

whoami symbol = $1$DGA123:[TST$USERS.][ALEXANDER.VAX.LIBXML2-2_9_1]TEST.
COM;1


procdir symbol = $1$DGA123:[TST$USERS.][ALEXANDER.VAX.LIBXML2-2_9_1]

%RMS-F-DIR, error in directory name

 The same error occured.

Advisor
AlexanderM
Posts: 19
Registered: ‎09-26-2013
Message 10 of 20 (2,609 Views)

Re: libxml building

[ Edited ]

Volker,

I've implemented your suggestion.
Result is the next:

WX01> @build_libxml.com
$1$DGA123:[TST$USERS.][ALEXANDER.VAX_ESF.LIBXML2-2_9_1.VMS]BUILD_LIBXML.COM;

$1$DGA123:[TST$USERS.][ALEXANDER.VAX_ESF.LIBXML2-2_9_1.VMS]
%RMS-F-DIR, error in directory name

 

It seems that the result is the same.

Honored Contributor
Volker Halle
Posts: 5,206
Registered: ‎04-26-2004
Message 11 of 20 (2,597 Views)

Re: libxml building

[ Edited ]

Alexander,

 

the problem is in the directory name:

 

$ set def $1$DGA123:[TST$USERS.][ALEXANDER.VAX.LIBXML2-2_9_1]
%RMS-F-DIR, error in directory name
$ set def $1$DGA123:[TST$USERS.ALEXANDER.VAX.LIBXML2-2_9_1]   ! this works !

 

As a workaround, try setting your default directory using the working SET DEFAULT command above, before you invoke @build_libxml.com

 

 

Solving this problem would most likely require a concealed logical name and changes to your account in SYSUAF:

 

$ define/sys/exec/transl=conc tst$users $1$DGA123:[TST$USERS.]

And your login-directory should become something like TST$USERS:[ALEXANDER]

 

Volker.

Advisor
AlexanderM
Posts: 19
Registered: ‎09-26-2013
Message 12 of 20 (2,584 Views)

Re: libxml building

Thanks. Thsi error is fixed. But there are many another in compillation dependences.  I'll try to resolve it.

 

PS. But in general, I am looking for small xml library with validation written in pure c (or binaries for openvms alpha). It is an ideal if it will have only one library file and header. I want just include it in my project without any system installing.

Regular Advisor
Jansen_8
Posts: 109
Registered: ‎11-06-2005
Message 13 of 20 (2,568 Views)

Re: libxml building

I sucessfully compiled libxml2 for OpenVMS 8.4. See for the the modifactions I had to make:

  http://nchrem.tnw.tudelft.nl/openvms/software2.html#LIBXML2

 

Note that I always set the compilation qualifiers /float=ieee/name=(as_is,short).

The only reason, I do this is that this works for all packages displayed on my web-page, so ensuring inter-package comaptibility.

 

                            Jouk

Advisor
AlexanderM
Posts: 19
Registered: ‎09-26-2013
Message 14 of 20 (2,555 Views)

Re: libxml building

Thanks for the advice.

I've located patch contents into corresponding folders and get the same error:

 

 
Spoiler
$whoami = f$parse(f$environment("PROCEDURE"),,,,"NO_CONCEAL")
$   procdir = f$parse(whoami,,,"DEVICE") + f$parse(whoami,,,"DIRECTORY")
$   set default 'procdir'

 

 
I've resolved it with manual pointing of paths.
After this I've got next compiller errors:
Spoiler
CC/nowarn/DEF=HAVE_CONFIG_H/NAMES=(as_is,SHORTENED)/FLOAT=IEEE/IEEE_MODE=DENORM_
RESULTS/INCLUDE=xml_srcdir/object=TST$USERS:[ALEXANDER.LIBXML2-2_9_1.DEBUG]PAR
SER.OBJ; PARSER.C
 
    (const xmlChar *) "http://www.w3.org/XML/1998/namespace".
.....^
%CC-E-DECLARATOR, Invalid declarator.
at line number 140 in file TST$USERS:[ALEXANDER.LIBXML2-2_9_1.INCLUDE.LIBXML]T
REE.H;1
 
    xmlElementType          type;       /* XML_ATTRIBUTE_DECL, must be second !
*/.
....^
%CC-E-MISSINGTYPE, Missing type specifier or type qualifier.
at line number 254 in file TST$USERS:[ALEXANDER.LIBXML2-2_9_1.INCLUDE.LIBXML]T
REE.H;1
 
    xmlElementType          type;       /* XML_ELEMENT_DECL, must be second ! */
.
....^
%CC-E-MISSINGTYPE, Missing type specifier or type qualifier.
at line number 347 in file TST$USERS:[ALEXANDER.LIBXML2-2_9_1.INCLUDE.LIBXML]T
REE.H;1
 
typedef xmlElementType xmlNsType;.
.......................^
%CC-E-NOSEMI, Missing ";".
at line number 374 in file TST$USERS:[ALEXANDER.LIBXML2-2_9_1.INCLUDE.LIBXML]T
REE.H;1
 
    xmlNsType      type;        /* global or local */.
....^
%CC-E-MISSINGTYPE, Missing type specifier or type qualifier.
at line number 390 in file TST$USERS:[ALEXANDER.LIBXML2-2_9_1.INCLUDE.LIBXML]T
REE.H;1
 
    ((n)->type == XML_ELEMENT_NODE ? NULL : (n)->content).
........^
%CC-E-CLOSEPAREN, Missing ")".
at line number 515 in file TST$USERS:[ALEXANDER.LIBXML2-2_9_1.INCLUDE.LIBXML]T
REE.H;1
 
        htmlElementAllowedHere((parent), (elt)->name).
...............................^
%CC-E-NOTEXPECTING, Error parsing parameter list. Found "(" when expecting one o
f: <type-specifier>, <identifier>, "...", ")".
at line number 291 in file TST$USERS:[ALEXANDER.LIBXML2-2_9_1.INCLUDE.LIBXML]H
TMLPARSER.H;1
 
typedef xmlChSRange *xmlChSRangePtr;.
....................^
%CC-E-NOSEMI, Missing ";".
at line number 29 in file TST$USERS:[ALEXANDER.LIBXML2-2_9_1.INCLUDE.LIBXML]CH
VALID.H;1
 
                                 ((0x61 <= (c)) && ((c) <= 0x7a)) || \.
...................................^
%CC-E-DECLARATOR, Invalid declarator.
at line number 65 in file TST$USERS:[ALEXANDER.LIBXML2-2_9_1.INCLUDE.LIBXML]CH
VALID.H;1
 
                                 xmlIsPubidChar_ch((c)) : 0).
........................................................^
%CC-E-NOSEMI, Missing ";".
at line number 208 in file TST$USERS:[ALEXANDER.LIBXML2-2_9_1.INCLUDE.LIBXML]C
HVALID.H;1
 
                                 ((0x61 <= (c)) && ((c) <= 0x7a))).
...................................^
%CC-E-DECLARATOR, Invalid declarator.
at line number 251 in file TST$USERS:[ALEXANDER.LIBXML2-2_9_1.INCLUDE.LIBXML]P
ARSERINTERNALS.H;1
 
    if (*(p) == 0x10) { p++ ; if (*(p) == 0x13) p++; }.
....^
%CC-E-DECLARATOR, Invalid declarator.
at line number 289 in file TST$USERS:[ALEXANDER.LIBXML2-2_9_1.INCLUDE.LIBXML]P
ARSERINTERNALS.H;1
 
    while ((*p) && (*(p) != '>')) (p)++.
....^
%CC-E-DECLARATOR, Invalid declarator.
at line number 298 in file TST$USERS:[ALEXANDER.LIBXML2-2_9_1.INCLUDE.LIBXML]P
ARSERINTERNALS.H;1
 
    (const xmlChar *) "urn:oasis:names:tc:entity:xmlns:xml:catalog".
.....^
%CC-E-DECLARATOR, Invalid declarator.
at line number 38 in file TST$USERS:[ALEXANDER.LIBXML2-2_9_1.INCLUDE.LIBXML]CA
TALOG.H;1
 
                xmlCatalogSetDefaultPrefer(xmlCatalogPrefer prefer);.
................^
%CC-E-NOSEMI, Missing ";".
at line number 165 in file TST$USERS:[ALEXANDER.LIBXML2-2_9_1.INCLUDE.LIBXML]C
ATALOG.H;1
 
    ctxt->str_xml_ns = xmlDictLookup(ctxt->dict, XML_XML_NAMESPACE, 36);.
..................................................................^
%CC-E-BADEXPR, Invalid expression.
at line number 1043 in file TST$USERS:[ALEXANDER.LIBXML2-2_9_1]PARSER.C;1
 
  ( ((unsigned char *) s)[ 0 ] == c1 && ((unsigned char *) s)[ 1 ] == c2 && \.
......^
%CC-E-DECLARATOR, Invalid declarator.
at line number 1985 in file TST$USERS:[ALEXANDER.LIBXML2-2_9_1]PARSER.C;1
 
    if (*ctxt->input->cur == '%') xmlParserHandlePEReference(ctxt);     \.
....^
%CC-E-DECLARATOR, Invalid declarator.
at line number 2019 in file TST$USERS:[ALEXANDER.LIBXML2-2_9_1]PARSER.C;1
 
                 (ctxt->input->end - ctxt->input->cur < INPUT_CHUNK))   \.
......................^
%CC-E-CLOSEPAREN, Missing ")".
at line number 2038 in file TST$USERS:[ALEXANDER.LIBXML2-2_9_1]PARSER.C;1
 
        ctxt->input->col++;                                             \.
............^
%CC-E-NOSEMI, Missing ";".
at line number 2060 in file TST$USERS:[ALEXANDER.LIBXML2-2_9_1]PARSER.C;1
 
    } else ctxt->input->col++;                                          \.
......^
%CC-E-DECLARATOR, Invalid declarator.
at line number 2070 in file TST$USERS:[ALEXANDER.LIBXML2-2_9_1]PARSER.C;1
 
        while (IS_BLANK_CH(*cur)) {.
................................^
%CC-E-BADEXPR, Invalid expression.
at line number 2106 in file TST$USERS:[ALEXANDER.LIBXML2-2_9_1]PARSER.C;1
 
            while (IS_BLANK_CH(cur)) { /* CHECKED tstblanks.xml */.
...................................^
%CC-E-BADEXPR, Invalid expression.
at line number 2123 in file TST$USERS:[ALEXANDER.LIBXML2-2_9_1]PARSER.C;1
 
        } while (IS_BLANK(cur)); /* CHECKED tstblanks.xml */.
..............................^
%CC-E-BADEXPR, Invalid expression.
at line number 2137 in file TST$USERS:[ALEXANDER.LIBXML2-2_9_1]PARSER.C;1
 
    GROW;.
........^
%CC-E-BADEXPR, Invalid expression.
at line number 2195 in file TST$USERS:[ALEXANDER.LIBXML2-2_9_1]PARSER.C;1
 
        GROW;.
............^
%CC-E-BADEXPR, Invalid expression.
at line number 2226 in file TST$USERS:[ALEXANDER.LIBXML2-2_9_1]PARSER.C;1
 
                GROW;.
....................^
%CC-E-BADEXPR, Invalid expression.
at line number 2230 in file TST$USERS:[ALEXANDER.LIBXML2-2_9_1]PARSER.C;1
 
    } else if  ((RAW == '&') && (NXT(1) == '#')) {.
......^
%CC-E-NOWHILE, Missing "while".
at line number 2257 in file TST$USERS:[ALEXANDER.LIBXML2-2_9_1]PARSER.C;1
 
        GROW;.
............^
%CC-E-BADEXPR, Invalid expression.
at line number 2259 in file TST$USERS:[ALEXANDER.LIBXML2-2_9_1]PARSER.C;1
 
                GROW;.
....................^
%CC-E-BADEXPR, Invalid expression.
at line number 2263 in file TST$USERS:[ALEXANDER.LIBXML2-2_9_1]PARSER.C;1
 
    } else {.
......^
%CC-E-NOWHILE, Missing "while".
at line number 2286 in file TST$USERS:[ALEXANDER.LIBXML2-2_9_1]PARSER.C;1
 
%CC-F-TOOMANYERR, More than 30 errors were encountered in the course of compilat
ion.
%CC-F-ENDDIAGS, !AS completed with !UL diagnostic!%S
%PURGE-W-SEARCHFAIL, error searching for TST$USERS:[ALEXANDER.LIBXML2-2_9_1.DE
BUG]*.*;*
-RMS-E-FNF, file not found

 

 

May be it was called by compiller version (DEC C V6.0-001 on OpenVMS Alpha V 8.3).
Esteemed Contributor
H.Becker
Posts: 373
Registered: ‎04-09-2009
Message 15 of 20 (2,551 Views)

Re: libxml building

> Solving this problem would most likely require a concealed logical name ...

 

Hmm, to me it looks like there is already a concealed device, otherwise the result of f$parse (..."no_conceal") wouldn't contain the ".][".  And that is what the writer of the DCL script wanted, as that's the meaning of the parse-type "no_conceal". To me it looks like a bug in the script.

Esteemed Contributor
H.Becker
Posts: 373
Registered: ‎04-09-2009
Message 16 of 20 (2,540 Views)

Re: libxml building

    (const xmlChar *) "http://www.w3.org/XML/1998/namespace".

If that's an exact cut and paste from the compiler message, then it looks like there is still a trailing character, which is shown as ".", here. As we all know, C would expect a ";" at the end. Also, as can be seen in the git repository, the tree.h include file has a

#define XML_XML_NAMESPACE \
    (const xmlChar *) "http://www.w3.org/XML/1998/namespace"

 To me it looks like the "\" is not seen as the last character before the end of the record, so the #define is not continued, hence it is seen as a separate, but invalid declaration => %CC-E-DECLARATOR

Honored Contributor
Bill Hall
Posts: 249
Registered: ‎07-21-2003
Message 17 of 20 (2,529 Views)

Re: libxml building

Try this code should handle the logical device correctly:

 

$!  Test_alexander.com
$!
$   whoami  = f$environment("PROCEDURE")
$   procdev = f$parse(whoami,,,"DEVICE","no_conceal")
$   procdir = f$parse(whoami,,,"DIRECTORY","no_conceal")
$   procdir = procdir -"][" - "><" - "[" - "]" - "<" - ">"
$   procdir = "[" + procdir + "]"
$   procdir = procdev + procdir
$   set default 'procdir'
$!
$   Exit

 

Bill

Bill Hall
Esteemed Contributor
H.Becker
Posts: 373
Registered: ‎04-09-2009
Message 18 of 20 (2,519 Views)

Re: libxml building

I'm sure that an Alpha or I64 has enough cpu cycles to do this extra processing, but before "fixing" anything I would like to understand what the purpose of "no_conceal" in this context really is: is it needed for a simple "set default" or is there anything else?

Honored Contributor
Bill Hall
Posts: 249
Registered: ‎07-21-2003
Message 19 of 20 (2,505 Views)

Re: libxml building

Hartmut,

 

Removing the "no_conceal" from the f$parse used to define the whoami symbol would also have worked for the definition of procdir and the subsequent set default 'procdir' as below.

 

$ whoami = f$parse(f$environment("PROCEDURE"))

$ procdir = f$parse(whoami,,,"DEVICE") + f$parse(whoami,,,"DIRECTORY")

$ set default 'procdir'

 

I jumped to the conclusion that the procdir symbol might be parsed as a string later in the procedure to build a temporary logical root or build a subdirectory or a file specification that would then fail.

Bill Hall
Advisor
AlexanderM
Posts: 19
Registered: ‎09-26-2013
Message 20 of 20 (2,491 Views)

Re: libxml building

I've rid from trail symbols. The library was built without any errors. Thanks for the help.

The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the Terms of Use and Rules of Participation.