Skip to content

Current build pain #3735

@ocdtrekkie

Description

@ocdtrekkie

Working on building Sandstorm on my Debian 11 box. So far:

BoringSSL has been a pain:

  • I had an issue I got past by adding libunwind-dev, which is supposed to be optional but maybe we should tell people to install it.
  • I still couldn't build BoringSSL, and tried moving to a newer version, 0.20250818.0, which seems okay. (But!)
  • BoringSSL main requires CMake 3.22 as of last month (Bullseye has 3.18), which is why I picked this tag.
  • The Makefile references a "master" branch for BoringSSL, it is "main" now.
  • The build then fails because it cannot find /build/ssl/libssl.a and /build/crypto/libcrypto.a but they are just in /build now, moving them lets me proceed.

Once surviving this, I am now in Meteor frontend build processing... which is still in progress.

To fix the GitHub CI runner, we need to be able to build on a newer Ubuntu, and I believe that requires updating capnp, so that is my next thing to look at once I get past the basics.

cc: @wwahammy because I think you've spent more time with some of this botrot than me.

Metadata

Metadata

Assignees

No one assigned

    Labels

    sandstorm-devIssues hacking on Sandstorm

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions