Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 6 May 2019 13:39:43 +0200 (CEST)
From:      Ronald Klop <ronald-lists@klop.ws>
To:        James Shuriff <james@opentech.cc>
Cc:        bob prohaska <fbsd@www.zefox.net>, "freebsd-arm@freebsd.org" <freebsd-arm@freebsd.org>
Subject:   RE: Compiling u-boot-rpi3 on an rpi3
Message-ID:  <490066464.19.1557142783764@localhost>
In-Reply-To: <BN7PR06MB5187D5B8BCFD22D54FE30D30AA300@BN7PR06MB5187.namprd06.prod.outlook.com>
References:  <20190506020115.GA40421@www.zefox.net> <BN7PR06MB51875E5B873CC610CF475843AA300@BN7PR06MB5187.namprd06.prod.outlook.com> <20190506021613.GB40421@www.zefox.net> <BN7PR06MB51879F0EA5A24C5E7FB32A11AA300@BN7PR06MB5187.namprd06.prod.outlook.com> <20190506035435.GA40846@www.zefox.net> <BN7PR06MB5187D5B8BCFD22D54FE30D30AA300@BN7PR06MB5187.namprd06.prod.outlook.com>

next in thread | previous in thread | raw e-mail | index | archive | help
Just as a data point.

The last build of the pkg system was on the 1st of May. It was successful.
http://thunderx1.nyi.freebsd.org/data/head-arm64-default/p499706_s346582/logs/u-boot-rpi3-2019.04.log

Regards,
Ronald.
 
