DatacondAPI Library INSTALLATION NOTES

1 Import Changes
2 Retrieving the Source Code
- 2.1 The Entire System
3 Building the Source
- 3.1 Default configuration
- 3.2 Custom configuration
4 Reporting problems
- 4.1 Accessing GNATS via the Web
  - 4.1.1 Submitting a new problem report.
  - 4.1.2 Checking the status of a problem report
5 Calling DatacondAPI
6 Writing Translation Functions
7 Writing Algorithm Section
8 Caveats
9 Software Packages Used by DatacondAPI Library

Part 1
Installation

1 Import Changes

Version 1.8.0
- As of this release, a new method for building the Third party packages has been employed. Please refer to for full details.

2 Retrieving the Source Code

2.1 The Entire System

When building the entire system, there are two methods of obtaining the source code. The first is by ftping the tar-ball and the second is by CVS. The tar-ball distribution is the preferred method as this is a known stable version of the software. The CVS version is best for developers and others who need the latest developmental version of the DatacondAPI Library software.

2.1.1 Tar-ball distribution

With the tar-ball distribution, all of the source code is contained in one large tar archive that has been compress with GNU zip. Use the command "gzip -dc datacond-1.16.3.tar.gz - tar xf -" to extract the sources. This will create a subdirectory datacond-1.16.3. The latest version can be obtained from http://ldas-sw.ligo.caltech.edu/packages/datacond-1.16.3.tar.gz.

2.1.2 CVS distribution

The CVS repository is available via the web. It is a good way to browse the code and look for changes that may have affected the system in an adverse way. The location is https://ldas-sw.ligo.caltech.edu/cgi-bin/gnatsweb.cgi.

To retrieve sources from CVS you must have access to the CVS repository. If you do not already have access and feel that you need access, please contact Kent Blackburn or Albert Lazzarini with your request.

There are two flags. The "-D<DATE>" flag retrieves the most recent revision of the file that is no later than <DATE>. The date format is versatile and supports most any format of dates. Please see the man or info page for CVS for a complete description. The reserved <DATE> of "now" can be used to retrieve the latest version of the source code.

The "-r<TAG>" flag retrieves files belonging to the specified <TAG>. These tags have several variations to support different efforts. The most common is "ldas-<major_version>_<minor_version>_<patch_version>". These represent the official releases of the DatacondAPI Library software. The reserved <TAG> "HEAD" may be used to retrieve the latest version of the source code.

In all the commands listed below, it is assumed the most recent version of the software is desired. If not, please substitute "-rHEAD" with the appropriate flag as described above.

2.1.3 Retrieving the Relevant Pieces

To work with the most recent version of the LDAS software, follow the instructions below.

3 Building the Source

3.1 Default configuration

The DatacondAPI Library script "datacond-1.16.3/build-ldas" (or "ldas/build-ldas " if building from CVS) will examine the system, configure the software, and build all libraries and APIs. Currently the only supported operating systems are Solaris 10 and CentOS 5.2.

3.2 Custom configuration

There are many options to datacond-1.16.3/build-ldas to modify its default behavior. datacond-1.16.3/build-ldas takes options starting with two hyphens (--) as options that need to be passed to configure. Options that start with a single hyphen (-) are options interpreted only by datacond-1.16.3/build-ldas.

Of special note is the building of the metadataAPI. It is not necessary to build this API unless needing to interact with a database. The LDAS system uses DB2 under Solaris. On other systems, the iODBC library can be linked against to produce the shared object. The other option, which is cleaner, is the disabling of the building of the metadataAPI shared object. This is achieved by the --enable-metadata-api=no flag. See below.

3.2.1 datacond-1.16.3/build-ldas Options

Option Name	Description

-help	Print help message and then exit
-config-only	Do all steps up to and including configuration
-force	Don't stop make on errors
-install	Perform the installation step.
-no-stow	Don't use stow's installation paradigm.
-mail[=ADDR]	Mail know warning messages and known error messages. If ADDR is specified it is used, else the mail is sent to the invoking user.
-parallel[=NUM]	Make use of parallel make. If NUM is specified, then only spawn NUM subprocesses, else spawn as many as possible.
-tmpdir[=DIR]	Specify the location of temporary files. The default value is the current directory.
-distcheck	This option causes the build process to verify the integrity of the build process by first creating a tarball and then running configure, make and make check using the files from the tarball. NOTE: This option will not work if used on a tarball distribution since the tarball distribution cannot make a tarball of itself. It is best to run make check by hand in the buid directory of a tarball distribution to verify the build at the unit level.
-warn-unsupported-compiler	This option allows the user to try compiling with a compiler that has not been certified. It changes the error level of unsupported compiler from fail to warning. If this option is used with a supported compiler, no message is generated.

