| Date Of Receipt: 28-SEP-1995 11:34:02.07
From: SMURF::QUARRY::"[email protected]" "28-Sep-1995 1132"
To: [email protected]
CC: [email protected], wrksys::tosi, wrsys::coulter, [email protected]
Subj: Re: Building X11r6(decx11.nightly_pool)
If you need to submit to platinum, then you should build against platinum. The
ptx11 tree and the decx11 tree diverged some time ago. Sup ptx11.nightly
instead.
I'm not sure how you are doing the build, you didn't say, but the key pieces
to ensure that you get the correct tools, compiler, includes, libs etc. is as
follows:
Make sure that ./tools/alpha_osf1/cc/usr is fully populated. Dates on the libs
should be current. Here's what shlib looks like:
cardinal cc/usr [41] ll shlib/
total 8342
drwxr-xr-x 2 devbld staff 8192 Sep 28 02:08 ./
drwxr-xr-x 7 devbld staff 8192 Sep 28 02:08 ../
-rw-r--r-- 1 devbld staff 2833 Sep 27 21:48 .mrg..so_locations
-rw-r--r-- 1 devbld staff 57344 Sep 27 22:35 libaio.so
-rw-r--r-- 1 devbld staff 32768 Sep 27 22:35 libaio_raw.so
-rw-r--r-- 1 devbld staff 40960 Sep 27 22:18 libaud.so
-rwxr-xr-x 1 devbld staff 1540016 Sep 27 22:13 libc.so*
and so on.
Here's the main thing to do as far as building;
the build script sets the following variables
COMP_HOST_ROOT={path_to_tree}/tools/alpha_osf1/cc
COMP_TARGET_ROOT="${COMP_HOST_ROOT}
NLSPATH="${COMP_HOST_ROOT}/usr/lib/nls/msg/%L/%N:/usr/lib/nls/msg/%L/%N"
DECCXX_DIRECTORY=${COMP_HOST_ROOT}
PATH=${COMP_HOST_ROOT}/usr/bin:${COMP_HOST_ROOT}/usr/bin/X11:/etc:/sbin:/usr/sb
in:$PATH
and export all of that.
That will ensure that the correct tools are used.
then go to src and ---> make -k BOOTSTRAPCFLAGS="-D__alpha" World
I do not know if this will build on platinum system, all of our production
builds are on 3.2 variants. Setting the above should isolate you from the
system environment anyway.
If you sup the ptx11.nightly_pool collection, you get the build logs in ./Logs.
-Grant
|
| The Open3D group needs to submit code to the platinum base and to accomplish
| that we are trying to work with a sup of decx11.nightly_pool.
|
| We have been told that decx11.nightly_pool can be built on OSF3.2C and
| run on platinum.
|
| We have been successfully able to make World in the sup'ed decx11.nightly_poo
l
| tree but have had great difficulty creating a build process that allows
| the creation of static backing trees(using ode3.0), which when built generate
| working executables. For some reason the resulting shared objects:
| 1) can not be executed without problems
| 2) can not be debugged with dbx or gdb
| 3) in some cases, though shared objects exist, the loader seems
| unable to find all shared objects.
|
| We have also tried to build these sources on a platinum machine and have foun
d
| compile errors that do not exist when building on 3.2C. This suggests that
| ode is not setting the build environment correct.
|
|
| A couple of questions:
| 1) Is decx11.nightly_pool the best way to obtain a complete
| build environment for x11r6? Is there a pool which contains
| a complete build environment for x11r6 which is more stable
| than decx11.nightly_pool?
| 2) Sup'ing of decx11.nightly_pool does not include build logs.
| This information is very important in that it would minimize
| potential problems at our end and remove the need for a query
| to ZK to determine wether a problem is self-inflicted or not.
|
| How does one go about obtaining build logs?
|
| 3) I am aware that there are folks in ZK that build on 3.2C and
| are able to debug on platinum. Is this the most effective
| method for developing on x11r6 or do you recommend performing
| all development on platinum?
| 4) Are you aware of any general issues with building x11r6 which
| could help minimize problems developing in this environment?
|
| Unfortunately, there is very little time left for experimenting.
|
| Any help you can provide would be greatly appreciated.
|
|
| Martin Buckley
|
|