Van: James Shuriff <james@opentech.cc>
Datum: maandag, 6 mei 2019 06:16
Aan: bob prohaska <fbsd@www.zefox.net>
CC: "freebsd-arm@freebsd.org" <freebsd-arm@freebsd.org>
Onderwerp: RE: Compiling u-boot-rpi3 on an rpi3
> 
> I wouldn't say that's obvious. You could have been building a specific stable, release, or releng branch. I checked and r347055 is a head revision. I am also running 13.0-CURRENT (r347167) on rpi3b. I can at least confirm if I'm having the same issue with the port once my system is free. I use the repo because I like to tune U-Boot a bit finer than the port does. I'm using v2019.07-rc1 from the repo. The port uses v2019.04 so it's up to date at least.
> 
> Do you use your rpi3b as the host system for building src?
> 
> - James Shuriff
> 
> -----Original Message-----
> From: bob prohaska <fbsd@www.zefox.net>
> Sent: Sunday, May 5, 2019 11:55 PM
> To: James Shuriff <james@opentech.cc>
> Cc: bob prohaska <fbsd@www.zefox.net>
> Subject: Re: Compiling u-boot-rpi3 on an rpi3
> 
> On Mon, May 06, 2019 at 03:01:07AM +0000, James Shuriff wrote:
> > Bob,
> >
> > Which version of FreeBSD are you running?
> 
> Sorry, I thought it was obvious 8-)
> 
> Current. On an rpi3b (no wifi)
> 
> > What is the output of `uname -p`?
> aarch64
> 
> > The Das U-Boot tools (where your issue is) are compiled using the host
> > system's toolchain.
> >
> Mostly I'm trying to raise a flag to the ports folks that u-boot no longer builds. It did in the not-hugely-distant past. My initial hope was that I had some sort of misconfiguration, but so far nobody's pointed it out.
> 
> I realize that not many people are trying to self-host FreeBSD on any version of the Pi2 or Pi3, but it's doable and useful in low-throughput hobby applications like mine.
> 
> Many thanks for your attention!
> 
> bob prohaska
> 
> 
> 
> > - James Shuriff
> > Managing Member
> > OpenTech.cc LLC
> > Direct #: +1 631 333 7437
> > Main #: +1 631 333 7260
> >
> > -----Original Message-----
> > From: bob prohaska <fbsd@www.zefox.net>
> > Sent: Sunday, May 5, 2019 10:16 PM
> > To: James Shuriff <james@opentech.cc>
> > Cc: bob prohaska <fbsd@www.zefox.net>
> > Subject: Re: Compiling u-boot-rpi3 on an rpi3
> >
> > Hi James,
> >
> > That seems rather drastic. I'd like to stay within the ports system since this isn't a "must do" situation. At one time building u-boot on an rpi worked, though that was a while ago.
> >
> > Thanks for writing!
> >
> > bob prohaska
> >
> > On Mon, May 06, 2019 at 02:08:34AM +0000, James Shuriff wrote:
> > > Try building it directly from the repo. This is how I build for rpi3:
> > >
> > > Clone the git repo https://github.com/u-boot/u-boot
> > >
> > > In configs/rpi_3_defconfig:
> > > * Change CONFIG_OF_EMBED=y to CONFIG_OF_EMBED =n
> > > * Add CONFIG_OF_BOARD=y
> > > * Change CONFIG_ENV_FAT_DEVICE_AND_PART="0:1" to CONFIG_ENV_FAT_DEVICE_AND_PART="1:1"
> > >
> > > Make sure you have the aarch64-none-elf-gcc package.
> > >
> > > Use these commands to build:
> > > gmake CROSS_COMPILE=aarch64-none-elf- rpi_3_defconfig gmake
> > > CROSS_COMPILE=aarch64-none-elf- u-boot.bin
> > >
> > > - James Shuriff
> > >
> > > -----Original Message-----
> > > From: owner-freebsd-arm@freebsd.org <owner-freebsd-arm@freebsd.org>
> > > On Behalf Of bob prohaska
> > > Sent: Sunday, May 5, 2019 10:01 PM
> > > To: freebsd-arm@freebsd.org; freebsd-ports@freebsd.org
> > > Subject: Compiling u-boot-rpi3 on an rpi3
> > >
> > > With FreeBSD at r347055 and ports at 500862 attempts to compile
> > > sysutils/u-boot-rpi3 stop with a string of errors starting with
> > > ld: error: undefined symbol: EVP_MD_CTX_new
> > > >>> referenced by mxsimage.c
> > > >>>               tools/mxsimage.o:(mxsimage_generate)
> > >
> > > ld: error: undefined symbol: EVP_MD_CTX_free
> > > >>> referenced by mxsimage.c
> > > >>>               tools/mxsimage.o:(mxsimage_generate)
> > >
> > > ld: error: undefined symbol: EVP_MD_CTX_new
> > > >>> referenced by mxsimage.c
> > > >>>               tools/mxsimage.o:(mxsimage_generate)
> > >
> > > ld: error: undefined symbol: EVP_CIPHER_CTX_reset
> > > >>> referenced by mxsimage.c
> > > >>>               tools/mxsimage.o:(mxsimage_generate)
> > >
> > > Is there a fix or workaround?
> > >
> > > Thanks for reading,
> > >
> > > bob prohaska
> > > _______________________________________________
> > > freebsd-arm@freebsd.org mailing list
> > > https://lists.freebsd.org/mailman/listinfo/freebsd-arm
> > > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org"
> > > ________________________________
> > >  DISCLAIMER: This message and any attachments are intended solely for the use of the recipient and may contain confidential information. If you have received this message in error please delete it and promptly notify the sender, James Shuriff (james@opentech.cc<mailto:james@opentech.cc>).
> > >
> > ________________________________
> >  DISCLAIMER: This message and any attachments are intended solely for the use of the recipient and may contain confidential information. If you have received this message in error please delete it and promptly notify the sender, James Shuriff (james@opentech.cc<mailto:james@opentech.cc>).
> >
> ________________________________
>  DISCLAIMER: This message and any attachments are intended solely for the use of the recipient and may contain confidential information. If you have received this message in error please delete it and promptly notify the sender, James Shuriff (james@opentech.cc<mailto:james@opentech.cc>).
> _______________________________________________
> freebsd-arm@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-arm
> To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org"
> 
> 
> 
From owner-freebsd-arm@freebsd.org  Mon May  6 14:27:22 2019
Return-Path: <owner-freebsd-arm@freebsd.org>
Delivered-To: freebsd-arm@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id AB3D7158C583
 for <freebsd-arm@mailman.ysv.freebsd.org>;
 Mon,  6 May 2019 14:27:22 +0000 (UTC)
 (envelope-from james@opentech.cc)
