From owner-freebsd-current@FreeBSD.ORG  Tue Jun 22 15:36:35 2004
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 5C7B616A4CE
	for <current@FreeBSD.org>; Tue, 22 Jun 2004 15:36:35 +0000 (GMT)
Received: from server.alexdupre.com (host245-49.pool8288.interbusiness.it
	[82.88.49.245])	by mx1.FreeBSD.org (Postfix) with ESMTP id 7AD0043D5F
	for <current@FreeBSD.org>; Tue, 22 Jun 2004 15:36:34 +0000 (GMT)
	(envelope-from ale@FreeBSD.org)
Received: from [192.168.0.101] (thunder.alexdupre.com [192.168.0.101])
	i5MFaQHO021479;	Tue, 22 Jun 2004 17:36:27 +0200 (CEST)
	(envelope-from ale@FreeBSD.org)
Message-ID: <40D851FA.1030103@FreeBSD.org>
Date: Tue, 22 Jun 2004 17:36:26 +0200
From: Alex Dupre <ale@FreeBSD.org>
User-Agent: Mozilla Thunderbird 0.7 (Windows/20040616)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Andrea Campi <andrea+freebsd_current@webcom.it>
References: <20040622151128.GA82977@webcom.it>
In-Reply-To: <20040622151128.GA82977@webcom.it>
X-Enigmail-Version: 0.84.1.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
cc: current@FreeBSD.org
Subject: Re: Is NO_YP_LIBC working?
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 22 Jun 2004 15:36:35 -0000

Andrea Campi wrote:

> in the process of setting up a nanobsd-based system I've stumbled on so
> many issues during a make buildworld that I've started wondering whether
> NO_YP_LIBC is meant to work. Is anybody using it, and do you need local
> changes?

Currently it's broken. Try this patch: 
http://sources.zabbadoz.net/freebsd/patchset/10039-no-yp-libc.diff

> Another question is what should it actually do. Parts of librpcsvc and
> libwrap call yp_*, as do libexec/{mknetid,ypxfr); it doesn't make sense
> to not compile YP support in libc but try (and fail) to compile these.
> Maybe we should have a single variable (NOYP or NO_YP, I don't care)
> that turns off all YP-only code.

This is exactly what the patch does (or at least it should, I never 
tried it).

Ciao ;-)

-- 
Alex Dupre