greg@mobius.Viewlogic.COM (Gregory Larkin) (11/13/90)
Hi All,
Well, I'm finally getting around to making the transition from
V1.3 to V1.5.10. I downloaded the upgrade kit from plains a
while ago and have started patching the sources. I have patched
the /usr/include directory and now I have started trying to patch
and rebuild libc.a. Can anyone tell me the required tar files
that contain libc.a patch files??
I think I have narrowed it down to ansi.0[01], other.0[01], posix.00,
and (maybe) string.00. Does anyone have any info on this?? Also,
libc.a contains many .s files (such as ior.s, aor.s, etc. ----
remembering from not-so-good memory) that do not appear in the
upgrade files. Are these files the same from 1.3 to 1.5.10??
As an aside, I recompiled libc.a with the missing routines last week.
(V1.3). During the process, some 330 files were created in the
source directory. After I was done, I deleted all .c and .s files.
But now, when I run fsck on the device (hard disk), it says
"Warning: huge directory /dev/hd7" or something like that. Should I
be concerned?? Is there any way to tell the FS that there are no
longer tons of files around??
Thanks for all help,
--
Greg Larkin (ASIC Engineer)
Viewlogic Systems, Inc. (The CAE Company)
293 Boston Post Road West -------------------------------------
Marlboro, MA 01752 |"We've got captains not courageous,|
508 480 0881 x321 |captains tumbling into madness..." |
E-mail: greg@Viewlogic.COM |Peter Garrett, Midnight Oil |
-------------------------------------cagney@chook.ua.oz (Andrew Cagney - aka Noid) (11/13/90)
From article <1990Nov12.111055@mobius.Viewlogic.COM>, by greg@mobius.Viewlogic.COM (Gregory Larkin): > > Hi All, > > Well, I'm finally getting around to making the transition from > V1.3 to V1.5.10. I downloaded the upgrade kit from plains a > while ago and have started patching the sources. I have patched > the /usr/include directory and now I have started trying to patch > and rebuild libc.a. Can anyone tell me the required tar files > that contain libc.a patch files?? > > I think I have narrowed it down to ansi.0[01], other.0[01], posix.00, > and (maybe) string.00. Does anyone have any info on this?? Have a look in the files TABLE & WHAT_IS_WHERE, they are very usefull for finding things. From the file TABLE: # # The libc sources (In 1.5 the src-lib was split into subdirectories) # ---------------- # # lib for the IBM # IBM:ibm_1.3/src/lib/IBM_PC:src/lib/ibm:IBM specific ansi:ibm_1.3/src/lib:src/lib/ansi: other:ibm_1.3/src/lib:src/lib/other: posix:ibm_1.3/src/lib:src/lib/posix: string::src/lib/string:IBM specific and from `KIT', the above means... directory. The file TABLE has this information. It consists of lines of the form: key:old-directory:new-directory:optional-comment Find the line in the file table starting with IBM. It will look something like IBM:src/lib/IBM_PC:src/lib/ibm: This indicates that the old version of the src/lib/ibm directory is in ????/lib/IBM_PC. Print out the file TABLE and keep it handy. You will need to refer to it each time you need to determine the location of a new/old directory. Hope this speeds things up a little... Noid