summaryrefslogtreecommitdiff
path: root/performance-tests/TTCP/C/README
diff options
context:
space:
mode:
authornobody <nobody@ae88bc3d-4319-0410-8dbf-d08b4c9d3795>1997-01-01 08:00:34 +0000
committernobody <nobody@ae88bc3d-4319-0410-8dbf-d08b4c9d3795>1997-01-01 08:00:34 +0000
commitd9661aebab28abc0ec4fb1e716170d347d56c168 (patch)
treeecb671ab4b8e299bf5cbb8b2dfeed8a49b65fc06 /performance-tests/TTCP/C/README
parentea0d28240863caf437a18071bfd03e7b146c5ade (diff)
downloadATCD-unlabeled-4.3.2.tar.gz
This commit was manufactured by cvs2svn to create branchunlabeled-4.3.2
'unlabeled-4.3.2'.
Diffstat (limited to 'performance-tests/TTCP/C/README')
-rw-r--r--performance-tests/TTCP/C/README38
1 files changed, 0 insertions, 38 deletions
diff --git a/performance-tests/TTCP/C/README b/performance-tests/TTCP/C/README
deleted file mode 100644
index 88788c386eb..00000000000
--- a/performance-tests/TTCP/C/README
+++ /dev/null
@@ -1,38 +0,0 @@
-
- TTCP for c_version, ACE-wrappers, ORBeline and Orbix
- ----------------------------------------------------
-
-This is the super-readme file for the "ttcp" code. This directory contains the C, ACE-wrappers,
-ORBeline and Orbix versions of ttcp code. To compile the code, you have to do the following:
-
-1. You should have ACE, ORBeline and Orbix installed in your system and configured correctly.
- (see the reference manual for installation and configuration procedure)
-
-2. Copy this directory (ttcp) in the same directory structure to your disk space.
-
-3. setup the following environment parameters (before compilation stage):
- WRAPPER_ROOT, ORBELINE_ROOT, ORBIX_ROOT, LD_LIBRARY_PATH.
-
-For example:
-WRAPPER_ROOT=/project/adaptive/ACE_wrappers
-ORBELINE_ROOT=/project/adaptive/ORBelineV1.2
-ORBIX_ROOT=/project/adaptive/Orbix
-LD_LIBRARY_PATH=/project/adaptive/ORBelineV1.2/lib
- :/project/adaptive/ACE_wrappers/build/SunOS5.4/src
- :/project/adaptive/Orbix/lib
-
-4. Do make (using GNU make) in this directory level. This will create the executable ttcp
- target code for each ttcp version.
-
-5. Read the README or How_to_run_tests file existing in each directory to know how to use the
- executable.
-
-6. Have fun.
-
-
-
-Ehab S. Al-Shaer
-6/30/1995
-
-
-