From nobody Sat Jun 26 09:18:31 2021 X-Original-To: stable@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 6955A11D2D84 for ; Sat, 26 Jun 2021 09:18:56 +0000 (UTC) (envelope-from mgrooms@shrew.net) Received: from mx1.shrew.net (mx1.shrew.net [38.97.5.131]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4GBpG7345Cz3w8c for ; Sat, 26 Jun 2021 09:18:55 +0000 (UTC) (envelope-from mgrooms@shrew.net) Received: from mail.shrew.net (mail.shrew.prv [10.24.10.20]) by mx1.shrew.net (8.15.2/8.15.2) with ESMTP id 15Q9IsYo025838 for ; Sat, 26 Jun 2021 04:18:54 -0500 (CDT) (envelope-from mgrooms@shrew.net) Received: from [10.24.1.224] (unknown [198.29.36.26]) by mail.shrew.net (Postfix) with ESMTPSA id E8FAD19ADF7 for ; Sat, 26 Jun 2021 04:18:48 -0500 (CDT) Subject: Re: arm64 stable/13 buildworld stops in bc To: stable@freebsd.org References: From: Matthew Grooms Message-ID: <230194b7-8836-8672-a793-a7a8c6dcb146@shrew.net> Date: Sat, 26 Jun 2021 04:18:31 -0500 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.11.0 List-Id: Production branch of FreeBSD source code List-Archive: https://lists.freebsd.org/archives/freebsd-stable List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.6.2 (mx1.shrew.net [10.24.10.10]); Sat, 26 Jun 2021 04:18:54 -0500 (CDT) X-Rspamd-Queue-Id: 4GBpG7345Cz3w8c X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of mgrooms@shrew.net designates 38.97.5.131 as permitted sender) smtp.mailfrom=mgrooms@shrew.net X-Spamd-Result: default: False [-3.30 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; ARC_NA(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; RBL_DBL_DONT_QUERY_IPS(0.00)[38.97.5.131:from]; TO_MATCH_ENVRCPT_ALL(0.00)[]; R_SPF_ALLOW(-0.20)[+mx]; MIME_GOOD(-0.10)[text/plain]; TO_DN_NONE(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[stable@freebsd.org]; RCPT_COUNT_ONE(0.00)[1]; SPAMHAUS_ZRD(0.00)[38.97.5.131:from:127.0.2.255]; RCVD_COUNT_THREE(0.00)[3]; DMARC_NA(0.00)[shrew.net]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:174, ipnet:38.0.0.0/8, country:US]; RCVD_TLS_LAST(0.00)[]; MAILMAN_DEST(0.00)[stable] X-ThisMailContainsUnwantedMimeParts: N On 6/26/2021 12:20 AM, Stefan Esser wrote: > Am 26.06.21 um 04:30 schrieb Matthew Grooms: >> Hi All, >> >> I've been trying to build stable/13 kernel & world periodically for arm64 and >> either I'm not having very much luck or it's broken more times than it >> compiles. Is there an automated process that's checking builds for that platform? > Hi Matthew, > > there automated CI tests for all supported platforms, and if bc had failed > to build there, I'd have been informed. > >> Most recently, world stops building with bc ( see below ). However, that looks >> like that was last touched on June 1st. Has the build really been broken since >> then? :/ > Not for me ... > >> --- all_subdir_usr.bin --- >> /usr/src/contrib/bc/src/program.c:515:28: error: too few arguments to function >> call, expected 3, have 2 >>         bc_file_puts(&vm.fout, str); >>         ~~~~~~~~~~~~              ^ >> /usr/src/contrib/bc/include/file.h:81:6: note: 'bc_file_puts' declared here >> void bc_file_puts(BcFile *restrict f, BcFlushType type, const char *str); >>      ^ > This looks to me like the result of an incomplete update of the sources. > > History editing has been added a few releases back and the function signature > of bc_files_puts has been changed to take 3 instead of 2 arguments. > > It looks like you got a mismatch between this header and the callers of this > function. Specifically, line 515 mentioned in the error message above is line > 517 in up-to.date sources and reads: > > bc_file_puts(&vm.fout, bc_flush_save, str); > > Definitely 3 parameters there ... > > See https://cgit.freebsd.org/src/tree/contrib/bc/src/program.c?h=stable/13#n512 > line 517 - that's what your program.c should look like ... > >> /usr/src/contrib/bc/src/program.c:529:21: error: too few arguments to function >> call, expected 2, have 1 >>                 bc_vm_putchar('\0'); >>                 ~~~~~~~~~~~~~     ^ >> /usr/src/contrib/bc/include/vm.h:437:6: note: 'bc_vm_putchar' declared here >> void bc_vm_putchar(int c, BcFlushType type); >>      ^ >> /usr/src/contrib/bc/src/program.c:552:23: error: too few arguments to function >> call, expected 2, have 1 >>                                 bc_vm_putchar('\\'); >>                                 ~~~~~~~~~~~~~     ^ >> /usr/src/contrib/bc/include/vm.h:437:6: note: 'bc_vm_putchar' declared here >> void bc_vm_putchar(int c, BcFlushType type); >>      ^ >> /usr/src/contrib/bc/src/program.c:556:18: error: too few arguments to function >> call, expected 2, have 1 >>                 bc_vm_putchar(c); >>                 ~~~~~~~~~~~~~  ^ >> /usr/src/contrib/bc/include/vm.h:437:6: note: 'bc_vm_putchar' declared here >> void bc_vm_putchar(int c, BcFlushType type); >>      ^ >> /usr/src/contrib/bc/src/program.c:601:25: error: too few arguments to function >> call, expected 2, have 1 >>                 bc_file_flush(&vm.fout); >>                 ~~~~~~~~~~~~~         ^ >> /usr/src/contrib/bc/include/file.h:76:6: note: 'bc_file_flush' declared here >> void bc_file_flush(BcFile *restrict f, BcFlushType type); >>      ^ >> /usr/src/contrib/bc/src/program.c:607:49: error: too few arguments to function >> call, expected 2, have 1 >>                         if (inst == BC_INST_PRINT) bc_vm_putchar('\n'); >> ~~~~~~~~~~~~~     ^ >> /usr/src/contrib/bc/include/vm.h:437:6: note: 'bc_vm_putchar' declared here >> void bc_vm_putchar(int c, BcFlushType type); > All the other error messages do point at a mix of source files from before > and after introduction of the history feature, too ... > > The line numbers in your version of program.c seem to be off, compared to > the current sources, e.g. check out lines 609 and 610 on the above given URL > for the correct sources that correspond to that last error message. > > Update your sources to a consistent state and your issue should be resolved. > > Let me know if there are any further problems with this program. Hi Stefan & Mark, I appreciate the quick response. That is strange. This build host didn't exist a few days ago and I started with a fresh git clone of stable/13.I could try to re-clone that but I'm not sure how it could have a mix of old and new sources. I also do a git pull before every build attempt ... root@build:/usr/src # git pull Already up to date. root@build:/usr/src # git status On branch stable/13 Your branch is up to date with 'origin/stable/13'. However, I am cross compiling aarch64 from an amd64 host which is running the release branch .... root@build:/usr/src # freebsd-version -u 13.0-RELEASE-p2 Do I need to update my amd64 build host to stable before cross compiling aarch64? I wouldn't think that compiling sources from /usr/src would be affected by release files installed on the build host. Thanks, -Matthew