Received: from NAM02-BL2-obe.outbound.protection.outlook.com
 (mail-eopbgr750051.outbound.protection.outlook.com [40.107.75.51])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits))
 (Client CN "mail.protection.outlook.com",
 Issuer "GlobalSign Organization Validation CA - SHA256 - G3" (verified OK))
 by mx1.freebsd.org (Postfix) with ESMTPS id 80A8F7205A
 for <freebsd-arm@freebsd.org>; Mon,  6 May 2019 14:27:21 +0000 (UTC)
 (envelope-from james@opentech.cc)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=opentech.cc;
 s=selector1;
 h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck;
 bh=IZAezwHuSWEXhHVB13XQN5rxT4av/nDPqRZs77BXTNk=;
 b=d2iUTyURYOs1ymOenGnBxvbwz1yjRMqhj/ZMshgYlDEmt7mV54COgo72fm6AID2RW4NaaAG0AKmMYwy0olzGila0OaTkyhDUPyTY1yEQwupgdsBbFOmAWKgy6qyK8THbFiDHKAx32o/Iv5tQvlnLPVPU3+Lp2LvF+Ir2TzX1TgY=
Received: from BN7PR06MB5187.namprd06.prod.outlook.com (20.176.29.18) by
 BN7PR06MB4004.namprd06.prod.outlook.com (52.132.220.147) with Microsoft SMTP
 Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id
 15.20.1856.11; Mon, 6 May 2019 14:27:19 +0000
Received: from BN7PR06MB5187.namprd06.prod.outlook.com
 ([fe80::3934:1ed8:5f2e:1d6f]) by BN7PR06MB5187.namprd06.prod.outlook.com
 ([fe80::3934:1ed8:5f2e:1d6f%5]) with mapi id 15.20.1856.012; Mon, 6 May 2019
 14:27:19 +0000
From: James Shuriff <james@opentech.cc>
To: Ronald Klop <ronald-lists@klop.ws>
CC: bob prohaska <fbsd@www.zefox.net>, "freebsd-arm@freebsd.org"
 <freebsd-arm@freebsd.org>
Subject: RE: Compiling u-boot-rpi3 on an rpi3
Thread-Topic: Compiling u-boot-rpi3 on an rpi3
Thread-Index: AQHVA6/hKExcD8AWFEuc9fg9iSbTAKZdWLJAgAADSICAAAwtUIAAD0+AgAACV/CAAH+egIAALbKQ
Date: Mon, 6 May 2019 14:27:19 +0000
Message-ID: <BN7PR06MB51872AFFADC205CFB8870BE7AA300@BN7PR06MB5187.namprd06.prod.outlook.com>
References: <20190506020115.GA40421@www.zefox.net>
 <BN7PR06MB51875E5B873CC610CF475843AA300@BN7PR06MB5187.namprd06.prod.outlook.com>
 <20190506021613.GB40421@www.zefox.net>
 <BN7PR06MB51879F0EA5A24C5E7FB32A11AA300@BN7PR06MB5187.namprd06.prod.outlook.com>
 <20190506035435.GA40846@www.zefox.net>
 <BN7PR06MB5187D5B8BCFD22D54FE30D30AA300@BN7PR06MB5187.namprd06.prod.outlook.com>
 <490066464.19.1557142783764@localhost>
In-Reply-To: <490066464.19.1557142783764@localhost>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [71.251.5.193]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 6613b161-4c03-4758-593d-08d6d22ef226
x-microsoft-antispam: BCL:0; PCL:0;
 RULEID:(2390118)(7020095)(4652040)(7021145)(8989299)(4534185)(7022145)(4603075)(4627221)(201702281549075)(8990200)(7048125)(7024125)(7027125)(7023125)(5600141)(711020)(4605104)(2017052603328)(7193020);
 SRVR:BN7PR06MB4004; 
x-ms-traffictypediagnostic: BN7PR06MB4004:
x-ms-exchange-purlcount: 6
x-microsoft-antispam-prvs: <BN7PR06MB40044FBD99B26D47EF25328BAA300@BN7PR06MB4004.namprd06.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:3383;
x-forefront-prvs: 0029F17A3F
x-forefront-antispam-report: SFV:NSPM;
 SFS:(10009020)(376002)(136003)(396003)(346002)(39830400003)(366004)(13464003)(189003)(38564003)(199004)(6916009)(8936002)(74482002)(6436002)(74316002)(99286004)(14444005)(5024004)(256004)(316002)(53386004)(229853002)(6246003)(33656002)(54906003)(66476007)(66946007)(66556008)(64756008)(66446008)(73956011)(76116006)(5660300002)(71200400001)(2906002)(55016002)(53936002)(7736002)(66066001)(68736007)(606006)(9686003)(236005)(8676002)(6306002)(54896002)(81166006)(81156014)(25786009)(76176011)(446003)(508600001)(476003)(26005)(53546011)(6506007)(11346002)(966005)(186003)(71190400001)(790700001)(7696005)(52536014)(3846002)(102836004)(4326008)(6116002)(86362001)(14454004)(486006);
 DIR:OUT; SFP:1101; SCL:1; SRVR:BN7PR06MB4004;
 H:BN7PR06MB5187.namprd06.prod.outlook.com; FPR:; SPF:None; LANG:en;
 PTR:InfoNoRecords; MX:1; A:1; 
