From nobody Mon May 9 17:08:17 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 6901E1AD0972 for ; Mon, 9 May 2022 17:08:22 +0000 (UTC) (envelope-from crb@chrisbowman.com) Received: from mail-pg1-x533.google.com (mail-pg1-x533.google.com [IPv6:2607:f8b0:4864:20::533]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4KxngT1GBbz4n8R for ; Mon, 9 May 2022 17:08:21 +0000 (UTC) (envelope-from crb@chrisbowman.com) Received: by mail-pg1-x533.google.com with SMTP id s16so2484921pgs.3 for ; Mon, 09 May 2022 10:08:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chrisbowman-com.20210112.gappssmtp.com; s=20210112; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=UReJ/d8XOUJAR7QWS/3VOpB8r2M1WLYHMJENgOtgPk4=; b=Zmju5VdL9JtZ9ChRUEhYk4m7hj2EDPDkzOnTCVgTf5cIvoOY0OOZK2io0Hbmd+qNCY L87mGrJOk2fM+zSGfNRhqzZJnjHSOtf8BwdRf7Mos29WfFhBN/b1Il1YTcjeZ8lRS4R7 t6yw0Hwa/8k94Az5sKHNE9bATW6oitLFx1IdAeFC68zVBFS50AwtEgjNtiMbMOMC3fr7 OxrPvZNleq9/SMnWLeu6m7KMZwTjx5dOXNgLJqLKC5ImdvisQdnjKXB0eNTzaHzdvZDU Hmtjkf/E4DLLnzrNRiigrzNQftxb4MyRY/hn1Y4Fs+WzLJagnhTIMZLFHmohAyTa/ZyT l/IQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=UReJ/d8XOUJAR7QWS/3VOpB8r2M1WLYHMJENgOtgPk4=; b=xgS/WaKrpc0w0J4ZajnlXcRAjJQh4Rjcpb2Sfe9rjzQmlULi+8XXEGqexm+uoMit3H jkMwH9MPvTUsG+6dXptWZFDijwo7OSfL7hSt1Sa3FIK9XzA2RiojB1psT4sNmK+BThFn P09jwQtkl/yXsLVrJzvsDl2/bJlmd+Myq7BlKBFMcbD9TL3EYNGWBo2Z80KHV/MzHmXk Blom0wAWMZtqx8d+108yb4CgJvXHfhNJ+PqhrY8b1IU1oQTDHjNuZKp9/dy29UM++Fdm YGVx2eUegFSxBplecZvMei5ZF7FNaE6V/RVXq9wy7z/go9cB40KO6z64FNNdr6mYa++5 ejBQ== X-Gm-Message-State: AOAM533B58X0e4xnqQlp2jeOp4Jrbzbayo8kmwEHZ5olsd3SA7Z/zOSd pd40QSf8V0txLb8B6CQ4mVp/SHIjfFRH/a/I X-Google-Smtp-Source: ABdhPJzNzal4XG62vkRzaBiiE+IyafevSiu+NCDrL1E0ycH7KvEWBWOFCR+UntZYHzpekuGyWOv+QA== X-Received: by 2002:a05:6a00:4385:b0:510:4422:aa3a with SMTP id bt5-20020a056a00438500b005104422aa3amr17019608pfb.16.1652116099902; Mon, 09 May 2022 10:08:19 -0700 (PDT) Received: from smtpclient.apple ([2600:1700:5430:10b1:b128:189:8c64:6e]) by smtp.gmail.com with ESMTPSA id 30-20020a17090a19de00b001dc8eca6536sm8995651pjj.4.2022.05.09.10.08.18 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Mon, 09 May 2022 10:08:19 -0700 (PDT) From: Christopher Bowman Message-Id: <8469BF19-B39E-42B1-AC52-35F38CAD1B5F@chrisbowman.com> Content-Type: multipart/alternative; boundary="Apple-Mail=_05C49D6A-A32E-4D05-8355-B0F5896A04C7" 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 (Mac OS X Mail 15.0 \(3693.60.0.1.1\)) Subject: Re: Recent u-boot port change Date: Mon, 9 May 2022 10:08:17 -0700 In-Reply-To: <20220509122939.4e8a9d48@mp2.dino.sk> Cc: freebsd-ports@freebsd.org To: Milan Obuch References: <83B78F74-9C4D-4727-AC71-E21ED5E7E1AA@chrisbowman.com> <20220509122939.4e8a9d48@mp2.dino.sk> X-Mailer: Apple Mail (2.3693.60.0.1.1) X-Rspamd-Queue-Id: 4KxngT1GBbz4n8R X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=chrisbowman-com.20210112.gappssmtp.com header.s=20210112 header.b=Zmju5VdL; dmarc=none; spf=none (mx1.freebsd.org: domain of crb@chrisbowman.com has no SPF policy when checking 2607:f8b0:4864:20::533) smtp.mailfrom=crb@chrisbowman.com X-Spamd-Result: default: False [-2.22 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; ARC_NA(0.00)[]; R_DKIM_ALLOW(-0.20)[chrisbowman-com.20210112.gappssmtp.com:s=20210112]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; MV_CASE(0.50)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-ports@freebsd.org]; DMARC_NA(0.00)[chrisbowman.com]; RCVD_COUNT_THREE(0.00)[3]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[chrisbowman-com.20210112.gappssmtp.com:+]; RCPT_COUNT_TWO(0.00)[2]; RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::533:from]; NEURAL_HAM_SHORT(-0.42)[-0.421]; MLMMJ_DEST(0.00)[freebsd-ports]; R_SPF_NA(0.00)[no SPF record]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; RCVD_TLS_ALL(0.00)[]; MID_RHS_MATCH_FROM(0.00)[] X-ThisMailContainsUnwantedMimeParts: N --Apple-Mail=_05C49D6A-A32E-4D05-8355-B0F5896A04C7 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 Hi! I am building a slave port of my own creation. but I would have expected = the master port to take care of this patching. I=E2=80=99ve had that = suggestion that e2fsprogs should be providing the uuid stuff but I=E2=80=99= m not seeing that get called here. Maybe something about my setup. Thanks for the hint on the u-boot mailing list. Regards, Christopher=20 > On May 9, 2022, at 3:29 AM, Milan Obuch wrote: >=20 > On Sun, 8 May 2022 15:29:08 -0700 > Christopher Bowman > = wrote: >=20 >> First, I truly do appreciate all the effort every one puts into >> FreeBSD. Apologies if I=E2=80=99m not quite following protocol here: >>=20 >> 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. >=20 > Hi, >=20 > 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. >=20 >> 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 other >> 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. >>=20 >=20 > 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... >=20 > 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... >=20 > Regards, > Milan --Apple-Mail=_05C49D6A-A32E-4D05-8355-B0F5896A04C7 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8 Hi!
I am building a slave port of my own = creation. but I would have expected the master port to take care of this = patching.  I=E2=80=99ve had that suggestion that e2fsprogs should = be providing the uuid stuff but I=E2=80=99m not seeing that get called = here.  Maybe something about my setup.

Thanks for the hint on the u-boot = mailing list.
Regards,
Christopher 

On May = 9, 2022, at 3:29 AM, Milan Obuch <freebsd-ports@dino.sk> wrote:

On Sun, 8 May 2022 15:29:08 -0700
Christopher Bowman <crb@chrisbowman.com> 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:

tools/mkeficapsule.c:18:10: fatal error: 'uuid/uuid.h' file = not found
#include <uuid/uuid.h>
      ^~~~~~~~~~~~~
1 error generated.

There is a = uuid.h in /usr/include so I patched this.

Then I come across:

tools/mkeficapsule.c:21:10: fatal error: 'gnutls/gnutls.h' = file not
found #include <gnutls/gnutls.h>
      ^~~~~~~~~~~~~~~~~
1 error generated.

Ok so I = install gnutls and patch the make file to also search
/usr/local/include where that gets installed.  Next I = get:

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.

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:

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.

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 = other
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

= --Apple-Mail=_05C49D6A-A32E-4D05-8355-B0F5896A04C7--