Commit | Line | Data |
c2960299 |
1 | # Info from Johann Klasek <jk@auto.tuwien.ac.at> |
2 | # Merged by Andy Dougherty <doughera@lafcol.lafayette.edu> |
3 | # Last revised Fri Jun 2 11:21:27 EDT 1995 |
f1ca563b |
4 | |
c2960299 |
5 | # uname -a looks like |
6 | # DomainOS newton 10.4.1 bsd4.3 425t |
7 | |
8 | # We want to use both BSD includes and some of the features from the |
9 | # /sys5 includes. |
10 | ccflags="$ccflags -A cpu,mathchip -I/usr/include -I/sys5/usr/include" |
11 | |
12 | # These adjustments are necessary (why?) to compile malloc.c. |
13 | freetype='void' |
14 | i_malloc='undef' |
15 | malloctype='void *' |
16 | |
17 | # This info is left over from perl4. |
f1ca563b |
18 | cat <<'EOF' |
19 | Some tests may fail unless you use 'chacl -B'. Also, op/stat |
20 | test 2 may fail occasionally because Apollo doesn't guarantee |
21 | that mtime will be equal to ctime on a newly created unmodified |
22 | file. Finally, the sleep test will sometimes fail. See the |
23 | sleep(3) man page to learn why. |
24 | |
c2960299 |
25 | See hints/apollo.sh for hints on running h2ph. |
26 | |
f1ca563b |
27 | And a note on ccflags: |
28 | |
29 | Lastly, while -A cpu,mathchip generates optimal code for your DN3500 |
30 | running sr10.3, be aware that you should be using -A cpu,mathlib_sr10 |
31 | if your perl must also run on any machines running sr10.0, sr10.1, or |
32 | sr10.2. The -A cpu,mathchip option generates code that doesn't work on |
33 | pre-sr10.3 nodes. See the cc(1) man page for more details. |
34 | -- Steve Vinoski |
35 | |
36 | EOF |
c2960299 |
37 | |
38 | # Running h2ph, on the other hand, presents a challenge. |
39 | |
40 | #The perl header files have to be generated with following commands |
41 | |
42 | #sed 's|/usr/include|/sys5/usr/include|g' h2ph >h2ph.new && chmod +x h2ph.new |
43 | #(set cdir=`pwd`; cd /sys5/usr/include; $cdir/h2ph.new sys/* ) |
44 | #(set cdir=`pwd`; cd /usr/include; $cdir/h2ph * sys/* machine/*) |
45 | |
46 | #The SYS5 headers (only sys) are overlayed by the BSD headers. It seems |
47 | #all ok, but once I am going into details, a lot of limitations from |
48 | #'h2ph' are coming up. Lines like "#define NODEV (dev_t)(-1)" result in |
49 | #syntax errors as converted by h2ph. |
50 | |
51 | # Generally, h2ph might need a lot of help. |