From owner-freebsd-ports Fri Jan 10 07:52:28 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id HAA16824 for ports-outgoing; Fri, 10 Jan 1997 07:52:28 -0800 (PST) Received: from po1.glue.umd.edu (root@po1.glue.umd.edu [129.2.128.44]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id HAA16814 for ; Fri, 10 Jan 1997 07:52:23 -0800 (PST) Received: from skipper.eng.umd.edu (skipper.eng.umd.edu [129.2.103.24]) by po1.glue.umd.edu (8.8.3/8.7.3) with ESMTP id KAA25837; Fri, 10 Jan 1997 10:52:20 -0500 (EST) Received: from localhost (chuckr@localhost) by skipper.eng.umd.edu (8.8.3/8.7.3) with SMTP id KAA10909; Fri, 10 Jan 1997 10:52:19 -0500 (EST) X-Authentication-Warning: skipper.eng.umd.edu: chuckr owned process doing -bs Date: Fri, 10 Jan 1997 10:52:19 -0500 (EST) From: Chuck Robey X-Sender: chuckr@skipper.eng.umd.edu To: "Jim Spath (Webmaster Jim)" cc: Warner Losh , ports@freebsd.org Subject: Re: Niklas Hallqvist: archivers/hpack.non-usa.only In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-ports@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Fri, 10 Jan 1997, Jim Spath (Webmaster Jim) wrote: > On Thu, 9 Jan 1997, Warner Losh wrote: > > > In message David Nugent writes: > > : No, they don't have sys/param.h. It is a BSDism that is only > > : recently being more widely adopted. IIRC, AIX and DG's UNIX > > : don't have it either. I don't currently have access to either > ... > > well as IRIX 5.2 and 6.x. I don't know about DG's unix, however I > > suspect that it does have it based on reports I received, along with > > diffs, that OI compile on that machine with a single, small change to > > the files needing to be included for time stuff. The DG system in > > question was a SYSVr4.something based system for the mk88000. > > > > I've sent mail to some friends that I have with these systems for them > > to check to be sure that my memory is correct. They have not yet > > responded. Guys, I want to remind all you of something you might be overlooking here. WE DON'T CARE WHICH SYSTEMS HAVE OR DON'T HAVE SYS/PARAM.H. Excuse me for shouting, this isn't the first time I've posted that. We only care about detecting, non-destructively (both for systems that do and for those that don't have it) whether of not it's there. We are aware that a lot of systems don't have it. The proposal is to detect either the cpp-defined "unix" or "__unix__" variable, which should indicate (if it's found) that sys/param.h does in fact exist on a particular system. If you find a system that defined either of those symbols, but DOESN'T have sys/param.h, that would really be of particular interest. Detect the unix/__unix_ either by a short program, of by doing a cpp -dM, followed by a control D, and it would print out all the locally defined variables. ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@eng.umd.edu | communications topic, C programming, and Unix. 9120 Edmonston Ct #302 | Greenbelt, MD 20770 | I run Journey2 and picnic, both FreeBSD (301) 220-2114 | version 3.0 current -- and great FUN! ----------------------------+-----------------------------------------------