received-spf: None (protection.outlook.com: opentech.cc does not designate
 permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: EGa2p4bU/i+mOM7ljN+nXgecv4u7SI/IS5b5rnFwVI56srd713N2Kty+CJlUFviJBwHzNq8+3990ZnywgXWWmRTO8bZwKTiavLLtyo2B3wd2/njZTks6kU5EjwiGTD4L0DKsnW6EovBwCgdSOIaE0QODiqDtBKGpHXKmSxUuahjmqVQnLdIlhhjS1Q8PWQ61A8mDLkXCkneRQvx0XZLwfxLL/EJAfYySNUPOC1sAE+FsoJsuD1aR0A8A3Jl2Wi1Xiw1Pl7uLn7LFM4GPMG7yYayc3tNc8AsNNttfjXY1dNWddhxt1d4LugtL7i8raXiagxFHK85AfimiHlAAD11kNBzhfshq3iJDPsTOU/oGxvJP1UyNDnBbsydaU9TiCPFQ1JrxhuqxRPgQehtPX6cZmORd93FVOjrJao80d0ilyys=
MIME-Version: 1.0
X-OriginatorOrg: opentech.cc
X-MS-Exchange-CrossTenant-Network-Message-Id: 6613b161-4c03-4758-593d-08d6d22ef226
X-MS-Exchange-CrossTenant-originalarrivaltime: 06 May 2019 14:27:19.1762 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5c5dd5ac-929c-48f6-a3f4-c0c8602c24af
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN7PR06MB4004
X-Rspamd-Queue-Id: 80A8F7205A
X-Spamd-Bar: --
Authentication-Results: mx1.freebsd.org;
 dkim=pass header.d=opentech.cc header.s=selector1 header.b=d2iUTyUR;
 spf=pass (mx1.freebsd.org: domain of james@opentech.cc designates 40.107.75.51
 as permitted sender) smtp.mailfrom=james@opentech.cc
X-Spamd-Result: default: False [-2.15 / 15.00]; ARC_NA(0.00)[];
 TO_DN_EQ_ADDR_SOME(0.00)[];
 R_DKIM_ALLOW(-0.20)[opentech.cc:s=selector1]; HAS_XOIP(0.00)[];
 FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3];
 R_SPF_ALLOW(-0.20)[+ip4:40.107.0.0/16];
 NEURAL_HAM_LONG(-0.99)[-0.990,0];
 MIME_GOOD(-0.10)[multipart/alternative,text/plain];
 DMARC_NA(0.00)[opentech.cc];
 NEURAL_HAM_MEDIUM(-0.94)[-0.944,0]; TO_DN_SOME(0.00)[];
 URI_COUNT_ODD(1.00)[17]; RCVD_COUNT_THREE(0.00)[3];
 TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[opentech.cc:+];
 MX_GOOD(-0.01)[cached: opentech-cc.mail.protection.outlook.com];
 RCVD_IN_DNSWL_NONE(0.00)[51.75.107.40.list.dnswl.org : 127.0.3.0];
 NEURAL_HAM_SHORT(-0.70)[-0.703,0]; FROM_EQ_ENVFROM(0.00)[];
 MIME_TRACE(0.00)[0:+,1:+]; RCVD_TLS_LAST(0.00)[]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
X-Content-Filtered-By: Mailman/MimeDel 2.1.29
X-BeenThere: freebsd-arm@freebsd.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Porting FreeBSD to ARM processors." <freebsd-arm.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-arm>,
 <mailto:freebsd-arm-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-arm/>;
