Differences

This shows you the differences between two versions of the page.

--- building-packages [2015/05/07 00:54] – snacsnoc
+++ building-packages [2025/02/22 06:12] (current) – snacsnoc
@@ Line 1: / Line 1: @@
 ====== Building packages ======
-For native compilations export CC to ''CC="musl-gcc -static"'' and compile normally. See below for an example.
+Example build flow:
 <code>
-export CC="musl-gcc -static"
+export LDFLAGS="-s"
 export C_INCLUDE_PATH=/include:/usr/include
 tar xvf myfancysoftware-1.0.tar.gz && cd myfancysoftware-1.0
@@ Line 16: / Line 17: @@
 </code>
+If configure complains about /lib/cpp failing sanity check, try this:
+<code>
+fbpkg install ucpp
+ln -sf /usr/bin/ucpp /lib/cpp
+export CPPFLAGS="-I/include -I/usr/include"
+</code>
+and recompile.
+**pkg-config**
+Use pkgconf as a drop-in replacement instead, install via fbpkg
+<code>
+ln -sf /usr/bin/pkgconf /usr/bin/pkg-config
+</code>
+**Notes**
+For non-native compilations (using the musl toolchain) set ''--host=i486-musl-linux'' and enable any static compilation options (such as '' CFLAGS="-static" LDFLAGS="-static" '').
-For non-native compilations (using the musl toolchain) set ''--host=i486-musl-linux'' and enable any static compilation options (such as CFLAGS="static").
+Optimize for i486 CPUs: '' CFLAGS="-march=i486 -mtune=i486 -Os -fomit-frame-pointer" ''
 As well, for either types of builds setting ''CFLAGS="-s" LDFLAGS="-s"'' is a good idea to automatically have gcc to strip the libs and binaries.
-A mirror of all the packages tars are available here: http://snacklinux.org/tars/
+A mirror of all the packages tars are available here: http://snacklinux.geekness.eu/tars/