3.2.2 Configure Options

Option	Description

--prefix=PREFIX	install architecture-independent files in PREFIX [/ldas/ldas-0.0]
--enable-metadata-api[=yes]	build the metadata API
--disable-tcl	Specifically disable all TCL bindings. This was added for building the datacond library package without TCL.
--with-extra-cxxflags	Additional C++ compiler flags
--with-extra-ldflags	Additional linker flags
--with-ldflags	Replace linker flags
--with-mountpt	Specify frame builder directory
--with-optimization	Compiler optimization [extreme - high - medium - low - none]
--enable-inlining	forces inlining of code
--with-ospace[=DIR]	ObjectSpace directory

3.2.3 datacond-1.16.3/build-ldas Options - View status of the LDAS build

The options described here should be used after the build-script completes with the compilation of the LDAS software. The will grep the log files and return information about how the compilation completed. If there is a need to examine the full context of messages, the log files are in a subdirectory of the build-ldas script of: "`uname`-`uname -m`/build_logs".

Option Name	Description

-errors	Display known error messages in all log files
-errors-make	Display known error messages in make log file
-status	Display build process currently executing along with directory listing of log files sorted by time last modified
-warnings	Display known warning message in all log files
-warnings-make	Display known warning messages in make log file

3.2.4 Important Configuration Options for Building DatacondAPI Library

There are several options that should be used when building LDAS DatacondAPI Library.

The first of these options is -install. With this option the software will be installed according to the --prefix and -no-stow options if there were no errors during the compilation. If this option is not used, the the installer must manually go into the build directory and execute the command make install. NOTE: If the manual approach is used, be sure not to override the value of prefix (ex: make prefix=/tmp install) as the installed system will not operate properly and may not start at all.

The another option is -no-stow. LDAS recommends using stow for all software installed (Read the description of the package for further information). If stow cannot be used, then this option will recalculate the the destination directory purely on the --prefix option specified.

4 Reporting problems

DatacondAPI Library uses GNATS for reporting and tracking problem reports. Each major piece of code and each major task has a category. For example, errors that are found in this documentation should be submitted under the category "doc" since it represents a documentation error.

4.1 Accessing GNATS via the Web

https://ldas-sw.ligo.caltech.edu/cgi-bin/gnatsweb.cgi?database=ldas

The above link will bring you to a page explaining levels of severity, levels of priorities, and explain the types of classes. The link at the bottom of the page will bring you into the GNATS system where you will be able to submit and query problem reports.

All users can submit problem and query reports. Only developers can modify problem reports once they have been submitted.

4.1.1 Submitting a new problem report.

Once in the GNATS system, choose "create". This brings up a form which must be filled out.

Does

Specify an appropriate Category
Specify an appropriate Severity
Specify an appropriate Priority
Specify an appropriate Class
Leave submitter-id as "ldas"
Specify the release of the DatacondAPI Library software. Use the value of the <Date> of the -D or the <Tag> of the -r option used when exporting the files. If the value "now" or "HEAD" were used, please specify the date you performed the export.
Give a complete description of the problem. More details that are give, the better.
Give a description of how to repeat the observed problem.
If there is a known fix, please describe it.

Don'ts

Use the CC field. This has caused problems in the past.

Once the form has been completely filled out, go to the top or the bottom of the page and select the "submit" button. You will receive e-mail notifying you of your submitted problem report and the id with which it is associate. You will also receive e-mail whenever there is a change to the problem report.

4.1.2 Checking the status of a problem report

There are two ways of checking the status of a problem report. The first is using the "View problem report" option from the GNATs main page. If you have the problem report id, just type in the number and select the "view" button. A page with the full details of the problem report will appear.

The second method allows you to query the GNATS system for problem reports of interest and has two flavors. The simplest is the "Query Problem Reports." Use this method by selecting the "query" button. A web form page will appear. Refine the search by using the drop down selectors and/or using the text widgets. The query is executed after selecting the "submit" button. If you are interested in problem reports that are potentially closed, be sure the "Ignore Closed" button below the "State" field is not selected.

