Hi Jason, I have removed the autoconf "stuff". (The Xerces-C++ documentation talked about possibly needing the autoconf utility. Not knowing UNIX, I thought I needed to run it.) Essentially, I have started over. I downloaded the latest stable Xerces C++ binary file for Solaris. After unzipping it and untarring it, I noticed there was no src directory. I went back to the site and noticed there were also source files available. Why were there no source files in the binary tar file? Did I miss something? I did download the .gz source file but when I went to untar it I got checksum errors. I repeated the whole process several times and still got checksum errors. Since our development network has been disconnected from the internet, I cannot go directly to the UNIX machine but must go through a Windows system first. I don't know if this is corrupting the .gz source file. I can download the Windows file (the .zip extension). I will need to convert the source files from Windows to UNIX since a carriage return is at the end of each line. (I have a program to do that.) Is there a problem using these source files?
Thanks again, Maureen -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Wednesday, September 26, 2001 2:22 PM To: [EMAIL PROTECTED] Subject: Re: Error installing xerces-p on Solaris 2.6 "Altenau, Maureen D CECOM RDEC C2D" <[EMAIL PROTECTED]> writes: > The runConfigure script is in the samples directory. Yes, and there is one in the src/ directory as well. > I moved the configure script that was included with the autoconf > software into that directory and ran it. It seemed to run. It > created several directories and Makefiles. I did not set the -m and > -t switches. Is that a problem? Ackk!!! No, no, no, no!! First, you do *not* need autoconf, you are *not* going to modify the source code files, remove it from sight. I don't know where you got the idea that you needed it. Most Open Source software is built and installed in a series of very easy steps: * download tarball (foo.tar.gz) * untar the tarball (tar zxf foo.tar.gz, or gunzip foo.tar.gz && tar xf foo.tar * configure (or in the case of Xerces-C 'runConfigure') * make (or depending on your system 'gmake') * make install (or depending on your system 'gmake install') You first want to cd into the src/ directory and execute runConfigure there. You don't need the -t or -m flags, but it will use the defaults which you may not want if you are doing unicode processing. I don't do unicode, so it's fine for me. Then you will 'make' and 'make install'. After that, you want to go to the samples/ directory and execute that runConfigure script, then 'make' and 'make install' there as well. Then you can try out the sample programs that came with Xerces-C (e.g. DOMCount, SAXCount, etc) to ensure that you've got a working installation. The entire build system is set up for you, *DON'T* start moving files around!!! I would remove your build directory and unpack it from scratch. > Also, can I use make or do I need to use gmake? If you've got solaris, you don't want to use the system make that comes with solaris, you want to use the GNU make program which is usually installed as 'gmake'. If you run the command 'gmake --version' you should see: GNU Make version 3.79.1, by Richard Stallman and Roland McGrath. Built for powerpc-unknown-linux-gnu Copyright (C) 1988, 89, 90, 91, 92, 93, 94, 95, 96, 97, 98, 99, 2000 Free Software Foundation, Inc. or something similar. jas. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
