mcm@pear.ucsb.edu (Marcelo C. Mourier) (03/06/90)
Hi there! As a first-time upgrader I'm running into the same kind of troubles most of you ran into before; specifically, building the new library... As I'd like to catch up with v1.5.3 as soon as po- ssible, I'd greatly appreciate if one of you guys that has done this before could give me a hand with this stuff. Following is a des- cription of my system and of my current upgrading status. I have PH's v1.3 running in my AT. I have the /usr and root file systems in my HD's hd2 and hd3 partitions, respectively. Every- thing is running fine. I also have the crc and patch programs, and the complete 1.3 -> 1.5.0 upgrade file set. I have reorganized the /usr directory tree according to the official 1.5.0 one, which is slightly different from v1.3's one. Here's what I've done so far: - First I upgraded the /usr/include, /usr/include/minix, and /usr/in- clude/sys directories with the contents of the corresponding dis- tribution files (include_00, etc.). - Then I upgraded the ansi, other, and posix library directories with the corresponding distribution files. - Then I recompiled all the library functions using the run scripts. Besides a bunch of warning messages due to incompatible pointers everything worked fine. - Then I moved all the *.s files from these directories to a tempora- ry working directory /usr/tmp/lib. At this point I'm almost ready to build the new library. How- ever there are still some missing things. Concretely: - What ever happened in 1.5.0 with the IBM specific files that were in /usr/src/minix/lib/IBM_PC in v1.3? I assume these files should go now in /usr/src/lib/ibm, but in the crc list of all the 1.5.0 files (see post "1.5.3 #1 - Intro") this directory, nor any of its files, shows up (?!). However, in the same posting, the crc list for the 1.5.3 files shows the /usr/src/lib/ibm directory and its files, which are indeed basically the same as in v1.3's lib/IBM_PC. You can guess what my first question is: What IBM specific files should we use for building the 1.5.0 library; the same ones used in v1.3 ..? - The second question is regarding the various compiler specific library functions (adi.s, and.s, cii.s, and the like). Again, should we use the same ones used in v1.3's libc.a? - Finally, how should I get the proper order for the library functions? I've seen all sorts of problems posted to the net about this subject. Yesterday I tried: lorder *.s|tsort on the files in my /usr/tmp/lib directory and lorder complained that it didn't have enough memory. However, running ls|wc on the same directory gave something like 1400 characters, which is less than the 2k initial stack allocated by exec when spawning the lorder process. I don't understand what's going on, so I'd appreciate if somebody could mail me a file containing the pro- per library order, or give me a clue as how to do it myself with the 1.3 lorder and tsort programs. I assume that with the new library up and running I should be able to proceed the upgrade smoothly. Anyway, any additional suggestion or tip will be more than welcome. I'm really looking forward to get 1.5.3 up soon, because AST is already threating with 1.5.4...! Thanks in advance to whoever comes to my rescue. Marcelo - mcm@cs.ucsb.edu