List-Post: <mailto:freebsd-arm@freebsd.org>
List-Help: <mailto:freebsd-arm-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-arm>,
 <mailto:freebsd-arm-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 06 May 2019 14:27:23 -0000

I was able to build the port from aarch64.

I'm a bit concerned that aarch64-none-elf-gcc has no maintainer. It's two y=
ears old. The port is GPLv3 so that's not the reason it's using an old vers=
ion.

- James Shuriff

From: Ronald Klop <ronald-lists@klop.ws>
Sent: Monday, May 6, 2019 7:40 AM
To: James Shuriff <james@opentech.cc>
Cc: bob prohaska <fbsd@www.zefox.net>; freebsd-arm@freebsd.org
Subject: RE: Compiling u-boot-rpi3 on an rpi3

Just as a data point.

The last build of the pkg system was on the 1st of May. It was successful.
http://thunderx1.nyi.freebsd.org/data/head-arm64-default/p499706_s346582/lo=
gs/u-boot-rpi3-2019.04.log

Regards,
Ronald.


Van: James Shuriff <james@opentech.cc<mailto:james@opentech.cc>>
Datum: maandag, 6 mei 2019 06:16
Aan: bob prohaska <fbsd@www.zefox.net<mailto:fbsd@www.zefox.net>>
CC: "freebsd-arm@freebsd.org<mailto:freebsd-arm@freebsd.org>" <freebsd-arm@=
freebsd.org<mailto:freebsd-arm@freebsd.org>>
Onderwerp: RE: Compiling u-boot-rpi3 on an rpi3
I wouldn't say that's obvious. You could have been building a specific stab=
le, release, or releng branch. I checked and r347055 is a head revision. I =
am also running 13.0-CURRENT (r347167) on rpi3b. I can at least confirm if =
I'm having the same issue with the port once my system is free. I use the r=
epo because I like to tune U-Boot a bit finer than the port does. I'm using=
 v2019.07-rc1 from the repo. The port uses v2019.04 so it's up to date at l=
east.

Do you use your rpi3b as the host system for building src?

- James Shuriff

-----Original Message-----
From: bob prohaska <fbsd@www.zefox.net<http://www.zefox.net>>;
Sent: Sunday, May 5, 2019 11:55 PM
To: James Shuriff <james@opentech.cc<mailto:james@opentech.cc>>
Cc: bob prohaska <fbsd@www.zefox.net<http://www.zefox.net>>;
Subject: Re: Compiling u-boot-rpi3 on an rpi3

On Mon, May 06, 2019 at 03:01:07AM +0000, James Shuriff wrote:
> Bob,
>
> Which version of FreeBSD are you running?

Sorry, I thought it was obvious 8-)

Current. On an rpi3b (no wifi)

> What is the output of `uname -p`?
aarch64

> The Das U-Boot tools (where your issue is) are compiled using the host
> system's toolchain.
>
Mostly I'm trying to raise a flag to the ports folks that u-boot no longer =
builds. It did in the not-hugely-distant past. My initial hope was that I h=
ad some sort of misconfiguration, but so far nobody's pointed it out.

I realize that not many people are trying to self-host FreeBSD on any versi=
on of the Pi2 or Pi3, but it's doable and useful in low-throughput hobby ap=
plications like mine.

Many thanks for your attention!

bob prohaska



> - James Shuriff
> Managing Member
> OpenTech.cc LLC
> Direct #: +1 631 333 7437
> Main #: +1 631 333 7260
>
> -----Original Message-----
> From: bob prohaska <fbsd@www.zefox.net<http://www.zefox.net>>;
> Sent: Sunday, May 5, 2019 10:16 PM
> To: James Shuriff <james@opentech.cc<mailto:james@opentech.cc>>
> Cc: bob prohaska <fbsd@www.zefox.net<http://www.zefox.net>>;
> Subject: Re: Compiling u-boot-rpi3 on an rpi3
>
> Hi James,
>
> That seems rather drastic. I'd like to stay within the ports system since=
 this isn't a "must do" situation. At one time building u-boot on an rpi wo=
