From owner-freebsd-current@freebsd.org Tue Oct 6 01:37:42 2020 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 5010F435EFF for ; Tue, 6 Oct 2020 01:37:42 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4C50TL1TZ1z3WC9 for ; Tue, 6 Oct 2020 01:37:42 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: from mail-qk1-f175.google.com (mail-qk1-f175.google.com [209.85.222.175]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) (Authenticated sender: kevans) by smtp.freebsd.org (Postfix) with ESMTPSA id 162C225F09 for ; Tue, 6 Oct 2020 01:37:42 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: by mail-qk1-f175.google.com with SMTP id f142so14929786qke.13 for ; Mon, 05 Oct 2020 18:37:42 -0700 (PDT) X-Gm-Message-State: AOAM533wB/KZLvDYOa5fknAICHfa4jl8QQzq2sBJSbBYGb7R0O0l/60k Z+exUS+CT9+8W6KTnfIAAF+WSOBk9hLj8bcWSFY= X-Google-Smtp-Source: ABdhPJy28S6kdZNc5Aao9EVsSiEKqwakAd+0koEiwWJFEAbK2+U9ONhc5L3stWZVBU919UpsFbb+N/v4+YAFQIl+AFI= X-Received: by 2002:a05:620a:ce3:: with SMTP id c3mr3126766qkj.103.1601948261755; Mon, 05 Oct 2020 18:37:41 -0700 (PDT) MIME-Version: 1.0 References: <20201005065439.2b5c7375@hermann.fritz.box> In-Reply-To: From: Kyle Evans Date: Mon, 5 Oct 2020 20:37:30 -0500 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: CURRENT: cross compiling 12-STABLE failure in: bin/cp/utils.c:517:14: error: member reference base type 'void' is not a structure or union To: "Hartmann, O." Cc: FreeBSD CURRENT Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.33 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: Tue, 06 Oct 2020 01:37:42 -0000 On Mon, Oct 5, 2020 at 9:54 AM Kyle Evans wrote: > > On Sun, Oct 4, 2020 at 11:55 PM Hartmann, O. wrote: > > > > For a couple of weeks now cross-compiling 12-STBALE on CURRENT fails > > due to an compiler error in bin/cp/utils.c, see details below. > > > > At this moment, CURRENT is at FreeBSD 13.0-CURRENT #39 r366364: Fri Oct > > 2 17:51:39 CEST 2020 amd64 and the sources for 12-STABLE are at > > revision 366437. > > > > The compilation environment is the NanoBSD environment of the CURRENT > > running host. > > > > A similar constellation of host and cross-compiled target (regarding OS > > versions, the hardware platform is slightly different, for the record) > > works: running a simple, well known "make" builds 12-STABLE without > > problems. > > > > I tried to build NanoBSD in a vanilla state (without conf files for > > WITH/WITHOUT tags), but the failure is always the same. > > > > Can someone help or give some hints where to look for the reason of th > > miscompilation? > > > > Hi, > > This is the same failure that was recently reported on the -stable@ > list for stable/11 (entitled "building releng11 on RELENG12 broken > ?"). It should only happen in the presence of WITHOUT_AUTO_OBJ, but > that shouldn't be the case on stable/12. It's clearly trying to > rebuild it into the src tree in the same way, though: > > [/pool/sources/12-STABLE/src/bin/cp/utils.o] Error code 1 > > This is interesting, but I'm afraid I don't know the nanobsd build > well enough to understand what's going on here. I suspect it's > related, though. > Another report came to me privately that had tracked it down in the other direction -- building -CURRENT from an earlier 12 -- that pointed directly at a bug in crunchgen on -CURRENT. I've committed the fix in r366466, you will want to update to that world or at least rebuild+reinstall crunchgen with that fix. Thanks, Kyle Evans