NetBSD Problem Report #41709

From kre@munnari.OZ.AU  Mon Jul 13 10:45:16 2009
Return-Path: <kre@munnari.OZ.AU>
Received: from ( [])
	by (Postfix) with ESMTP id AC63363BADF
	for <>; Mon, 13 Jul 2009 10:45:16 +0000 (UTC)
Message-Id: <>
Date: Mon, 13 Jul 2009 17:45:08 +0700 (ICT)
From: kre@munnari.OZ.AU
Subject: emulators/compat40 cannot build on NetBSD 4 systems
X-Send-Pr-Version: 3.95

>Number:         41709
>Category:       pkg
>Synopsis:       emulators/compat40 cannot build on NetBSD 4 systems
>Confidential:   no
>Severity:       serious
>Priority:       high
>Responsible:    pkg-manager
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Mon Jul 13 10:50:00 +0000 2009
>Originator:     Robert Elz
>Release:        NetBSD 4.0_STABLE
	Prince of Songkla University
System: NetBSD 4.0_STABLE NetBSD 4.0_STABLE (JADE-1.696-20080517) #9: Fri May 23 18:55:13 ICT 2008 i386
Architecture: i386
Machine: i386
	The compatNM packages are all defined so that they refuse to
	build on system version NM itself (N.M really) - and that's
	wrong, only earlier versions should be rejected.

	I build binary packages on a NetBSD 4.0 system (which isn't
	changing any time soon as with a 5.0 kernel, I have processes
	that simply hang).   That means I can only build NetBSD 4.0
	(or earlier) packages, wven using pkg_comp and libkver (the
	running kernel, at least, needs to be at least as high a
	version as is being emulated by libkver or things are likely to fail).

	I want to run the packages I build on other systems (that's
	a reason for binary packages, not the only reason, but one of them)
	and some of those systems are running NetBSD 5 or -current (or
	something that was -current and is > 5.0).   For that, I need
	compat40 installed.   But I can't build compat40 because I am
	only running a NetBSD 4 (based - see the Release and Environment PR
	fields) kernel, an environment in which compat40 refuses to

	This has been discussed before on tech-pkg, with no disagreement
	to changing the pkg to allow it to be built on NetBSD 4.0 as
	well (there isn't, and logically cannot be, any problem beinging
	compat40 on NetBSD 4.0, etc).   But nothing changed, so I assume
	the request fell throuh a crack.   Hence this PR ...

	Blindingly obvious...


ONLY_FOR_PLATFORM=      NetBSD-4.99.*-* NetBSD-[5-9]*-* NetBSD-[1-9][0-9]*-*


ONLY_FOR_PLATFORM=      NetBSD-[4-9]*-* NetBSD-[1-9][0-9]*-*

	There's no need to be able to build compat40 on older NetBSD's, 4.0
	packages in general can't be built there, even if this one
	conceivably could (and as there's no point doing do, I never
	tested that).

	This PR relates only to emulators/compat40 - all the older ones (that
	I looked at anyway) have the same problem, I just never noticed it
	before, as until now my build system hadn't ever been an older NetBSD
	version than the target systems.   There's no longer any need to fix
	any of the others though, as supporting building on NetBSD 3.0
	(or older) is no longer expected, so being unable to build compat30
	on 3.0 is no longer relevant.

	There's also not yet an emulators/compat50 to have a similar
	problem which would need to be fixed.  (There probably should be).

	While fixing this, whoever does it might also want to look at this
	comment in compat40/Makefile ...

# XXX Until NetBSD 5.0 is released, we fetch the distfiles into a date-specific
# XXX subdirectory where the date corresponds to the build of HEAD against
# XXX which these compat40 packages were generated.

	and notice that the "until" passed months ago...

NetBSD Home
NetBSD PR Database Search

(Contact us) $NetBSD: query-full-pr,v 1.39 2013/11/01 18:47:49 spz Exp $
$NetBSD:,v 1.8 2006/05/07 09:23:38 tsutsui Exp $
Copyright © 1994-2007 The NetBSD Foundation, Inc. ALL RIGHTS RESERVED.