For more advanced queries, select the "advanced query" button. This form allows you to search by time and date and by regular expressions. Again if you are interested in problem reports that are potentially closed, be sure the "Ignore Closed" button in the "State" field is not selected.

Part 2
Programming Guide

5 Calling DatacondAPI

This is Beta code! Please note that this is a work in progress interface and as such the interface may be altered. This first draft is being presented to the larger community in an attempt to address needs and concearns that have not been exposed by the Beta testing. Please submit any problems or suggestions to the LDAS Problem Tracking System located at http://www.ldas-sw.ligo.caltech.edu/ProblemTracking.html. Use the catagory datacond_api - The Data Conditioning API. Be sure to use the ldas problem tracking database.

The standalone datacondAPI has a single call. This call is DatacondCaller().

5.1 Synopsis

g++ [ flag... ] file... -ldatacondCaller [ library... ]

#include "datacondAPI/DatacondCaller.h"

int DatacondCaller( const char* Algorithm, const char* Aliases, datacond_symbol_type* Symbols, int NumberOfSymbols, char** ErrorMessage );

5.2 Description

The DatacondCaller() allows for a C/C++ program to use all of the algorithms defined in the Dataconditioning API without having to submit an LDAS job. The algorithms as described by Algorithm are executed in the process space of the calling C/C++ program. Aliases allows for mapping of complex channel names into simple names. This list should be of the form:

<simple name>=<channel name>;[<simple name>=<channel name>; ...]

where <simple name> is the name of the object used in Algorithm and <channel name> represents the name of the object ingested into the symbol table. Symbols is an array describing how to translate data for input or output. The size of this array needs to be passed as NumberOfSymbols. If NumberOfSymbols is smaller than the number of elements in Symbols, then the trailing records will not be processed resulting in either symbols needed by the algoritm section not being defined or data products generated by the algoritm section not being translated for use by the caller. When an error is generated, it will be placed into ErrorMessage. This pointer is allocated by the function so as not to have an arbitrary maximum size for the error message. It is the responsibility of the caller to free the memory (via free()) if an error is returned.

5.3 Return Value

Upon successful completion, the value DATACOND_OK is returned. All other return values indicate an error.

5.4 Errors

DATACOND_OK - No error happened
DATACOND_PARSE_ALIASES_FAILURE - When trying to parse Aliases, a syntax error was encountered.
DATACOND_PARSE_FAILURE - When trying to parse Algoritm, a syntax error was encountered.
DATACOND_EXEC_FAILURE - When executing the Algoritm, a runtime error was encountered.
DATACOND_INGESTION_FAILURE - An error was encountered when trying to ingest one of Symbols.

6 Writing Translation Functions

The first thing to note about Translation Functions is they must be written in C++ because they interface with the classes defined in the Datacondditioning API.

Translation functions describe how to exchange a user's custom data with the Dataconditioning API's UDT (Universal Data Type). A translation function can be for input, output or input/output.

All translation functions have the form int TranslationFunction( translation_direction Direction, void** UserData, void** DatacondData, void* AuxData );

All pointers to data (UserData, DatacondData, and AuxData) are forms of void* to relax strict type checking since the data types are arbitrary. Caution must be take when casting these references to objects. If inappropriate casts are done, the application may terminate with a segmintation violation or a bus error.

Direction indicates the direction of the translation. DATACOND_SYMBOL_INPUT is used to indicate translation from user's data format into the UDT format used by the Dataconditioning API. DATACOND_SYMBOL_OUTPUT is used to indicate translation from the UDT format used by the Dataconditioning API into the user's data format. It is possible for the same function to handle both of these cases by use of a conditional or switch statement. This practice is encouraged for consitency of the translation. If the user data format or the Dataconditioning API format changes, only one file needs to be changed.

UserData represents data in the user data format. For DATACOND_SYMBOL_INPUT, this must be non-NULL.

DatacondData represents data in the Dataconditioning API UDT format. For DATACOND_SYMBOL_OUTPUT, this will not be NULL.

AuxData represents any auxilary information that the caller needs to pass to the translation function. It is only used by the translation function.

Each translation function should return either TRANSLATION_OK if no errors were encountered, TRANSLATION_FAIL otherwise.

7 Writing Algorithm Section

There is no difference between writing the algoritm section for LDAS or for DatacondAPI Library. A description of what can be in the action section can be found at:
http://www.ldas-sw.ligo.caltech.edu/doc/userAPI/html/actions.html

8 Caveats

Must link with C++ compiler. It currently has only been tested with GNU g++.
Beta code so the interface may change.

