DSL Tips and Tricks :: easier way to compile stuff for DSL

You might want to do some googling for some beginner's guides to this.

Also, always read the README and INSTALL text files in the sources for instructions.

Building from source on dsl is much like building from source on bigger systems, with the exception that dsl lacks a lot of headers and libs that may or may not be needed for particular builds. Often these have to be added first.

In the simplest scenario:

1. Install gcc1-with-libs.dsl
2. tar -zxvf somesource.tar.gz
3. cd somesource
4. ./configure
5. make
6. make install

Not all sources have a "configure" script. If they do, it will often tell you if something is missing from the system that it needs.

In the worst case scenario, you can spend some time hunting down dependencies and headers and building or otherwise installing those first, one after the other.

It can be a bit of an art form on a minimalized system such as dsl - see the thread on building Xorg as an example.

Or you could wait, I think florian might make an extension out of flphoto..

I after a "hiatus" on this story, I finally managed to compile glibc-2.3.2 - for some reason it needs about 800MB to compile for a 13MB tar.bz2 package...

So now I have gcc, binutils, glibc, m4, etc, etc compiled on dsl to /opt/build using a compile environment built from "sarge" debs (chosen because the "sarge" libc6 is closest to that of dsl). If I understand correctly, gcc requires "kernel headers" in addition to the glibc headers in order to be able to compile - I plan to take the headers from /include in the full 2.4.26 kernel sources - does this make the most sense in dsl terms?

The recommended procedure for getting 2.4 kernel headers:

Quote

make mrproper
make include/linux/version.h
make symlinks
mkdir /tools/include/asm
cp -v include/asm/* /tools/include/asm
cp -vR include/asm-generic /tools/include
cp -vR include/linux /tools/include

This is to --prefix=/tools. Change that to what you want.

As you see, it doesn't just copy the whole include dir..

Thanks - that seems to have done the trick (at least to compile patch-2.5.9 as a test).

I'm aiming to make a build/compile uci [edit] - given that some libs (eg libc-2.3.2.so) will be duplicated with dsl, is it better to symlink to the base dsl versions or use separate libs in the extension?

Next Page...
original here.