If it would help, we could supply a VM with each release that had the coreboot toolchain pre-built. It's also possible to use the released docker images to rebuild coreboot - those already contain the toolchain.
The advantages to both of these is that you'd be building in the environment that was originally used at the time the code was developed - that works around a significant number of problems that you could be running int. If you're interested in either of those options, let me know and I'll supply images and instructions to get you up and running. Martin Jan 8, 2023, 12:16 by rminn...@gmail.com: > But in some cases static libs are no longer provided at all. Would be nice to > know if that's the case for libuuid. > > On Sun, Jan 8, 2023, 9:24 AM Nico Huber <> nic...@gmx.de> > wrote: > >> On 08.01.23 17:42, ron minnich wrote: >> > For reasons I still don't understand, the various linux distros no longer >> > ship .a as part of the library package. >> >> They ship them separately. On Ubuntu, usually a -dev package. I even >> recall -devel-static packages (-devel was headers only and such) >> ~20 years back. >> >> The reason to ship them separately is simple: not everybody has the >> space/bandwidth to spare. These habits are decades old. Some newer >> distros moved to ship everything in one package, though. >> >> One odd thing about libuuid: The Ubuntu package is called uuid-dev >> (not libuuid-dev). That's something I don't understand ;) >> >> Nico >> _______________________________________________ coreboot mailing list -- coreboot@coreboot.org To unsubscribe send an email to coreboot-le...@coreboot.org
