Date: Mon, 22 Jun 2015 20:00:13 +0200 (CEST) From: =?ISO-8859-1?Q?Trond_Endrest=F8l?= <Trond.Endrestol@fagskolen.gjovik.no> To: Jason Evans <jasone@freebsd.org> Cc: Garrett Cooper <yaneurabeya@gmail.com>, FreeBSD current <freebsd-current@freebsd.org> Subject: Re: amd64 base/head r284673 fails to build on amd64 base/head r284639, pilot error? Message-ID: <alpine.BSF.2.20.1506221951120.69928@mail.fig.ol.no> In-Reply-To: <6D234532-B476-4D50-89EE-4BE424578BFC@freebsd.org> References: <alpine.BSF.2.20.1506211155290.69928@mail.fig.ol.no> <65E0AFBE-0E73-42C9-A140-4AC617500E73@gmail.com> <6D234532-B476-4D50-89EE-4BE424578BFC@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 22 Jun 2015 09:41-0700, Jason Evans wrote: > On Jun 21, 2015, at 1:05 PM, Garrett Cooper <yaneurabeya@gmail.com> wrote: > > On Jun 21, 2015, at 3:16, Trond Endrestøl <Trond.Endrestol@fagskolen.gjovik.no> wrote: > >> Am I the only one who fails to build recent base/head (r284673) on > >> pretty recent base/head (r284639)? This is on amd64 with ZFS and BEs. > > > > ... > > > >> CC=clang > >> CXX=clang++ > >> CPP=clang-cpp > > > > You need to remove these lines. They shouldn?t have been set before or after the commits from projects/bmake . > > I hit the same build failure, and I don't have any of those lines in my /etc/make.conf. Mine is: > > STRIP= > > # added by use.perl 2013-01-21 16:11:13 > PERL_VERSION=5.12.4 > WITH_PKGNG=yes > > The STRIP= definition appears to have no impact with regard to the build failure. > > I routinely do multiple buildworld/installworld cycles when updating, so I am pretty sure that this is a self bootstrap failure; buildworld/installworld succeeds the first time, but not the second time. r283923 does not have the problem, so this was introduced sometime in the past three weeks. I concur. DTrace support is b0rken. I installed a fresh VM at work using Glen's recent base/head snapshot, 20150618 r284544. I created an /etc/src.conf file with only WITH_CTF=yes. I got hold of base/head r284678, started a -j4 buildworld + buildkernel, and immediately ctfconvert started complaining about nothing to do, i.e.: ERROR: ctfconvert: rc = -1 No entry found [dwarf_next_cu_header_c(61)] Same result with -j1. I probably forgot to mention earlier, after my problems began last week, I always wiped /usr/obj clean before building again. I haven't activated dtraceall.ko using /boot/loader.conf, but I guess those that dare, end up with a kernel panic. I certainly did that last week. -- +-------------------------------+------------------------------------+ | Vennlig hilsen, | Best regards, | | Trond Endrestøl, | Trond Endrestøl, | | IT-ansvarlig, | System administrator, | | Fagskolen Innlandet, | Gjøvik Technical College, Norway, | | tlf. mob. 952 62 567, | Cellular...: +47 952 62 567, | | sentralbord 61 14 54 00. | Switchboard: +47 61 14 54 00. | +-------------------------------+------------------------------------+ From owner-freebsd-current@FreeBSD.ORG Mon Jun 22 18:14:54 2015 Return-Path: <owner-freebsd-current@FreeBSD.ORG> Delivered-To: freebsd-current@nevdull.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 900B1C2C for <freebsd-current@nevdull.freebsd.org>; Mon, 22 Jun 2015 18:14:54 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: from mail-vn0-x22d.google.com (mail-vn0-x22d.google.com [IPv6:2607:f8b0:400c:c0f::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 444EEAB4; Mon, 22 Jun 2015 18:14:54 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: by vnbg129 with SMTP id g129so7062750vnb.2; Mon, 22 Jun 2015 11:14:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:content-transfer-encoding :in-reply-to:user-agent; bh=rQyrazNZj3/pZj0s+wqUQj5SLpAqQX2WQpYYw1jJ5Ts=; b=sWIF/kJXlyIKK3xm4p267w84x1tV4x8t84YUq1+slyKWlqphejcSQbSkaN/Io/L8po hvY5ScgYaMb6fZJhBIo4HWzwkSpWtLGNgO8ELqraN0hNOuB3/8Nv/kWUjS5Rx9QwJLn6 RTxfgkFAMkjmvnqxWNZS067Qsneor/f5xGgiZwkYLpcpSbluRIe9aommuDRR3Xq/1Zjk 93TYD6MPhXUZjyX6LOHAppGzda8yu3mbZ8E+OsCU7lnd4m9M8gXBdBCILDs4sc9r3A81 XxntxIHfM0iwJ81hOfmlE6F7f9OvDnQR4+ulMRH8+rG5i52WZVXsdjdYaJdctucjrros GKKA== X-Received: by 10.53.0.226 with SMTP id bb2mr20312630vdd.4.1434996893458; Mon, 22 Jun 2015 11:14:53 -0700 (PDT) Received: from muskytusk ([104.236.250.12]) by mx.google.com with ESMTPSA id ml19sm3754933vdb.7.2015.06.22.11.14.51 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 22 Jun 2015 11:14:52 -0700 (PDT) Sender: Mark Johnston <markjdb@gmail.com> Date: Mon, 22 Jun 2015 18:14:19 +0000 From: Mark Johnston <markj@FreeBSD.org> To: Trond =?iso-8859-1?Q?Endrest=F8l?= <Trond.Endrestol@fagskolen.gjovik.no> Cc: Jason Evans <jasone@freebsd.org>, Garrett Cooper <yaneurabeya@gmail.com>, FreeBSD current <freebsd-current@freebsd.org> Subject: Re: amd64 base/head r284673 fails to build on amd64 base/head r284639, pilot error? Message-ID: <20150622181419.GB98009@muskytusk> References: <alpine.BSF.2.20.1506211155290.69928@mail.fig.ol.no> <65E0AFBE-0E73-42C9-A140-4AC617500E73@gmail.com> <6D234532-B476-4D50-89EE-4BE424578BFC@freebsd.org> <alpine.BSF.2.20.1506221951120.69928@mail.fig.ol.no> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <alpine.BSF.2.20.1506221951120.69928@mail.fig.ol.no> User-Agent: Mutt/1.5.23 (2014-03-12) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussions about the use of FreeBSD-current <freebsd-current.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/options/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: Mon, 22 Jun 2015 18:14:54 -0000 On Mon, Jun 22, 2015 at 08:00:13PM +0200, Trond Endrestøl wrote: > On Mon, 22 Jun 2015 09:41-0700, Jason Evans wrote: > > > On Jun 21, 2015, at 1:05 PM, Garrett Cooper <yaneurabeya@gmail.com> wrote: > > > On Jun 21, 2015, at 3:16, Trond Endrestøl <Trond.Endrestol@fagskolen.gjovik.no> wrote: > > >> Am I the only one who fails to build recent base/head (r284673) on > > >> pretty recent base/head (r284639)? This is on amd64 with ZFS and BEs. > > > > > > ... > > > > > >> CC=clang > > >> CXX=clang++ > > >> CPP=clang-cpp > > > > > > You need to remove these lines. They shouldn?t have been set before or after the commits from projects/bmake . > > > > I hit the same build failure, and I don't have any of those lines in my /etc/make.conf. Mine is: > > > > STRIP= > > > > # added by use.perl 2013-01-21 16:11:13 > > PERL_VERSION=5.12.4 > > WITH_PKGNG=yes > > > > The STRIP= definition appears to have no impact with regard to the build failure. > > > > I routinely do multiple buildworld/installworld cycles when updating, so I am pretty sure that this is a self bootstrap failure; buildworld/installworld succeeds the first time, but not the second time. r283923 does not have the problem, so this was introduced sometime in the past three weeks. > > I concur. DTrace support is b0rken. > > I installed a fresh VM at work using Glen's recent base/head snapshot, > 20150618 r284544. I created an /etc/src.conf file with only > WITH_CTF=yes. I got hold of base/head r284678, started a -j4 > buildworld + buildkernel, and immediately ctfconvert started > complaining about nothing to do, i.e.: > > ERROR: ctfconvert: rc = -1 No entry found [dwarf_next_cu_header_c(61)] > > Same result with -j1. These warnings are benign and are the result of compiling with WITH_CTF and without debug info. Compiling with WITH_DEBUG_FILES or DEBUG_FLAGS=-g will allow CTF to be generated, but its absence shouldn't cause any problems (aside from these annoying warnings). > > I probably forgot to mention earlier, after my problems began last > week, I always wiped /usr/obj clean before building again. > > I haven't activated dtraceall.ko using /boot/loader.conf, but I guess > those that dare, end up with a kernel panic. I certainly did that last > week. Can you elaborate on this? There don't seem to be any reports of such a panic, and I certainly dare to load dtraceall.ko on head. :) -Mark
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.20.1506221951120.69928>