From owner-freebsd-current@FreeBSD.ORG Sun Apr 22 19:07:57 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5951B106564A; Sun, 22 Apr 2012 19:07:57 +0000 (UTC) (envelope-from yanegomi@gmail.com) Received: from mail-ob0-f182.google.com (mail-ob0-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id EF7F48FC14; Sun, 22 Apr 2012 19:07:56 +0000 (UTC) Received: by obqv19 with SMTP id v19so16772578obq.13 for ; Sun, 22 Apr 2012 12:07:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=sW10mCL8B8nFPifV5ecMQ588+MU/j3WbePP8jfg7qr0=; b=wJFakP3/hUp2mChk2JO1pcpuEToO4yFZdEEeC/kJNHe1UOIKcVv5UK6I6HhH05zr9e l40sWeFbSMg5/oddqBb30+yJL/CZLEt+Ny/b9exYfVppnWJvCagUPLRkpeiFo2M+hPAB PnDu/ssyytZVd/7VuBM0HUfPISHntIcFITMPMJykeYCC2dyU9vlg0qJ9PxSCmJOZ4RbF HcLPyTwFjbyiQ/Oh34ZXyHM/FwnzN9tmLUs79jFYikjJTn5WKXehWPMBnpreK70Dw6t/ BE/Xd0PxTJIALWH8vXphIurUt9R+J/UM1BJEdDbm5kKty0xS2LoGTPctsCT4thXWsxco ELPg== Received: by 10.60.27.170 with SMTP id u10mr9143053oeg.50.1335121676618; Sun, 22 Apr 2012 12:07:56 -0700 (PDT) Received: from [192.168.2.5] (dpc691939029.direcpc.com. [69.19.39.29]) by mx.google.com with ESMTPS id qa9sm7666532obc.17.2012.04.22.12.07.44 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 22 Apr 2012 12:07:56 -0700 (PDT) Mime-Version: 1.0 (Apple Message framework v1257) Content-Type: text/plain; charset=windows-1252 From: Garrett Cooper In-Reply-To: <4F944139.4070309@FreeBSD.org> Date: Sun, 22 Apr 2012 12:07:29 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: References: <4F915384.6070308@semihalf.com> <4F919C50.70809@FreeBSD.org> <9B9312D3-489E-4EF1-85CB-0353024F6B94@gmail.com> <4F9428ED.6060902@FreeBSD.org> <3862F1CA-C1C8-49E6-B768-114A0A212496@gmail.com> <4F944139.4070309@FreeBSD.org> To: Dimitry Andric X-Mailer: Apple Mail (2.1257) Cc: Jan Sieka , Doug Barton , Current FreeBSD Subject: Re: buildworld fails on FreeBSD 7.x for HEAD from 19.04.2012 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 22 Apr 2012 19:07:57 -0000 On Apr 22, 2012, at 10:34 AM, Dimitry Andric wrote: > Well, I wouldn't want to run autoconf during build, firstly because it > is horribly slow, and second because the results will be less > predictable. Maybe during the bootstrap stage, it would be = acceptable. Sure -- that seems reasonable. > But even then, one of the configure scripts could fail due to too-old > system components, and you would be SOL. =85 but it would be a step forward from where things are currently at. = I'm not sure how well tested "source upgrade" paths are, but being able = to upgrade from the lowest supported version to the latest supported = version, then upgrading to CURRENT (at the very least) would be nice. > Usually, if something is arch-dependent in a config.h file, we simply > surround it with #ifdefs. Makes sense (assumption being that it can be controlled via the = config.h/configure.{ac,in} file). However, jemalloc recently disproved = this >_<. > Apparently the file(1) build needs a 'mkmagic' tool, which generates > .mgc files (the 'compiled' version of magic files). This requirement > was originally added in r81845, more than 10 years ago. I tested out removing libmagic from Makefile.inc1 and see that there's = some dependency magic going on there where building the library failed. > Yes, it might work, but there is no guarantee. I'm not sure if there = is > enough incentive to change this policy. It would potentially require = a > lot effort to make it always work. Understood and I guess the ownness is upon the stakeholders to fix this, = but there are a lot of companies that depend on things like this working = (at least to reduce pain when doing source upgrades). This would = probably be less of an issue for developers that use freebsd-update or = for companies that roll their own freebsd-update (and servers). I have = yet to run into a company that does this though (not saying there aren't = groups that could or do do this, but it's not the standard path). > I wasn't aware of any chroot hackery? A publicly available example is available in FreeNAS ( = http://freenas.svn.sourceforge.net/viewvc/freenas?view=3Drevision&revision= =3D8193 ); the hangup is building packages for a target system that = doesn't match the build host. Cheers! -Garrett=