Part 3
Third Party Package Installation Guide

9 Software Packages Used by DatacondAPI Library

9.1 Building of 3rd party packages

The pkgbuilder building tool is now employed to greatly simplify the installation of third party packages. The environment variable LDASTOPSRCDIR must be set to use the rules given below. The value of this environment variable should be set to the fully qualified path of the top level directory of the LDAS source tree.

Before any of the packages can be installed, a directory of "/ldcg" must be created with read/write permissions for the user installing the software and read permissions for all other users. Although this directory is anchored at the root directory, it can reside anywhere there is sufficient space and have a symbolic link from there to "/ldcg." This needs to be added to the PATH and LD_LIBRARY_PATH environment variables. To set this variable for bourne shell and its derivitives use "PATH=/ldcg/bin:${PATH}; export PATH". For C shell and its derivities use "setenv PATH /ldcg/bin:${PATH}". Also for C shell and derivitives the rehash command will be need to be executed after each package installation. To set this variable for bourne shell and its derivitives use "LD_LIBRARY_PATH=/ldcg/lib:${LD_LIBRARY_PATH}; export LD_LIBRARY_PATH". For C shell and its derivities use "setenv LD_LIBRARY_PATH /ldcg/lib:${LD_LIBRARY_PATH}".

It is required to use stow. Please review the section dedicated to stow and install this package first.

The table below describes which packages are are needed for various configurations of LDAS. The columns "Solaris 10" and "CentOS 5.2/Intel" describe the operating system on which the LDAS software is to be compiled and run. The sub-column CVS stands for building of the LDAS system from the source in the CVS archive. The sub-column Tar-Ball stands for building of the LDAS system from a tar-ball distribution (ldas-x.x.x.tar.gz). The three field values are "Required", "Optional", and "RPM". A field value of "Required" means the package must be built. A field value of "Optional" means the package does not need to be built. A field value of "RPM" means that the package is required and can either be built from its sources or the RPM from RedHat may be used.

Software Packages used by DatacondAPI Library
Package	OS	Distribution	Requiremnts
stow 1.3.3	Solaris 10	CVS	Required
		Tarball	Required
	CentOS 5.2	CVS	Required
		Tarball	Required

pkgbuilder 0.11.0	Solaris 10	CVS	Required
		Tarball	Required
	CentOS 5.2	CVS	Required
		Tarball	Required

zlib 1.1.4	Solaris 10	CVS	Required
		Tarball	Required
	CentOS 5.2	CVS	RPM
		Tarball	RPM

BZip2 1.0.2	Solaris 10	CVS	OS Supplied
		Tarball	OS Supplied
	CentOS 5.2	CVS	RPM (bzip2-devel-1.0.2-16 bzip2-libs-1.0.2-16 bzip2-1.0.2-16)
		Tarball	RPM (bzip2-devel-1.0.2-16 bzip2-libs-1.0.2-16 bzip2-1.0.2-16)

tar 1.15.1	Solaris 10	CVS	Required
		Tarball	Required
	CentOS 5.2	CVS	Required
		Tarball	Required

patch	Solaris 10	CVS	Required
		Tarball	Required
	CentOS 5.2	CVS	Required
		Tarball	Required

binutils	Solaris 10	CVS	Required
		Tarball	Required
	CentOS 5.2	CVS	Required
		Tarball	Required

gcc	Solaris 10	CVS	Required
		Tarball	Required
	CentOS 5.2	CVS	Required
		Tarball	Required

coreutils	Solaris 10	CVS	Required
		Tarball	Required
	CentOS 5.2	CVS	Required
		Tarball	Required

make 3.79.1	Solaris 10	CVS	Required
		Tarball	Required
	CentOS 5.2	CVS	Required
		Tarball	Required

m4	Solaris 10	CVS	Required
		Tarball	Required
	CentOS 5.2	CVS	Required
		Tarball	Required

autoconf	Solaris 10	CVS	Required
		Tarball	Required
	CentOS 5.2	CVS	Required
		Tarball	Required

automake	Solaris 10	CVS	Required
		Tarball	Required
	CentOS 5.2	CVS	Required
		Tarball	Required

libtool	Solaris 10	CVS	Required
		Tarball	Required
	CentOS 5.2	CVS	Required
		Tarball	Required

bison	Solaris 10	CVS	Required
		Tarball	Required
	CentOS 5.2	CVS	Required
		Tarball	Required

