Go to file
Yann E. MORIN 8c3f1d5102 package/berkeleydb: fix shared-only build
Changeset f1d3e09 (Build shared libraries only as the default) broke the
berkeleydb package.

For some reason, we had a very strange post-configure action in bdb:
        $(SED) 's/\.lo/.o/g' $(@D)/build_unix/Makefile

This means that it is using non-libtool object files. This breaks
building shared-only.

This code has been present almost the whole time we've had a berkeleydb
package, that is:
  - November 2003: use a sed expression instead of perl
  - March 2003   : use a perl program
  - August 2002  : introduce berkeleydb

Getting rid of this sed expression fixes the build, and allows building
the three new static/shared combinations: static only, shared only,
both static and shared.

Fixes numerous build failures:

Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Cc: Peter Korsgaard <jacmet@uclibc.org>
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2014-12-13 10:36:02 +01:00
arch Turn the static lib option into a choice with more options 2014-12-12 00:09:02 +01:00
board configs/qemu: update to the latest kernel/headers versions 2014-12-09 14:30:37 +01:00
boot barebox: bump to version 2014.12.0 2014-12-10 20:01:26 +01:00
configs configs/qemu: update to the latest kernel/headers versions 2014-12-09 14:30:37 +01:00
docs Rename BR2_PREFER_STATIC_LIB to BR2_STATIC_LIBS 2014-12-11 22:48:13 +01:00
fs package: indentation cleanup 2014-12-10 21:53:30 +01:00
linux linux: bump default to version 3.18 2014-12-08 13:11:45 +01:00
package package/berkeleydb: fix shared-only build 2014-12-13 10:36:02 +01:00
support pkg-download: check hashes for locally cached files 2014-12-11 23:59:41 +01:00
system Rename BR2_PREFER_STATIC_LIB to BR2_STATIC_LIBS 2014-12-11 22:48:13 +01:00
toolchain Rename BR2_PREFER_STATIC_LIB to BR2_STATIC_LIBS 2014-12-11 22:48:13 +01:00
.defconfig buildroot: get rid of s390 support 2009-01-12 14:36:14 +00:00
.gitignore update gitignore 2013-05-04 12:41:55 +02:00
CHANGES Update for 2014.11 2014-12-01 10:19:00 +01:00
COPYING clarify license and fix website license link 2009-05-08 09:29:41 +02:00
Config.in Build shared libraries only as the default 2014-12-12 00:09:41 +01:00
Config.in.legacy Rename BR2_PREFER_STATIC_LIB to BR2_STATIC_LIBS 2014-12-11 22:48:13 +01:00
Makefile Merge branch 'next' 2014-12-01 11:16:42 +01:00
Makefile.legacy Makefile.legacy: fix recursive invocation with BUILDROOT_DL_DIR and _CONFIG 2014-02-11 08:14:57 +01:00
README docs: Move README file to root 2014-03-03 21:28:39 +01:00


To build and use the buildroot stuff, do the following:

1) run 'make menuconfig'
2) select the packages you wish to compile
3) run 'make'
4) wait while it compiles
5) Use your shiny new root filesystem. Depending on which sort of
    root filesystem you selected, you may want to loop mount it,
    chroot into it, nfs mount it on your target device, burn it
    to flash, or whatever is appropriate for your target system.

You do not need to be root to build or run buildroot.  Have fun!

Offline build:

In order to do an offline-build (not connected to the net), fetch all
selected source by issuing a
$ make source

before you disconnect.
If your build-host is never connected, then you have to copy buildroot
and your toplevel .config to a machine that has an internet-connection
and issue "make source" there, then copy the content of your dl/ dir to
the build-host.

Building out-of-tree:

Buildroot supports building out of tree with a syntax similar
to the Linux kernel. To use it, add O=<directory> to the
make command line, E.G.:

$ make O=/tmp/build

And all the output files (including .config) will be located under /tmp/build.

More finegrained configuration:

You can specify a config-file for uClibc:
$ make UCLIBC_CONFIG_FILE=/my/uClibc.config

And you can specify a config-file for busybox:
$ make BUSYBOX_CONFIG_FILE=/my/busybox.config

To use a non-standard host-compiler (if you do not have 'gcc'),
make sure that the compiler is in your PATH and that the library paths are
setup properly, if your compiler is built dynamically:
$ make HOSTCC=gcc-4.3.orig HOSTCXX=gcc-4.3-mine

Depending on your configuration, there are some targets you can use to
use menuconfig of certain packages. This includes:
$ make HOSTCC=gcc-4.3 linux-menuconfig
$ make HOSTCC=gcc-4.3 uclibc-menuconfig
$ make HOSTCC=gcc-4.3 busybox-menuconfig

Please feed suggestions, bug reports, insults, and bribes back to the
buildroot mailing list: buildroot@buildroot.org