Date: Mon, 6 May 2019 04:16:42 +0000 From: James Shuriff <james@opentech.cc> To: bob prohaska <fbsd@www.zefox.net> Cc: "freebsd-arm@freebsd.org" <freebsd-arm@freebsd.org> Subject: RE: Compiling u-boot-rpi3 on an rpi3 Message-ID: <BN7PR06MB5187D5B8BCFD22D54FE30D30AA300@BN7PR06MB5187.namprd06.prod.outlook.com> In-Reply-To: <20190506035435.GA40846@www.zefox.net> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
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> 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 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> > 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 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 <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 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>). > > > ________________________________ > 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>). > ________________________________ 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>).
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?BN7PR06MB5187D5B8BCFD22D54FE30D30AA300>