Compiling u-boot-rpi3 on an rpi3

[James Shuriff]

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 at www.zefox.net>
Sent: Sunday, May 5, 2019 11:55 PM
To: James Shuriff <james at opentech.cc>
Cc: bob prohaska <fbsd at 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 at www.zefox.net>
> Sent: Sunday, May 5, 2019 10:16 PM
> To: James Shuriff <james at opentech.cc>
> Cc: bob prohaska <fbsd at 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 at freebsd.org <owner-freebsd-arm at freebsd.org>
> > On Behalf Of bob prohaska
> > Sent: Sunday, May 5, 2019 10:01 PM
> > To: freebsd-arm at freebsd.org; freebsd-ports at 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 at freebsd.org mailing list
> > https://lists.freebsd.org/mailman/listinfo/freebsd-arm
> > To unsubscribe, send any mail to "freebsd-arm-unsubscribe at 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 at opentech.cc<mailto:james at 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 at opentech.cc<mailto:james at 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 at opentech.cc<mailto:james at opentech.cc>).