From owner-freebsd-bugs  Fri Nov  1 08:45:56 1996
Return-Path: owner-bugs
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id IAA23641
          for bugs-outgoing; Fri, 1 Nov 1996 08:45:56 -0800 (PST)
Received: from ip.sensenet.com (ip.sensenet.com [199.33.238.23])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id IAA23627
          for <freebsd-bugs@freebsd.org>; Fri, 1 Nov 1996 08:45:50 -0800 (PST)
From: micro@sensenet.com
Received: (from micro@localhost) by ip.sensenet.com (8.7.5/8.7.3) id LAA00503 for freebsd-bugs@freebsd.org; Fri, 1 Nov 1996 11:45:40 -0500
Date: Fri, 1 Nov 1996 11:45:40 -0500
Message-Id: <199611011645.LAA00503@ip.sensenet.com>
To: freebsd-bugs@freebsd.org
Subject: Re: MAXMEM in LINT...
Sender: owner-bugs@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Fri Nov  1 11:37:44 EST 1996

> This has changed in -current.
>
> Btw., yours should be
>
>       options "MAXMEM='(128*1024)'"
>
> to be exact.  The double quotes protect it from being misinterpreted
> by config(8), while the single quotes are for the shell when building
> the kernel.

Using the above breaks compilation of the kernel:
        ../../i386/i386/machdep.c :line 1181 Character constant too large:

The line in machdep.c is:

        Maxmem = MAXMEM/4;

In opt_machdep.h we have:
        #define MAXMEM  '(128*1024)'

when this is changed to:
        #define MAXMEM (128*1024)
compilation continues.

-primus

PS      I am now using 2.2-961014-SNAP