From nobody Mon May 9 10:29:39 2022 X-Original-To: freebsd-ports@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 21FE01AC19C5 for ; Mon, 9 May 2022 10:29:54 +0000 (UTC) (envelope-from freebsd-ports@dino.sk) Received: from mailhost.netlabit.sk (mailhost.netlabit.sk [84.245.65.72]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4Kxcqj1dp2z3C4j for ; Mon, 9 May 2022 10:29:53 +0000 (UTC) (envelope-from freebsd-ports@dino.sk) Received: from mp2.dino.sk (fw3.dino.sk [84.245.95.254]) (AUTH: LOGIN milan, TLS: TLSv1/SSLv3,256bits,AES256-SHA) by mailhost.netlabit.sk with ESMTPSA; Mon, 09 May 2022 12:29:45 +0200 id 00DC4C60.6278ED19.00006479 Date: Mon, 9 May 2022 12:29:39 +0200 From: Milan Obuch To: freebsd-ports@freebsd.org Subject: Re: Recent u-boot port change Message-ID: <20220509122939.4e8a9d48@mp2.dino.sk> In-Reply-To: <83B78F74-9C4D-4727-AC71-E21ED5E7E1AA@chrisbowman.com> References: <83B78F74-9C4D-4727-AC71-E21ED5E7E1AA@chrisbowman.com> X-Mailer: Claws Mail 3.19.0 (GTK+ 2.24.33; amd64-portbld-freebsd13.1) List-Id: Porting software to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-ports List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-ports@freebsd.org X-BeenThere: freebsd-ports@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Rspamd-Queue-Id: 4Kxcqj1dp2z3C4j X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of freebsd-ports@dino.sk designates 84.245.65.72 as permitted sender) smtp.mailfrom=freebsd-ports@dino.sk X-Spamd-Result: default: False [-3.29 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.99)[-0.994]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; R_SPF_ALLOW(-0.20)[+mx]; MIME_GOOD(-0.10)[text/plain]; TO_DN_NONE(0.00)[]; DMARC_NA(0.00)[dino.sk]; RCPT_COUNT_ONE(0.00)[1]; NEURAL_HAM_LONG(-1.00)[-0.998]; MID_RHS_MATCH_FROMTLD(0.00)[]; NEURAL_HAM_SHORT(-1.00)[-1.000]; MLMMJ_DEST(0.00)[freebsd-ports]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:5578, ipnet:84.245.64.0/18, country:SK]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[] X-ThisMailContainsUnwantedMimeParts: N On Sun, 8 May 2022 15:29:08 -0700 Christopher Bowman wrote: > First, I truly do appreciate all the effort every one puts into > FreeBSD. Apologies if I=E2=80=99m not quite following protocol here: > > I see that u-boot master port was recently upgraded to pull u-boot > 2022.04. I have a private port that I=E2=80=99ve been using but looks me = to > an earlier version of the port since the recent one uses a version of > u-boot I can=E2=80=99t get to work. I attempted to update my private port > based on the new version to see if I can get it working and committed > However, I=E2=80=99m confused how the master port ever built. Hi, I am building some of the u-boot ports in order to verify the process and test them locally. I think master port is not built directly, it serves as common place for u-boot related patches and similar things. You should build your slave port. > When I try to build with my patches applied I get the following > errors: >=20 > tools/mkeficapsule.c:18:10: fatal error: 'uuid/uuid.h' file not found > #include > ^~~~~~~~~~~~~ > 1 error generated. >=20 > There is a uuid.h in /usr/include so I patched this. >=20 > Then I come across: >=20 > tools/mkeficapsule.c:21:10: fatal error: 'gnutls/gnutls.h' file not > found #include > ^~~~~~~~~~~~~~~~~ > 1 error generated. >=20 > Ok so I install gnutls and patch the make file to also search > /usr/local/include where that gets installed. Next I get: >=20 > tools/mkeficapsule.c:631:8: warning: implicit declaration of function > 'uuid_parse' is invalid in C99 [-Wimplicit-function-declaration] if > (uuid_parse(optarg, uuid_buf)) { ^ > 1 warning generated. >=20 > uuid_parse doesn=E2=80=99t exist in /usr/include/uudi.h but > /usr/include/sys/uuid.h which is included by /usr/include/uuid.h does > have a parse_uuid (note: not uuid_parse) which looks right so I patch > again but now I get: >=20 > tools/mkeficapsule.c:631:8: warning: implicit declaration of function > 'parse_uuid' is invalid in C99 [-Wimplicit-function-declaration] if > (parse_uuid(optarg, uuid_buf)) { ^ > 1 warning generated. >=20 > at which point I give up and start to wonder how any of the other > u-boot ports build? I mean this doesn=E2=80=99t look very specific to my > port which is a Xilinx Zynq/arm architecture. I didn=E2=80=99t see any ot= her > Zynq ports in the tree so I couldn=E2=80=99t look at them for reference. > This all happens on a 13.0 system with a recent git copy of ports. > I have some local ports for Zynq based boards. I just did not verified them yet with new 2022.04 u-boot, I used old FreeBSD box for tests which needs full upgrade (in process). But testing u-boot ports locally is just before trying local ports... One hint - there is freebsd-uboot mailing list, designed specifically for u-boot related issues. While it is not much activity there, I think it is more appropriate for this discussion... Regards, Milan