From: hlu@phys1.physics.wsu.edu (Hongjiu Lu) Subject: Re: new ps for 0.97 on banjo Date: 2 Aug 1992 22:21:59 GMT
I am trying to fix that in gcc 2.2.2d. I am really too busy now. First, I have
to finish my Master project. Secondly, I am also looking for a job. The job
market is not very bright right now. I have to spend lots of time on it.
Gcc 2.2.2d was almost ready before 0.97. After I got 0.97, I found out the header files need some works.
-- H.J. Gcc/libc maintainer for Linux.In article <Aug.1.22.10.04.1992.22121@dumas.rutgers.edu>, hedrick@dumas.rutgers.edu (Charles Hedrick) writes: |> I've uploaded ps-0.97.tar.Z to banjo.concert.net, /pub/Linux/Incoming. |> I intend this to be temporary, until somebody figures out what is |> going on with include files. 0.97 has moved a bunch of include files |> that used to be in /usr/src/linux/include/sys to |> /usr/src/linux/include/linux. This causes no end of trouble to |> programs like ps. We now end up with versions of types.h and several |> other header files from /usr/include/linux and /usr/include/sys. I've |> added various #define's to keep duplicate copies from being loaded, |> but this is clearly not the right solution. I have no idea why Linus |> moved the header files for 0.97. The old way was sensible. By |> tradition, /usr/include/sys is supposed to be the header files from |> the kernel source area. Having duplicate copies in |> /usr/include/linux, which get pulled in whenever you load other files |> from /usr/include/linux, is an incredible pain. Note that this tar.Z |> file has both source and binaries (the binaries use the 2.2.2 shared |> library). |> |> If the include files are ever fixed, just remove all the #defines from |> the middle of the #includes at the beginning of ps.c, top.c, free.c |> and w.c.