rked, though that was a while ago.
>
> Thanks for writing!
>
> bob prohaska
>
> On Mon, May 06, 2019 at 02:08:34AM +0000, James Shuriff wrote:
> > Try building it directly from the repo. This is how I build for rpi3:
> >
> > Clone the git repo https://github.com/u-boot/u-boot
> >
> > In configs/rpi_3_defconfig:
> > * Change CONFIG_OF_EMBED=3Dy to CONFIG_OF_EMBED =3Dn
> > * Add CONFIG_OF_BOARD=3Dy
> > * Change CONFIG_ENV_FAT_DEVICE_AND_PART=3D"0:1" to CONFIG_ENV_FAT_DEVIC=
E_AND_PART=3D"1:1"
> >
> > Make sure you have the aarch64-none-elf-gcc package.
> >
> > Use these commands to build:
> > gmake CROSS_COMPILE=3Daarch64-none-elf- rpi_3_defconfig gmake
> > CROSS_COMPILE=3Daarch64-none-elf- u-boot.bin
> >
> > - James Shuriff
> >
> > -----Original Message-----
> > From: owner-freebsd-arm@freebsd.org<mailto:owner-freebsd-arm@freebsd.or=
g> <owner-freebsd-arm@freebsd.org<mailto:owner-freebsd-arm@freebsd.org>>
> > On Behalf Of bob prohaska
> > Sent: Sunday, May 5, 2019 10:01 PM
> > To: freebsd-arm@freebsd.org<mailto:freebsd-arm@freebsd.org>; freebsd-po=
rts@freebsd.org<mailto:freebsd-ports@freebsd.org>
> > Subject: Compiling u-boot-rpi3 on an rpi3
> >
> > With FreeBSD at r347055 and ports at 500862 attempts to compile
> > sysutils/u-boot-rpi3 stop with a string of errors starting with
> > ld: error: undefined symbol: EVP_MD_CTX_new
> > >>> referenced by mxsimage.c
> > >>>               tools/mxsimage.o:(mxsimage_generate)
> >
> > ld: error: undefined symbol: EVP_MD_CTX_free
> > >>> referenced by mxsimage.c
> > >>>               tools/mxsimage.o:(mxsimage_generate)
> >
> > ld: error: undefined symbol: EVP_MD_CTX_new
> > >>> referenced by mxsimage.c
> > >>>               tools/mxsimage.o:(mxsimage_generate)
> >
> > ld: error: undefined symbol: EVP_CIPHER_CTX_reset
> > >>> referenced by mxsimage.c
> > >>>               tools/mxsimage.o:(mxsimage_generate)
> >
> > Is there a fix or workaround?
> >
> > Thanks for reading,
> >
> > bob prohaska
> > _______________________________________________
> > freebsd-arm@freebsd.org<mailto:freebsd-arm@freebsd.org> mailing list
> > https://lists.freebsd.org/mailman/listinfo/freebsd-arm
> > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org<m=
ailto:freebsd-arm-unsubscribe@freebsd.org>"
> > ________________________________
> >  DISCLAIMER: This message and any attachments are intended solely for t=
he use of the recipient and may contain confidential information. If you ha=
ve received this message in error please delete it and promptly notify the =
sender, James Shuriff (james@opentech.cc<mailto:james@opentech.cc<mailto:ja=
mes@opentech.cc%3cmailto:james@opentech.cc>>).
> >
> ________________________________
>  DISCLAIMER: This message and any attachments are intended solely for the=
 use of the recipient and may contain confidential information. If you have=
 received this message in error please delete it and promptly notify the se=
nder, James Shuriff (james@opentech.cc<mailto:james@opentech.cc<mailto:jame=
s@opentech.cc%3cmailto:james@opentech.cc>>).
>
________________________________
 DISCLAIMER: This message and any attachments are intended solely for the u=
se of the recipient and may contain confidential information. If you have r=
eceived this message in error please delete it and promptly notify the send=
er, James Shuriff (james@opentech.cc<mailto:james@opentech.cc<mailto:james@=
opentech.cc%3cmailto:james@opentech.cc>>).
_______________________________________________
freebsd-arm@freebsd.org<mailto:freebsd-arm@freebsd.org> mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-arm
To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org<mailt=
o:freebsd-arm-unsubscribe@freebsd.org>"
________________________________
________________________________
DISCLAIMER: This message and any attachments are intended solely for the us=
e of the recipient and may contain confidential information. If you have re=
ceived this message in error please delete it and promptly notify the sende=
r, James Shuriff (james@opentech.cc<mailto:james@opentech.cc>).



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?490066464.19.1557142783764>