From 34ea77c220129e3935d352ad7c333928d2e8feff Mon Sep 17 00:00:00 2001 From: Eelco Dolstra Date: Mon, 30 Sep 2013 22:47:26 +0200 Subject: [PATCH] Remove obsolete doc file --- maintainers/docs/uclibc-cross.txt | 27 --------------------------- 1 file changed, 27 deletions(-) delete mode 100644 maintainers/docs/uclibc-cross.txt diff --git a/maintainers/docs/uclibc-cross.txt b/maintainers/docs/uclibc-cross.txt deleted file mode 100644 index c32a95eb2b2..00000000000 --- a/maintainers/docs/uclibc-cross.txt +++ /dev/null @@ -1,27 +0,0 @@ -Adding uClibc support for a new platform - -Sometimes you want to cross-compile to another architecture, for example an -embedded devices. For embedded devices the uClibc C library is popular. -In Nixpkgs there is support for uClibc for several architectures but not -everything is supported. - -Adding support is not very difficult, - -* Add your architecture to the buildfiles in -$nixpkgs/development/tools/misc/binutils-cross - -* Add your architecture to the buildfiles in -$nixpkgs/development/compilers/gcc-4.0-cross - -* Add your architecture to the buildfiles in -$nixpkgs/os-specific/linux/kernel-headers-cross - -* Add your architecture to the buildfiles in -$nixpkgs/development/uclibc - -In the latter directory you will also need a configuration file for uClibc. -You can make these by unpacking the uClibc sources and run a "make menuconfig". -In the configuration a few things need to be adapted: - -- kernel sources -> need to point at our own kernel headers -- install -> needs to point at $out