Hi there,
Sounds like it’s too Big? The emmc and rootfs is paking it and it’s a NO go.
Try building the basic thing first . does it build?
let us know.
HTH
GL 
PJ 
I asked AI…
Below are some common reasons and potential fixes when Buildroot (or a similar Yocto/embedded Linux build system) fails with an error like:
less
Copy code
config.status: executing libtool commands
make[2]: *** [Makefile:88: _all] Error 2
make[2]: Leaving directory ‘/home/jmc/reCamera-OS/output/sg2002_recamera_emmc/buildroot-2021.05’
make[1]: *** [Makefile:574: br-rootfs-pack] Error 2
make[1]: Leaving directory ‘/home/jmc/reCamera-OS/output/sg2002_recamera_emmc/build’
make: *** [Makefile:18: sg2002_recamera_emmc] Error 1
1. Install All Required Build Dependencies
On a fresh Ubuntu install, you may be missing some packages. Even if you installed a few, you might need additional dev libraries. Make sure you have:
- Basic build tools
bash
Copy code
sudo apt-get update
sudo apt-get install build-essential git
- Autoconf / Automake / Libtool
bash
Copy code
sudo apt-get install autoconf automake libtool
-
Other build libs (commonly needed for Buildroot / Yocto):
bash
Copy code
sudo apt-get install bison flex texinfo gawk libncurses5-dev \
libssl-dev cpio unzip rsync python3 xz-utils zlib1g-dev
- Ubuntu 22.04 and later sometimes rename or reorganize packages, so adapt if necessary.
-
chrpath (often needed for relocatable binaries in embedded builds):
bash
Copy code
sudo apt-get install chrpath
-
bc (sometimes needed in kernel/uboot builds):
bash
Copy code
sudo apt-get install bc
If you’re missing any of the key dependencies, Buildroot’s configure scripts (which might run ./configure, config.status, etc.) can fail unexpectedly.
2. Delete and Re-Extract (Clean Rebuild)
Build systems like Buildroot can leave stale artifacts if a previous partial build failed. Try:
-
Back up your config (e.g.,
.config) if you customized it.
- Completely remove or clean the
output/ or build/ directory:
bash
Copy code
make clean
or
bash
Copy code
rm -rf output/* build/*
-
Re-run your build from scratch:
bash
Copy code
make sg2002_recamera_emmc
Sometimes simply cleaning out the old partial build files resolves weird libtool or make errors.
3. Check the Host OS for Known Buildroot Quirks
-
Ubuntu 20.04 is usually fine, but if you’re on 22.04 or 24.04 (beta?), there could be issues with updated toolchains or certain out-of-date recipes in Buildroot 2021.05.
- Some Buildroot versions don’t handle newer host compilers or glibc versions well. A patch or a newer Buildroot might be required.
4. Try a Docker or LXD Container
If you keep hitting weird errors on your main Ubuntu host, you could:
-
Spin up a Docker container with an Ubuntu 20.04 or 22.04 base image.
-
Install all the dev dependencies.
-
Clone your recamera build environment into that container.
- Attempt the build in a clean, reproducible environment.
This approach often bypasses local OS differences and ensures you have exactly the libs Buildroot expects.
5. Double-Check the Buildroot/Project Docs
- The recamera OS might have specific instructions: “If you’re using Ubuntu, install these packages….”
- Some projects rely on environment variables or symlinks that might be missing. E.g., if
JAVA_HOME or CC isn’t set, certain builds can fail in the configure step.
- If it’s specifically failing at
libtool commands, it might be that your host’s libtool version or environment doesn’t match what Buildroot expects.
6. Inspect the Logs
Look in output/sg2002_recamera_emmc/buildroot-2021.05 or the subdirectory where it was compiling the failing package:
-
Look for “config.log” or any logs with actual error messages about missing headers, libraries, or “checking for something… no.”
- If the build triggered “Error 2” at a sub-step, the real error might appear just a few lines above in the logs.
Quick Check Summary
-
Install all standard dev packages (build-essential, libtool, autoconf, automake, etc.).
-
Clean the build directories thoroughly.
- Try Docker or an environment known to be stable for Buildroot 2021.05.
-
Check logs for the true error cause.
Following these steps usually gets rid of the dreaded _all Error 2 messages in Buildroot or any embedded Linux environment. Good luck with your recamera OS build!