summaryrefslogtreecommitdiff
path: root/target/mips/uclibc.config
AgeCommit message (Collapse)Author
2015-05-06add UCLIBC_HAS_CONTEXT_FUNCS for mongrel2Waldemar Brodkorb
2015-04-14LDSO_RUNPATH_OF_EXECUTABLE is required f.e. for sambaWaldemar Brodkorb
2015-03-23uClibc added a new symbol for utmp supportWaldemar Brodkorb
2015-02-20use MALLOC with GLIBC_COMPAT for all archsWaldemar Brodkorb
Use MALLOC for uClibc/uClibc-ng 1.0. Choice will be removed in uClibc-ng git.
2014-12-27enable getopt longWaldemar Brodkorb
2014-09-28always enable pthread debug support as discussed with tgWaldemar Brodkorb
2014-08-25disable XSI_MATH, prevent testsuite linking failures.Waldemar Brodkorb
2014-06-29remove RPC from uclibc, use libtirpcWaldemar Brodkorb
2014-06-29handle debug code handling inside OpenADKWaldemar Brodkorb
2014-06-27add ltp package, add more uClibc options to have a wider test rangeWaldemar Brodkorb
2014-05-24fix uclibc compile for qemu-arm (experimental fix), use DODEBUG as defaultWaldemar Brodkorb
2014-03-06cleanup uclibc.config mess. just use one and edit via sedWaldemar Brodkorb
2011-04-26make arm/mips architectures more configurable in a simpler wayWaldemar Brodkorb
2011-02-01needed for gdbWaldemar Brodkorb
2010-12-30rework architecture / embedded systems conceptWaldemar Brodkorb
Make configuration of new targets cheap. Just add a new file in target/arch/sys-enabled/foo. See other files for syntax. While doing runtime tests with the new infrastructure I've updated a lot of other stuff: - gcc 4.5.2 - uClibc 0.9.32-rc1 (NPTL) - strongswan, php, miredo, parted, util-linux-ng, e2fsprogs I promise, this is the last big fat commit this year ;)
2010-11-26implement the concept of target choice by embedded system or architectureWaldemar Brodkorb
you can now choose between specific embedded systems like PC Engines ALIX boards, Foxboard, .. or between generic architecture support like x86, x86_64, mips, ... This does reduce the overhead of duplicate configuration files in target directory. Now qemu, toolchain and ibm x40 support is combined in one target directory target/x86. Distinguishing between hardware profiles happens via menu based configuration. (CPU choice for kernel, CFLAGS for package building, ..). We will see if this is the right direction.