flex	Solaris 10	CVS	Required
		Tarball	Required
	CentOS 5.2	CVS	Required
		Tarball	Required

ospace	Solaris 10	CVS	Required
		Tarball	Required
	CentOS 5.2	CVS	Required
		Tarball	Required

9.2 stow 1.3.3

9.2.1 Description

GNU Stow is a program for managing the installation of software packages, keeping them separate (/usr/local/stow/emacs vs. /usr/local/stow/perl, for example) while making them appear to be installed in the same place (/usr/local). Stow is a Perl script which should run correctly under Perl 5.005 and above. You must install Perl before running Stow. Stow was inspired by Carnegie Mellon's Depot program, but is substantially simpler.

9.2.2 Links

Link Description

Link

Home Page

http://www.gnu.org/software/stow/

Download

ftp://ftp.gnu.org/gnu//stow/stow-1.3.3.tar.gz

Mirror

LDAS Patch

9.2.3 Build Requirements

Software Package used by DatacondAPI Library
Package	OS	Distribution	Requiremnts
stow 1.3.3	Solaris 10	CVS	Required
		Tarball	Required
	CentOS 5.2	CVS	Required
		Tarball	Required

9.2.4 Build Instructions

9.3 pkgbuilder 0.11.0

9.3.1 Description

Pkgbuilder is a utility designed to automate the process of building third party packages.

9.3.2 Links

Link Description

Link

Home Page

http://ldas-sw.ligo.caltech.edu/packages/pkgbuilder-0.11.0.tar.gz

Download

http://ldas-sw.ligo.caltech.edu/packages/pkgbuilder-0.11.0.tar.gz

Mirror

LDAS Patch

9.3.3 Build Requirements

Software Package used by DatacondAPI Library
Package	OS	Distribution	Requiremnts
pkgbuilder 0.11.0	Solaris 10	CVS	Required
		Tarball	Required
	CentOS 5.2	CVS	Required
		Tarball	Required

9.3.4 Build Instructions

9.4 zlib 1.1.4

9.4.1 Description

Zlib is designed to be a free, general-purpose, legally unencumbered, lossless data-compression library for use on virtually any computer hardware and operating system. The zlib data format is itself portable across platforms. Unlike the LZW compression method used in Unix compress(1), the compression method currently used in zlib essentially never expands the data. (LZW can double or triple the file size in extreme cases.) zlib's memory footprint is also independent of the input data and can be reduced, if necessary, at some cost in compression.

9.4.2 Links

Link Description	Link

Home Page	`http://www.gzip.org/zlib/`

9.4.3 Build Requirements

Software Package used by DatacondAPI Library
Package	OS	Distribution	Requiremnts
zlib 1.1.4	Solaris 10	CVS	OS Supplied
		Tarball	OS Supplied
	CentOS 5.2	CVS	RPM (zlib-devel-1.2.2.2-5.fc4 zlib-1.2.2.2-5.fc4)
		Tarball	RPM (zlib-devel-1.2.2.2-5.fc4 zlib-1.2.2.2-5.fc4)

9.4.4 Build Instructions

This package should already be installed on your system.

For Red Hat Linux verify with:

You should get a list of packages as referenced in the RPM list above.

For Solaris, check for the existance of the following files:

/usr/include/zlib.h
/usr/lib/libz.so

If you have an incomplete installation, please contact your system administrator as this package require system privileges to install.

9.5 BZip2 1.0.2

9.5.1 Description

bzip2 is a freely available, patent free, high-quality data compressor. It typically compresses files to within 10 percent to 15 percent of the best available techniques (the PPM family of statistical compressors), whilst being around twice as fast at compression and six times faster at decompression.

9.5.2 Links

Link Description	Link

Home Page	`http://sources.redhat.com/bzip2/`

9.5.3 Build Requirements

Software Package used by DatacondAPI Library
Package	OS	Distribution	Requiremnts
BZip2 1.0.2	Solaris 10	CVS	OS Supplied
		Tarball	OS Supplied
	CentOS 5.2	CVS	RPM (bzip2-devel-1.0.2-16 bzip2-libs-1.0.2-16 bzip2-1.0.2-16)
		Tarball	RPM (bzip2-devel-1.0.2-16 bzip2-libs-1.0.2-16 bzip2-1.0.2-16)

9.5.4 Build Instructions

This package should already be installed on your system.

For Red Hat Linux verify with:

You should get a list of packages as referenced in the RPM list.

For Solaris, check for the existance of the following files:

