summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorBruno Haible <bruno@clisp.org>2008-08-23 09:21:24 +0000
committerBruno Haible <bruno@clisp.org>2008-08-23 09:21:24 +0000
commite615372b7fb82c817c168d602f9745afcd955fde (patch)
tree215bff840ca0a0fb68c95c504b3f7c9ba2edba08
parent2ca6f8fac0850def62b8eb705373a8bdaaa1c2c2 (diff)
downloadgperf-e615372b7fb82c817c168d602f9745afcd955fde.tar.gz
Update the section "Compiling For Multiple Architectures".
New section "Particular Systems".
-rw-r--r--INSTALL54
1 files changed, 45 insertions, 9 deletions
diff --git a/INSTALL b/INSTALL
index 33741b1..5a151a2 100644
--- a/INSTALL
+++ b/INSTALL
@@ -81,16 +81,19 @@ in the source code directory. After you have installed the package for
one architecture, use `make distclean' before reconfiguring for another
architecture.
- On MacOS X systems, you can create libraries and executables that work
-on multiple system types - known as "fat" or "universal" binaries - by
-specifying multiple '-arch' options to the compiler but only a single
-'-arch' option to the preprocessor. Like this:
+ On MacOS X 10.5 and later systems, you can create libraries and
+executables that work on multiple system types--known as "fat" or
+"universal" binaries--by specifying multiple '-arch' options to the
+compiler but only a single '-arch' option to the preprocessor. Like
+this:
+
+ ./configure CC="gcc -arch i386 -arch x86_64 -arch ppc -arch ppc64" \
+ CXX="g++ -arch i386 -arch x86_64 -arch ppc -arch ppc64" \
+ CPP="gcc -E" CXXCPP="g++ -E"
- env CC="gcc -arch i386 -arch x86_64 -arch ppc -arch ppc64" \
- CXX="g++ -arch i386 -arch x86_64 -arch ppc -arch ppc64" \
- CPP="gcc -arch ppc -E" \
- CXXCPP="g++ -arch ppc -E" \
- ./configure
+ This is not guaranteed to produce working output in all cases. You
+may have to build one architecture at a time and combine the results
+using the 'lipo' tool if you have problems.
Installation Names
==================
@@ -130,6 +133,39 @@ find the X include and library files automatically, but if it doesn't,
you can use the `configure' options `--x-includes=DIR' and
`--x-libraries=DIR' to specify their locations.
+Particular Systems
+==================
+
+ On HP-UX, the default C compiler is not ANSI C compatible. If GNU CC
+is not installed, it is recommended to use the following options in order
+to use an ANSI C compiler:
+
+ ./configure CC="cc -Ae"
+
+and if that doesn't work, install pre-built binaries of GCC for HP-UX.
+
+ On OSF/1 a.k.a. Tru64, some versions of the default C compiler cannot
+parse its `<wchar.h>' header file. The option `-nodtk' can be used as
+a workaround. If GNU CC is not installed, it is therefore recommended
+to try
+
+ ./configure CC="cc"
+
+and if that doesn't work, try
+
+ ./configure CC="cc -nodtk"
+
+ On AIX 3, the C include files by default don't define some necessary
+prototype declarations. If GNU CC is not installed, it is recommended to
+use the following options:
+
+ ./configure CC="xlc -D_ALL_SOURCE"
+
+ On BeOS, user installed software goes in /boot/home/config, not
+/usr/local. It is recommended to use the following options:
+
+ ./configure --prefix=/boot/home/config
+
Specifying the System Type
==========================