bdale@col.hp.COM (Bdale Garbee) (06/14/91)
I should point out that we're all running 1.5h.00 here. When I try to apply the diffs1 patches to get to .01, I run into what look like compiler problems. The library file mkfifo.c won't compile, which causes libc.a to not have all the stuff after mkfifo in it, etc... I haven't chased this far, just far enough to decide that mkfifo looked ok to me, and to apply the patches a second time in case something had gotten hosed. Ideas? Bdale
sverre@lars.Seri.GOV (Sverre Froyen) (06/14/91)
> >I should point out that we're all running 1.5h.00 here. When I try to apply >the diffs1 patches to get to .01, I run into what look like compiler problems. >The library file mkfifo.c won't compile, which causes libc.a to not have all >the stuff after mkfifo in it, etc... I haven't chased this far, just far enough >to decide that mkfifo looked ok to me, and to apply the patches a second time >in case something had gotten hosed. > >Ideas? Looks like I ran into this too. Here's my diff from the 1.5h.01 distribution. sverre@abbor(4)$ diff -c dist/mkfifo.c mkfifo.c *** dist/mkfifo.c Sat Mar 2 11:58:56 1991 --- mkfifo.c Sat Mar 2 12:09:13 1991 *************** *** 2,10 **** #include <sys/types.h> #include <sys/stat.h> ! PUBLIC int mkfifo(name, mode) ! _CONST char *name; ! mode_t mode; { mode = (mode & 0777) | S_IFIFO; return(callm1(FS, MKNOD, len(name), (int)mode, 0, --- 2,8 ---- #include <sys/types.h> #include <sys/stat.h> ! PUBLIC int mkfifo(_CONST char *name, mode_t mode) { mode = (mode & 0777) | S_IFIFO; return(callm1(FS, MKNOD, len(name), (int)mode, 0, Sverre -- Sverre Froyen sverre@seri.gov, sunpeaks!seri!sverre
phil@cs.wwu.EDU (Phil Nelson) (06/15/91)
>I should point out that we're all running 1.5h.00 here. When I try to apply > ... >The library file mkfifo.c won't compile, which causes libc.a to not have all > ... >Ideas? Well, what version of gcc are you running? You should have at least a 1.37 binary. If not, one of 1.37 is on willow.cs.wwu.edu. I could put my current 1.39 binaries on willow if there was demand. As I remember, I has some trouble with the 1.35 cpp on some files. --Phil
bdale@col.hp.COM (Bdale Garbee) (06/15/91)
> I just went back to my machine to check, and my mkfifo.c does not compile. > So it must not be the compiler. In fact, I think it has to to with trying > to make things POSIX and or ANSI and not quit being right. Ok, thanks for the note. I applied Sverre's suggested change, and the libs built without incident. Built and installed kernel without incident. Am now working on the commands... but am currently running a 20meg disk, and it's tight with both sets of sources online! Gotta move some to the workstation... Bdale