Xref: utzoo comp.unix.microport:3566 comp.sources.d:3863 Path: utzoo!attcan!uunet!cs.utexas.edu!csd4.milw.wisc.edu!srcsip!nic.MR.NET!hal!ncoast!allbery From: allbery@ncoast.ORG (Brandon S. Allbery) Newsgroups: comp.unix.microport,comp.sources.d Subject: Re: Is anyone executing Cnews on microport 2.4 ? Message-ID: <13835@ncoast.ORG> Date: 12 Jul 89 22:53:50 GMT References: <1884@cbnewsh.ATT.COM> <14@pfm.UUCP> Reply-To: allbery@ncoast.ORG (Brandon S. Allbery) Followup-To: comp.unix.microport Organization: Cleveland Public Access UN*X, Cleveland, Oh Lines: 46 As quoted from <14@pfm.UUCP> by root@pfm.UUCP (TSOS of PFM): +--------------- | cab@cbnewsh.ATT.COM (CAB) writes: | >Tips on compilation appreciated, my compiler seems to barf | >on relay/hdrdefs.c line 49. The error message is | >compiler error: expression causes compiler loop: try simplifying +--------------- Some compilers aren't capable of handling complex expressions. And some expressions that look rather complex to the compiler look downright simple to us people, because some combination of two or three operators turns out to require a lot of work on the part of the compiler to implement. The error message says exactly what it means: look at line 49 of relay/hdrdefs.c, find the expression that's causing the problem, and split it up by storing temporary results in variables. +--------------- | No, sorry, I have the microport sys V 386 Rel. 3.0, but I have | trouble with the "spacefor" - the whole time inews says that there | is not enough space at my /usr/spool/news (32 MB free space !). +--------------- The release notes warn that "spacefor" WILL need to be adjusted for a given system.... Whoever wrote the System V code for "spacefor" assumed that the device name always fits exactly between the parentheses. This is not always true. I just hardcoded for our system (needed a quick fix, "doexpire" was hammering its head against the wall), but a better way to extract the free space is: df something | sed '/^[^(]*([^ ][^ ]* *): *\([0-9][0-9]*\) *b.*$/s//\1/' This should work on any System V and also works with the (slightly different) System III df. (Well, let me hedge that: it works with System III df, because I tested it just now. However, ncoast is not (yet) System V so I can't test it under System V right now. I'll test it on the 386 at work tomorrow and let you know what needs to be changed.) ++Brandon -- Brandon S. Allbery, moderator of comp.sources.misc allbery@ncoast.org uunet!hal.cwru.edu!ncoast!allbery ncoast!allbery@hal.cwru.edu Send comp.sources.misc submissions to comp-sources-misc@ NCoast Public Access UN*X - (216) 781-6201, 300/1200/2400 baud, login: makeuser * "ncoast" regenerates again! The 5th "ncoast", coming August 1 (stay tuned) *