From owner-freebsd-current  Wed Oct 29 20:29:37 1997
Return-Path: <owner-freebsd-current>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id UAA12846
          for current-outgoing; Wed, 29 Oct 1997 20:29:37 -0800 (PST)
          (envelope-from owner-freebsd-current)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id UAA12839
          for <freebsd-current@freefall.FreeBSD.org>; Wed, 29 Oct 1997 20:29:33 -0800 (PST)
          (envelope-from bde@zeta.org.au)
Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.6.9) id PAA12612; Thu, 30 Oct 1997 15:24:25 +1100
Date: Thu, 30 Oct 1997 15:24:25 +1100
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199710300424.PAA12612@godzilla.zeta.org.au>
To: asami@cs.berkeley.edu, bde@zeta.org.au,
        freebsd-current@freefall.FreeBSD.org, gurney_j@efn.org,
        peter@spinner.netplex.com.au
Subject: Re: bad system call - world build
Sender: owner-freebsd-current@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

>Actually, my question should have been: why does it work if you build
>3.0-current on 2.2-stable (as of now)?  I just confirmed that I can

2.2-"stable" has issetugid() in the kernel.

>build 3.0 on my 2.2-stable machine, can build 2.2-stable on 2.1.5R but
>not 3.0-current on 2.1.5R.  (I don't have 2.2.2R.)

That is because of a missing features in 2.2-"stable".  It doesn't
actually use issetugid() in libc/gen/glob.c, libc/nls/msgcat.c or
libtermcap/termcap.c, although it uses it in libc/locale/setlocale.c
and libc/locale/setrunelocale.c

For libtermcap there is also a library version numbering problem.
libtermcap.so's linked to libc.so.2.2 can't expect to find issetugid()
in libc even if the kernel has it.  This was fixed in -current by
bumping the _major_ number of libtermcap.

Bruce