From owner-freebsd-current@FreeBSD.ORG Wed Feb 19 05:16:25 2014 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 0C0CD121 for ; Wed, 19 Feb 2014 05:16:25 +0000 (UTC) Received: from mail-ob0-f180.google.com (mail-ob0-f180.google.com [209.85.214.180]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id BCDE6191E for ; Wed, 19 Feb 2014 05:16:24 +0000 (UTC) Received: by mail-ob0-f180.google.com with SMTP id wp4so19556718obc.39 for ; Tue, 18 Feb 2014 21:16:17 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:references:mime-version:in-reply-to:content-type :content-transfer-encoding:message-id:cc:from:subject:date:to; bh=iZ0KmOrDNnMh1OGfUKDF2qSFBjjpv9jdZK9KmkKn1vs=; b=RO6FDjE0t5ZolFn2eX0Tn1Whnxg6tjCphCFOfOH2bCyHsyKt3yCVFePYHE6sQIO+sV txinPp2HCpKoxmV94PdR4WDUe0lGtT4zkT1ROBy5P2IoYXxEMpehpXctNKX5m6V5iEJt 26BbeTNyAkFIY4fNNHoFaWutO9Zd3wkCvClgLAD42OtWNGJTegvqBkhefzK4Y5fGG8No QU+uFVTtwbWo7sRXRjpCE7pPAh74vQp4t+BMrfTrXWklx8M64xJpQD8ZscEVxD53nyGa dtLfufdg/S6VElSXUezyP+cFySBkqy9oKFa3U90U9Hlhx6/mcSQdxbPGIbvkeemFyFXO yyGA== X-Gm-Message-State: ALoCoQmGHSEUvlKrDboRzSRbKSw9+0xVS6O8NqwBJSkYAASILGHmoE/WEXaA6z04M53dz5bap2GA X-Received: by 10.60.94.231 with SMTP id df7mr121450oeb.69.1392786977762; Tue, 18 Feb 2014 21:16:17 -0800 (PST) Received: from [10.0.0.90] (50-78-194-198-static.hfc.comcastbusiness.net. [50.78.194.198]) by mx.google.com with ESMTPSA id z5sm66335490obg.13.2014.02.18.21.16.17 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 18 Feb 2014 21:16:17 -0800 (PST) References: <20140214173553.GA90364@onelab2.iet.unipi.it> <1392402215.1145.103.camel@revolution.hippie.lan> <1392751469.1145.24.camel@revolution.hippie.lan> Mime-Version: 1.0 (1.0) In-Reply-To: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Message-Id: X-Mailer: iPad Mail (11B554a) From: Warner Losh Subject: Re: HEAD buildkernel error (aic7xxx_seq.h is missing. Run 'make ahcfirmware') Date: Tue, 18 Feb 2014 22:16:15 -0700 To: Luigi Rizzo X-Mailman-Approved-At: Wed, 19 Feb 2014 12:39:07 +0000 Cc: FreeBSD Current , Ian Lepore X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.17 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: Wed, 19 Feb 2014 05:16:25 -0000 Sent from my iPad > On Feb 18, 2014, at 9:38 PM, Luigi Rizzo wrote: >=20 >> On Tue, Feb 18, 2014 at 11:24 AM, Ian Lepore wrote: >>=20 >>> On Fri, 2014-02-14 at 13:46 -0800, Luigi Rizzo wrote: >>>> On Fri, Feb 14, 2014 at 10:23 AM, Ian Lepore wrote: >>>>=20 >>>>> On Fri, 2014-02-14 at 18:35 +0100, Luigi Rizzo wrote: >>>>> on a freshly checked out HEAD, >>>>> "make toolchain" followed by "make buildkernel" fails at this stage: >>>>>=20 >>>>> ... >>>>> @ -> /usr/home/luigi/FreeBSD/head/sys >>>>> machine -> /usr/home/luigi/FreeBSD/head/sys/amd64/include >>>>> x86 -> /usr/home/luigi/FreeBSD/head/sys/x86/include >>>>> Error: aic7xxx_reg_print.c is missing. Run 'make ahcfirmware' >>>>> Error: aic7xxx_seq.h is missing. Run 'make ahcfirmware' >>>>> Error: aic7xxx_reg.h is missing. Run 'make ahcfirmware' >>>>>=20 >>>>> (don't think it matters, but i am cross compiling amd64 >>>>> from a stable/9 amd64 system, using clang). >>>>> I am not sure which commit triggered the problem, >>>>> but this used to work in the past -- toolchain was enough >>>>> to build a kernel. >>>>>=20 >>>>> cheers >>>>> luigi >>>>=20 >>>> That should be 'make kernel-toolchain', shouldn't it? >>>=20 >>> nope, fails with kernel-toolchain as well. >>> I need to do a full buildworld to avoid this problem. >>>=20 >>> cheers >>> luigi >>=20 >> This all used to work when cross-building from older systems, but there >> were some changes recently to get rid of the whole process of compiling >> the aicasm tool. There's supposed to be some sort of binary firmware >> blob involved now. >>=20 >> Did you try what the error message recommended (make ahcfirmware)? >=20 > i have not tried partly for laziness partly because usually > these suggestions require the command to run in the > cross-building environment. >=20 > But i guess my point is that building aicasm should be > part of kernel-toolchain (or whatever the target is for > "all the tools we need to build a kernel"). >=20 > Now, if aicasm is not changing we can perhaps try to > reuse the one in the host environment, in which > case i'd first try to support the same feature to > avoid rebuilding clang or gcc. The actual problem is old make. Old make doesn't parse this construct right,= but new make does. That's why some people hit it and others don't. The righ= t answer isn't to make aicasm a tool (which I tried and it failed the same w= ay). It would be better to disable these targets for old make. Warner > thanks > luigi > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"=