buildroot | Buildroot with BeagleBoard support

Unfortunately I can't provide you with a fix, but I've found a workaround for that exact same problem (company-hosted bitbucket resulting in exact same error). I also don't know exactly why the problem occurs, but my best guess would be that the libressl library shipped with Monterey has some sort of problem with specific (?TLSv1.3) certs. This guess is because the brew-installed openssl v1.1 and v3 don't throw that error when executed with /opt/homebrew/opt/openssl/bin/openssl s_client -connect ...:443

To get around that error, I've built git from source built against different openssl and curl implementations:

1. install autoconf, openssl and curl with brew (I think you can select the openssl lib you like, i.e. v1.1 or v3, I chose v3)
2. clone git version you like, i.e. git clone --branch v2.33.1 https://github.com/git/git.git
3. cd git
4. make configure (that is why autoconf is needed)
5. execute LDFLAGS="-L/opt/homebrew/opt/openssl@3/lib -L/opt/homebrew/opt/curl/lib" CPPFLAGS="-I/opt/homebrew/opt/openssl@3/include -I/opt/homebrew/opt/curl/include" ./configure --prefix=$HOME/git (here LDFLAGS and CPPFLAGS include the libs git will be built against, the right flags are emitted by brew on install success of curl and openssl; --prefix is the install directory of git, defaults to /usr/local but can be changed)
6. make install
7. ensure to add the install directory's subfolder /bin to the front of your $PATH to "override" the default git shipped by Monterey
8. restart terminal
9. check that git version shows the new version

This should help for now, but as I already said, this is only a workaround, hopefully Apple fixes their libressl fork ASAP.

Obviously there are differences in the 2 boards. Your build would succeed but wont run on pocket beagle because it is not meant to run on it.

To build BSP for pocket beagle follow below steps,

1. In Target options – Change Target architecture to ARM (little endian) – Change Target architecture variant to Cortex-A8

2. In Build options, set global patch directories to board/e-ale/pocketbeagle/patches/. This will allow you to put patches for Linux, U-Boot other packages in subdirectories of board/e-ale/pocketbeagle/patches/.

3. Toolchain - you can use external or internal.

4. In Kernel – Enable the Linux kernel, obviously! – Choose Custom version as the Kernel version – Choose 4.14.24 as Kernel version – Patches will already be applied to the kernel, thanks to us having defined a global patch directory above. – Choose omap2plus as the Defconfig name – We’ll need the Device Tree of the PocketBeagle, so enable Build a Device Tree Blob (DTB) – And use am335x-pocketbeagle as the Device Tree Source file names

5. Target packages - as per your requirement.

6. In Filesystem images, enable ext2/3/4 root filesystem, select the ext4 variant.

7. In Bootloaders, enable U-Boot, and in U-Boot: – Switch the Build system option to Kconfig: use U-Boot – Use a Custom version of value 2018.01. – Use am335x_pocketbeagle as the Board defconfig

As you have noticed, in the configuration, you have referenced board/e-ale/pocketbeagle/ patches as a directory containing patches for various packages. We now need to add the U-Boot and Linux patches that add support for the PocketBeagle, which are not upstream. Use patches, and just copy it to board/e-ale/pocketbeagle so that you get the following directory hierarchy:

Then build the BSP and run on your device.

source

After more research, it turns out this was an issue with the configuration path assigned within the Buildroot config. It was referring to the RPi3 configuration, which required a different kernel and GCC version. The fix involved the following:

By default, "Find in project" ignores files that are ignored by your Version Control System. This settin can be disabled in the Core Settings.

Since this is not ideal for most workflows, you might want to look at third-party packages that such as atom-ignore or similar packages.

There is no need to allocate memory for this task: pass a pointer to a local array along with its size and use strlcat properly:

Got it. Because I use grayscale images. So I have to add color_mode keyword argument in both flow_from_dataframe() and set it equal to "grayscale"

Patches can simply be applied with the 'patch' tool, but you probably have Buildroot in a git repo, so you can add it as a git commit with git am or directly cherry pick the commit with git cherry-pick . Do notice that genimage 15 does bring a few non-backwards compatible changes. If the above sounds complicated to you, then consider just moving to the 2022.02 release which includes it. The final 2022.02 release will be out in a few days, but you can already use 2022.02-rc3.

As mentioned in the comment to my question

That means that the option is a required dependency of some other option that you have selected. I think that if you press 'H' with the cursor on the option, it will tell you what that other option is.

H shows all the info you need about a package and showed me which package depends on cups. In my case, since I manually selected openjdk, cups was autoselected (and could not be deselected) because openjdk depends on cups.

I think you're taking this at the wrong level. I would rather recommend to look at what tool_install_dependencies and tool_build do in your tools_setup.sh script, and replicate that in the Buildroot package.

Based on its name, the tool_install_dependencies is particularly scary, as you definitely don't want a Buildroot package to install dependencies by itself.

Other than that, to directly answer your question: like in all Makefiles, each line of your rule is executed in a separate shell, so your "source tool_setup.sh" runs in a separate shell from "tool_install_dependencies", which explains why it doesn't work. If you want them to run in the same shell, do "source tool_setup.sh; tool_install_dependencies; tool_build".

But again, this smells like a very, very, very, very bad thing to do.