You are viewing a plain text version of this content. The canonical link for it is here.
Posted to c-dev@xerces.apache.org by "Stevens, Paul (EDS)" <p....@wcom.co.uk> on 2001/03/01 13:03:09 UTC

FW: XML4C for C++ : runConfigure does not recognise HP-11


> -----Original Message-----
> From:	Stevens, Paul (EDS) 
> Sent:	01 March 2001 11:55
> To:	'xerces-c-dev@xml.apache.org'
> Subject:	XML4C for C++ : runConfigure does not recognise HP-11
> 
> Hello Xerces Team
> 
> I am trying to build XML4C for the HP-11
> and have followed the instructions in the provided document to the letter.
> 
<< build.html >>  (Your mail system will not let me send this attachment)

> I have a couple of issues, is there anyone who can answer these?
> 
> Thanks,
> Paul
> 
> (1) The gunzip and tar does not create the src directory referred to in
> the build notes.
> (2) I have run autoconf in the samples directory instead.
> (3) There are less options provided by runConfigure than what you state in
> your notes.
> ==============================================================
> 
> /arbor/data/BUSMARK_WORK_DATA/pstevens/xml/samples> runConfigure
> runConfigure: Helper script to run "configure" for one of the supported
> platforms
> Usage: runConfigure "options"
>        where options may be any of the following:
>        -p <platform> (accepts 'aix', 'linux', 'solaris',
> 'hp-10', 'hp-11', 'os400', 'irix', 'ptx', 'tru64')
>        -c <C compiler name> (e.g. gcc, xlc or icc)
>        -x <C++ compiler name> (e.g. g++, xlC, or icc)
>        -d (specifies that you want to build debug version)
>        -h (get help on the above commands)
>        -z <extra compiler options>
> 
> (4) I have entered the following but get an error message saying machine
> -hp not recongnised:-
> ==========================================================================
> ====================
> 
> /arbor/data/BUSMARK_WORK_DATA/pstevens/xml/samples> runConfigure -php-11
> -ccc -xaCC
> Generating makefiles with the following options ...
> Platform: hp-11
> C Compiler: cc
> C++ Compiler: aCC
> Debug is OFF
> 
> creating cache ./config.cache
> checking for gcc... cc
> checking whether the C compiler (cc  -w -O  -lC) works... yes
> checking whether the C compiler (cc  -w -O  -lC) is a cross-compiler... no
> checking whether we are using GNU C... no
> checking whether cc accepts -g... no
> checking for c++... aCC
> checking whether the C++ compiler (aCC  -w -O  -lC) works... yes
> checking whether the C++ compiler (aCC  -w -O  -lC) is a cross-compiler...
> yes
> checking whether we are using GNU C++... no
> checking whether aCC accepts -g... yes
> checking for a BSD compatible install... /opt/imake/bin/install -c
> checking for autoconf... autoconf
> checking for floor in -lm... yes
> checking for pthread_create in -lpthread... no
> checking for pthread_create in -lpthreads... no
> checking how to run the C preprocessor... cc -E
> checking for inttypes.h... yes
> checking host system type... Invalid configuration `-hp-hpux11.00':
> machine `-hp' not recognized
> 
> updating cache ./config.cache
> creating ./config.status
> creating Makefile
> creating SAXCount/Makefile
> creating SAX2Count/Makefile
> creating DOMCount/Makefile
> creating SAXPrint/Makefile
> creating SAX2Print/Makefile
> creating DOMPrint/Makefile
> creating MemParse/Makefile
> creating Redirect/Makefile
> creating PParse/Makefile
> creating StdInParse/Makefile
> creating EnumVal/Makefile
> creating CreateDOMDocument/Makefile
> 
> Having build problems? Read instructions at
> http://xml.apache.org/xerces-c/build.html
> 
> In future, you may also directly type the following commands to create the
> Makefiles.
> 
> export CC=cc
> export CXX=aCC
> export CXXFLAGS= -w -O
> export CFLAGS= -w -O
> export LIBS=-L/usr/lib -L/opt/aCC/lib
> export LDFLAGS=-lC
> configure
> 
> If the result of the above commands look OK to you, go to the directory
> /arbor/data/BUSMARK_WORK_DATA/pstevens/xml/samples and type "gmake" to
> make the samples.
> 
> (5) A core file has been created; when I run GNU make I get "not a valid
> object" for all .cpp files
> ==========================================================================
> =========================
> 
> K:/arbor/data/BUSMARK_WORK_DATA/pstevens/xml/samples> /usr/local/bin/make
> Building SAXPrint
> cd SAXPrint ; /usr/local/bin/make  ; cd ..
> make[1]: Entering directory
> `/arbor/data/BUSMARK_WORK_DATA/pstevens/xml/samples/SAXPrint'
> mkdir -p /arbor/data/BUSMARK_WORK_DATA/pstevens/xml/bin/obj/SAXPrint
> cc  -I. -I/arbor/data/BUSMARK_WORK_DATA/pstevens/xml/include -o
> /arbor/data/BUSMARK_WORK_DATA/pstevens/xml/bin/obj/SAXPrint/SAXPrint.o
> /arbor/data/BUSMARK_WORK_DATA/pstevens/xml/samples/SAXPrint/SAXPrint.cpp
> /usr/ccs/bin/ld:
> /arbor/data/BUSMARK_WORK_DATA/pstevens/xml/samples/SAXPrint/SAXPrint.cpp:
> Not a valid object file (invalid system id)
> make[1]: ***
> [/arbor/data/BUSMARK_WORK_DATA/pstevens/xml/bin/obj/SAXPrint/SAXPrint.o]
> Error 1
> make[1]: Leaving directory
> `/arbor/data/BUSMARK_WORK_DATA/pstevens/xml/samples/SAXPrint'
> Building SAX2Print
> cd SAX2Print ; /usr/local/bin/make  ; cd ..
> make[1]: Entering directory
> `/arbor/data/BUSMARK_WORK_DATA/pstevens/xml/samples/SAX2Print'
> mkdir -p /arbor/data/BUSMARK_WORK_DATA/pstevens/xml/bin/obj/SAX2Print
> cc  -I. -I/arbor/data/BUSMARK_WORK_DATA/pstevens/xml/include -o
> /arbor/data/BUSMARK_WORK_DATA/pstevens/xml/bin/obj/SAX2Print/SAX2Print.o
> /arbor/data/BUSMARK_WORK_DATA/pstevens/xml/samples/SAX2Print/SAX2Print.cpp
> /usr/ccs/bin/ld:
> /arbor/data/BUSMARK_WORK_DATA/pstevens/xml/samples/SAX2Print/SAX2Print.cpp
> : Not a valid object file (invalid system id)
> 
> etc etc
> 
>