/usr/include/bzlib.h
/usr/lib/libbz2.so

If you have an incomplete installation, please contact your system administrator as this package require system privileges to install.

9.6 tar 1.15.1

9.6.1 Description

GNU `tar' saves many files together into a single tape or disk archive, and can restore individual files from the archive. It includes multivolume support, the ability to archive sparse files, automatic archive compression/decompression, remote archives and special features that allow `tar' to be used for incremental and full backups. It also includes `rmt', the remote tape server (the `mt' tape drive control program is in GNU `cpio').

9.6.2 Links

Link Description

Link

Home Page

http://www.gnu.org/software/tar/tar.html

Download

ftp://ftp.gnu.org/gnu//tar/tar-1.15.1.tar.gz

Mirror

LDAS Patch

9.6.3 Build Requirements

Software Package used by DatacondAPI Library
Package	OS	Distribution	Requiremnts
tar 1.15.1	Solaris 10	CVS	Required
		Tarball	Required
	CentOS 5.2	CVS	Required
		Tarball	Required

9.6.4 Build Instructions

9.7 patch

9.7.1 Description

patch takes a patch file containing a difference listing produced by the diff program and applies those differences to one or more original files, producing patched versions. Normally the patched versions are put in place of the originals. Backups can be made.

9.7.2 Links

Link Description

Link

Home Page

http://www.gnu.org/software/patch/patch.html

Download

ftp://ftp.gnu.org/gnu//patch/patch-.tar.gz

Mirror

LDAS Patch

9.7.3 Build Requirements

Software Package used by DatacondAPI Library
Package	OS	Distribution	Requiremnts
patch	Solaris 10	CVS	Required
		Tarball	Required
	CentOS 5.2	CVS	Required
		Tarball	Required

9.7.4 Build Instructions

9.8 binutils

9.8.1 Description

GNU binutils work mostly behind the scenes of Linux development, largely because GNU make and the GCC frontend does so many things automatically. Utilities include: ld as nm objdump objcopy nm ar ranlib strip c++filt size addr2line and dlltool.

9.8.2 Links

Link Description

Link

Home Page

http://sources.redhat.com/binutils/

Download

ftp://ftp.gnu.org/gnu//binutils/binutils-.tar.gz

Mirror

LDAS Patch

9.8.3 Build Requirements

Software Package used by DatacondAPI Library
Package	OS	Distribution	Requiremnts
binutils	Solaris 10	CVS	Required
		Tarball	Required
	CentOS 5.2	CVS	Required
		Tarball	Required

9.8.4 Build Instructions

9.9 gcc

9.9.1 Description

The GNU Compiler Collection contains frontends for C, C++, Objective-C, Fortran, Java, and Ada as well as libraries for these languages. It is a full-featured ANSI C compiler with support for K&R C as well. GCC provides many levels of source code error checking traditionally provided by other tools (such as lint), produces debugging information, and can perform many different optimizations to the resulting object code.

9.9.2 Links

Link Description

Link

Home Page

http://gcc.gnu.org

Download

ftp://gcc.gnu.org/pub/gcc/releases/gcc-/gcc-.tar.bz2

Mirror

ftp://ftp.gnu.org/gnu//gcc/gcc-/gcc-.tar.bz2

LDAS Patch

9.9.3 Build Requirements

Software Package used by DatacondAPI Library
Package	OS	Distribution	Requiremnts
gcc	Solaris 10	CVS	Required
		Tarball	Required
	CentOS 5.2	CVS	Required
		Tarball	Required

9.9.4 Build Instructions

9.10 GNU Coreutils

9.10.1 Description

GNU Coreutils are a set of basic file, shell, and text manipulation utilities for the GNU operating system that are expected to exist on every operating system. Previously, they were offered as three individual packages: fileutils, sh-utils, and textutils.

9.10.2 Links

Link Description

Link

Home Page

http://www.gnu.org/software/coreutils/

Download

http://mirrors.usc.edu/pub/gnu/coreutils/coreutils-.tar.gz

Mirror

ftp://ftp.gnu.org/gnu/coreutils/coreutils-.tar.gz

LDAS Patch

9.10.3 Build Requirements

Software Package used by DatacondAPI Library
Package	OS	Distribution	Requiremnts
GNU Coreutils	Solaris 10	CVS	Required
		Tarball	Required
	CentOS 5.2	CVS	Required
		Tarball	Required

9.10.4 Build Instructions

9.11 make 3.79.1

9.11.1 Description

GNU Make examines the timestamps on a set of interdependent files, and, if necessary, issues commands to bring them up-to-date. The user creates a makefile describing the files, their relationships, and the commands to run. Most often make is used to rebuild libraries and programs when their sources are changed, but it can be used for any situation where one set of files needs to be generated from another set.

9.11.2 Links

Link Description

Link

Home Page

http://www.gnu.org/software/make/make.html

Download

ftp://ftp.gnu.org/gnu//make/make-3.79.1.tar.gz

Mirror

LDAS Patch

9.11.3 Build Requirements

Software Package used by DatacondAPI Library
Package	OS	Distribution	Requiremnts
make 3.79.1	Solaris 10	CVS	Required
		Tarball	Required
	CentOS 5.2	CVS	Required
		Tarball	Required

9.11.4 Build Instructions

9.12 m4

9.12.1 Description

GNU m4 is an implementation of the traditional Unix macro processor. It is mostly SVR4 compatible, although it has some extensions (for example, handling more than 9 positional parameters to macros). GNU m4 also has built-in functions for including files, running shell commands, doing arithmetic, etc.

9.12.2 Links

Link Description

Link

Home Page

http://www.seindal.dk/rene/gnu/

Download

ftp://ftp.gnu.org/gnu//m4/m4-.tar.bz2

Mirror

LDAS Patch

9.12.3 Build Requirements

Software Package used by DatacondAPI Library
Package	OS	Distribution	Requiremnts
m4	Solaris 10	CVS	Required
		Tarball	Required
	CentOS 5.2	CVS	Required
		Tarball	Required

9.12.4 Build Instructions

9.13 autoconf

9.13.1 Description

Autoconf is an extensible package of m4 macros that produce shell scripts to automatically configure software source code packages. These scripts can adapt the package to many kinds of UNIX-like systems without manual user intervention.

9.13.2 Links

Link Description

Link

Home Page

http://www.gnu.org/software/autoconf/

Download

ftp://ftp.gnu.org/gnu//autoconf/autoconf-.tar.bz2

Mirror

LDAS Patch

9.13.3 Build Requirements

Software Package used by DatacondAPI Library
Package	OS	Distribution	Requiremnts
autoconf	Solaris 10	CVS	Required
		Tarball	Required
	CentOS 5.2	CVS	Required
		Tarball	Required

9.13.4 Build Instructions

9.14 automake

9.14.1 Description

Automake is a tool for automatically generating Makefiles compliant with the GNU Coding Standards. It was inspired by the 4.4BSD make and include files, but aims to be portable and to conform to the GNU standards for Makefile variables and targets. Automake is a Perl script. The input files are called Makefile.am. The output files are called Makefile.in; They are intended for use with Autoconf. Automake requires certain things to be done in your configure.in. This package also includes the äclocal" program. aclocal is a program to generate an 'aclocal.m4' based on the contents of 'configure.in'. It is useful as an extensible, maintainable mechanism for augmenting autoconf.

9.14.2 Links

Link Description

Link

Home Page

http://www.gnu.org/software/automake/automake.html

Download

ftp://ftp.gnu.org/gnu//automake/automake-.tar.bz2

Mirror

LDAS Patch

9.14.3 Build Requirements

Software Package used by DatacondAPI Library
Package	OS	Distribution	Requiremnts
automake	Solaris 10	CVS	Required
		Tarball	Required
	CentOS 5.2	CVS	Required
		Tarball	Required

9.14.4 Build Instructions

9.15 libtool

9.15.1 Description

GNU libtool is a generic library support script. Libtool hides the complexity of using shared and static libraries behind a consistent, portable interface. Libtool supports building static libraries on all platforms.

9.15.2 Links

Link Description

Link

Home Page

http://www.gnu.org/software/libtool/

Download

ftp://ftp.gnu.org/gnu//libtool/libtool-.tar.gz

Mirror

LDAS Patch

9.15.3 Build Requirements

Software Package used by DatacondAPI Library
Package	OS	Distribution	Requiremnts
libtool	Solaris 10	CVS	Required
		Tarball	Required
	CentOS 5.2	CVS	Required
		Tarball	Required

9.15.4 Build Instructions

9.16 bison

9.16.1 Description

Bison is a parser generator in the style of yacc(1). It should be upwardly compatible with input files designed for yacc.

9.16.2 Links

Link Description

Link

Home Page

http://www.gnu.org/software/bison/bison.html

Download

ftp://ftp.gnu.org/gnu//bison/bison-.tar.gz

Mirror

LDAS Patch

9.16.3 Build Requirements

Software Package used by DatacondAPI Library
Package	OS	Distribution	Requiremnts
bison	Solaris 10	CVS	Required
		Tarball	Required
	CentOS 5.2	CVS	Required
		Tarball	Required

9.16.4 Build Instructions

9.17 flex

9.17.1 Description

Flex is a fast lexical analyser generator. It is a tool for generating programs that perform pattern-matching on text. There are many applications for Flex, including writing compilers in conjunction with GNU Bison. Flex is a free implementation of the well known Lex program. It features a Lex compatibility mode, and also provides several new features such as exclusive start conditions.

9.17.2 Links

Link Description

Link

Home Page

http://www.gnu.org/software/flex/flex.html

Download

http://easynews.dl.sourceforge.net/sourceforge/flex/flex-.tar.bz2

Mirror

LDAS Patch

9.17.3 Build Requirements

Software Package used by DatacondAPI Library
Package	OS	Distribution	Requiremnts
flex	Solaris 10	CVS	Required
		Tarball	Required
	CentOS 5.2	CVS	Required
		Tarball	Required

9.17.4 Build Instructions

9.18 ospace

9.18.1 Description

Object Space

9.18.2 Links

Link Description

Link

Home Page

Download

http://ldas-sw.ligo.caltech.edu/packages/ObjectSpace-sunos.tar.gz

Mirror

LDAS Patch

9.18.3 Build Requirements

Software Package used by DatacondAPI Library
Package	OS	Distribution	Requiremnts
ospace	Solaris 10	CVS	Required
		Tarball	Required
	CentOS 5.2	CVS	Required
		Tarball	Required

9.18.4 Build Instructions

File translated from T_EX by T_TH, version 3.66.
On 4 Nov 2009, 14:00.

DatacondAPI Library INSTALLATION NOTES

Contents

Part 1 Installation

1 Import Changes

2 Retrieving the Source Code

2.1 The Entire System

2.1.1 Tar-ball distribution

2.1.2 CVS distribution

2.1.3 Retrieving the Relevant Pieces

3 Building the Source

3.1 Default configuration

3.2 Custom configuration

3.2.1 datacond-1.16.3/build-ldas Options

3.2.2 Configure Options

3.2.3 datacond-1.16.3/build-ldas Options - View status of the LDAS build

3.2.4 Important Configuration Options for Building DatacondAPI Library

4 Reporting problems

4.1 Accessing GNATS via the Web

4.1.1 Submitting a new problem report.

4.1.2 Checking the status of a problem report

Part 2 Programming Guide

5 Calling DatacondAPI

5.1 Synopsis

5.2 Description

5.3 Return Value

5.4 Errors

6 Writing Translation Functions

7 Writing Algorithm Section

8 Caveats

Part 3 Third Party Package Installation Guide

9 Software Packages Used by DatacondAPI Library

9.1 Building of 3rd party packages

9.2 stow 1.3.3

9.2.1 Description

9.2.2 Links

9.2.3 Build Requirements

9.2.4 Build Instructions

9.3 pkgbuilder 0.11.0

9.3.1 Description

9.3.2 Links

9.3.3 Build Requirements

9.3.4 Build Instructions

9.4 zlib 1.1.4

9.4.1 Description

9.4.2 Links

9.4.3 Build Requirements

9.4.4 Build Instructions

9.5 BZip2 1.0.2

9.5.1 Description

9.5.2 Links

9.5.3 Build Requirements

9.5.4 Build Instructions

9.6 tar 1.15.1

9.6.1 Description

9.6.2 Links

9.6.3 Build Requirements

9.6.4 Build Instructions

9.7 patch

9.7.1 Description

9.7.2 Links

9.7.3 Build Requirements

9.7.4 Build Instructions

9.8 binutils

9.8.1 Description

9.8.2 Links

9.8.3 Build Requirements

9.8.4 Build Instructions

9.9 gcc

9.9.1 Description

9.9.2 Links

9.9.3 Build Requirements

9.9.4 Build Instructions

9.10 GNU Coreutils

9.10.1 Description

9.10.2 Links

9.10.3 Build Requirements

9.10.4 Build Instructions

9.11 make 3.79.1

9.11.1 Description

9.11.2 Links

Part 1
Installation

Part 2
Programming Guide

Part 3
Third Party Package Installation Guide