libbsd | BSD compatibility library | TCP library

I solved it running under the Rosetta Terminal

1. Locate the Terminal application within the Utilities folder (Finder> Go menu > Utilities)

2. Select Terminal.app and right-click on it, then choose “Duplicate” Rename the duplicated Terminal app something obvious and distinct, like ‘Rosetta Terminal’

3. Now select the freshly renamed ‘Rosetta Terminal’ app and right-click and choose “Get Info” (or hit Command+i)

4. Check the box for “Open using Rosetta”, then close the Get Info window Run the “Rosetta Terminal” as usual, which will fully support Homebrew and other x86 command line apps

This is normal behavior in CMake. When compiling you binaries the rpath to the dependencies is set in the binary, but stripped when installing it.

By default if you don't change any RPATH related settings, CMake will link the executables and shared libraries with full RPATH to all used libraries in the build tree. When installing, it will clear the RPATH of these targets so they are installed with an empty RPATH. Source

When looking up runtime dependencies the rpath is preferred over the default directories (see https://stackoverflow.com/a/33520976/4181011). But since the rpath was removed from your library it doesn't know about you "out-of-default-directories"-dependencies.

You can manipulate the lookup with LD_LIBRARY_PATH, LD_PRELOAD or by adding the additional path to the lookup directories using ldconfig.

The example ldd output above was saved to "infile". Description: run awk to select lines with 4 fields and echo a command that would copy the lib from the third field to a destination directory:

Use gcc to link and use -Wl,-Bstatic to tell the linker to prefer linking against static libraries rather than shared ones. Example:

Might be a simple case of:

If you want to get puppeteer to work on alpine, try using an older version of puppeteer that works with an older version of Chrome. The newest version of Chrome supported on Alpine is 63, which was the version of Chrome used during the development of puppeteer version 0.11.0.

Since your using the --pure option, nothing from your previous environment will be imported into the shell. This includes the swift binary itself. So first I would add swift to the buildInputs.

The error your getting indicates that gcc doesn't even understand the command line options being passed. I don't know anything about Swift, but after seeing that I assumed that it needs a different compiler. Sure enough, after a quick search it looks like it is llvm based. You will thus need to also add clang to your build inputs. In addition, you'll need to use mkShell instead of mkDerivation to setup the proper environment.

The former is a wrapper to the latter that is specifically designed to set up a nix-shell, and ensures the environment is handled correctly. You'll need to pass in the shellHook attribute to override the default c compiler to clang using the CC envvar. The shellHook is a way of running arbitrary commands at the start of the shell.

As a final note, the nix-shell command searches for shell.nix by default so you don't have to pass it as an argument. If shell.nix does not exist, then it will try default.nix. If neither exist, then you'll have to explicitly specify the nix expressions location.

TLDR

to put it all together:

This is pretty easy to understand and replicate, but there is a number of moving parts.

We ssh to a remote machine with X forwarding. This ssh process must have access to a working X server locally. Here we'll start it up with a joke $DISPLAY:

You need to use WORKDIR as a Dockerfile instruction, instead of using it together with run instruction.

RUN has 2 forms:

• RUN (shell form, the command is run in a shell, which by default is /bin/sh -c on Linux or cmd /S /C on Windows) RUN

• ["executable", "param1", "param2"] (exec form)

WORKDIR

WORKDIR /path/to/workdir The WORKDIR instruction sets the working directory for any RUN, CMD, ENTRYPOINT, COPY and ADD instructions that follow it in the Dockerfile