summaryrefslogtreecommitdiffstats
path: root/package/Makefile.in
Commit message (Collapse)AuthorAgeFilesLines
* Another external toolchain fixThomas Petazzoni2009-03-291-2/+2
| | | | | | | | | | | | | | | | | | | | | | Change the definition of TARGET_LDFLAGS to use --sysroot $(STAGING_DIR) instead of -L$(STAGING_DIR)/lib -L$(STAGING_DIR)/usr/lib. It fixes the following failure while trying to build mtd-utils : /usr/local/xtools/arm-unknown-linux-uclibcgnueabi/bin/arm-unknown-linux-uclibcgnueabi-gcc -L/home/thomas/local/buildroot-output/build_arm/staging_dir/lib -L/home/thomas/local/buildroot-output/build_arm/staging_dir/usr/lib -o /home/thomas/local/buildroot-output/build_arm/mtd_orig/flash_eraseall /home/thomas/local/buildroot-output/build_arm/mtd_orig/crc32.o /home/thomas/local/buildroot-output/build_arm/mtd_orig/flash_eraseall.o /usr/local/xtools/arm-unknown-linux-uclibcgnueabi/lib/gcc/arm-unknown-linux-uclibcgnueabi/4.3.2/../../../../arm-unknown-linux-uclibcgnueabi/bin/ld: cannot find /lib/libc.so.0 collect2: ld returned 1 exit status make[1]: *** [/home/thomas/local/buildroot-output/build_arm/mtd_orig/flash_eraseall] Error 1 At the same time, simplify the definition of TARGET_CFLAGS, because the -I$(STAGING_DIR)/include -I$(STAGING_DIR)/usr/include -I$(TOOLCHAIN_EXTERNAL_PATH)/$(TOOLCHAIN_EXTERNAL_PREFIX)/include are no longer necessary since we sysroot the toolchain in $(SYSROOT_DIR). This patch has no effect on non-external toolchain builds. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
* package: add STAMP_DIR and use for host buildsPeter Korsgaard2009-03-191-2/+2
| | | | | | | | | | | | | | Move stamp (dependency) files outside the (version specific) source directories, so other packages can hardcode dependencies on them instead of having to use <PACKAGE>_VERSION variables. This is important as the variables in the make rules are evaluated when the rules is seen, which might be before the dependent makefile is parsed (and hence <PACKAGE>_VERSION variable is known, screwing up stuff. The downside of this is that the package isn't automatically rebuilt when the version changes (E.G. by a svn update) and you now also have to remove the stamp files next to $(BUILD_DIR)/<PACKAGE>-* to force a rebuild.
* pkg-config: rename pkgconfig to pkg-configPeter Korsgaard2009-03-191-2/+2
| | | | | | This matches upstream tarball, doesn't screw up existing .config's with BR2_PACKAGE_PKGCONFIG and makes sure the patch gets applied for target compilation.
* pkgconfig: install into HOST_DIRPeter Korsgaard2009-03-181-2/+2
|
* package: add HOST_DIR to target pathPeter Korsgaard2009-03-171-1/+1
|
* package: fix host pathPeter Korsgaard2009-03-171-2/+4
| | | | And generate dbus introspect xml for dbus-glib.
* package/Makefile.in: search $(HOST_DIR) for host includes / librariesPeter Korsgaard2009-03-161-0/+5
|
* Makefile: introduce $(HOST_DIR) for host binariesPeter Korsgaard2009-03-161-1/+3
| | | | | Add HOST_DIR directory handling. HOST_DIR should be used just like STAGING_DIR, but for host files instead of target ones.
* mpg123: remove arm funroll-loops workaroundPeter Korsgaard2009-02-051-8/+0
| | | | Fixed by toolchain patch.
* Do not overwrite user configurationUlf Samuelsson2009-02-011-5/+5
|
* Make toolchain configration to fix mpg123 global and move to MakefileUlf Samuelsson2009-01-241-0/+8
|
* toolchain: introduce HOSTCC_VERSION and fix gcc-4.3.x build with old host CCsPeter Korsgaard2009-01-191-0/+4
| | | | | | | | gcc < 4.2.0 doesn't support -Wno-overlength-stings, but gcc-4.3.x configure fails to detect that, breaking the build. Work around it by detecting the host gcc version (and store in HOSTCC_VERSION) and set the proper configure variables for gcc < 4.2.0.
* The liboil Makefile will use "-mcpu=vfp" when building for ARM.Ulf Samuelsson2009-01-181-0/+4
| | | | | | | | | | | | | | | The VFP is only available for a few ARM CPUs at the moment, so this breaks the liboil build. A patch is available upstream which only enables "-mfpu=vfp" if "--enable-vfp" is given to "configure". Autotools needs to be run for liboil for this to take effect. A new configuration BR2_VFP_FLOAT is added to allow enabling vfp. If this is "yes", then "-mfpu=vfp" is added to CFLAGS.
* Easier with one place for configure options for disabling gtk-docThomas Lundquist2009-01-171-0/+4
|
* buildroot: get rid of s390 supportPeter Korsgaard2009-01-121-3/+0
| | | | | As discussed on the list. It isn't supported by uclibc, so I strongly doubt anyone has been using it.
* buildroot: set SHELL instead of messing around with CONFIG_SHELLPeter Korsgaard2009-01-011-3/+3
| | | | | Simply set SHELL to bash instead of adding CONFIG_SHELL to all shell invocations. CONFIG_SHELL is still set, as it is used by kconfig.
* Fix TARGET_PATH for external toolchain buildsThomas Petazzoni2008-12-151-1/+1
| | | | | | | | | | TARGET_PATH didn't contain $(STAGING_DIR)/usr/bin, which means that programs installed in $(STAGING_DIR)/usr/bin were not considered for execution during Buildroot build process. This was a problem with host automake/autoconf/libtool, which could not be found. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
* Another external toolchain support solutionThomas Petazzoni2008-12-131-3/+1
| | | | | | | | | | | | | | | | | | | | * In toolchain/external-toolchain/ext-tool.mk, copy the contents of the sysroot directory to the staging dir. * In package/Makefile.in, add a --sysroot CFLAGS pointing to the staging dir * Remove the CFLAGS and LDFLAGS definition from TARGET_CONFIGURE_OPTS. I haven't investigated exactly why, but with these options, DirectFB fails to build because it cannot find PTHREAD_RECURSIVE_MUTEX_INITIALIZER_NP, even if DirectFB's Makefile properly sets -D_GNU_SOURCE. I have already sent this patch on December, 2nd to the mailing-list, but got no feedback. So let's commit and see what happens :-) Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
* package/: get rid of unneeded $(strip ..)Peter Korsgaard2008-12-081-4/+4
|
* Adding Central config.cache optionsDaniel Laird2008-11-281-1/+27
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The following changes allow for use of a central configure cache file. This speeds up configuration of packages. Its use is configurable at the top level (BR2_CONFIG_CACHE - default n). Old style makefiles can use it if they use the following MACRO in makefiles: $(AUTO_CONFIGURE_TARGET) see my change to directfb.mk. New style Autotools.in will use it if you set the global option. However you can enable the global option and on a per package overrule it by doing the following: $(PKGNAME)_USE_CONFIG_CACHE = NO see fontconfig.mk for an example of this. Finally I have removed a few config variable settings which indicated no CXX compiler as this is wrong and breaks the build when using this central cache. Config.in | 8 ++++++++ package/Makefile.autotools.in | 5 ++++- package/Makefile.in | 28 +++++++++++++++++++++++++++- package/atk/atk.mk | 2 +- package/directfb/directfb.mk | 7 +------ package/fontconfig/fontconfig.mk | 3 +++ package/libglib2/libglib2.mk | 2 +- package/libgtk2/libgtk2.mk | 1 - 8 files changed, 45 insertions(+), 11 deletions(-) I would appreciate feedback on this change (I have been testing for 2-3 weeks) But I can never test all cases! If you enable the BR2_CONFIG_CACHE option some Makefile.autotools.in based packages may now break - I cannot build them all. In this case you may need to remove config options that are being hardcoded all over the place (like gtk saying we have 2 CXX compiler) or disable the use of CONFIG CACHE file like I have done in fontconfig. I can build all packages required to get WebKit on DirectFB up and running and it runs fine. I will try to resolve any issues this creates as fast as I can. Signed-off-by: Daniel Laird <daniel.j.laird@nxp.com>
* Revert r24000: "Fix external toolchain build"Peter Korsgaard2008-11-211-10/+4
| | | | | This breaks builds with internal toolchain, so let's revert this until we find a proper solution.
* Fix external toolchain buildThomas Petazzoni2008-11-111-4/+10
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This patch is a new version of a patch already sent several times on the mailing-list, committed and reverted a few times by Daniel Laird, due to several imperfections. This version is a new try at finding a solution that works for everybody. Hopefully it'll work :-) The original problem is that external toolchain builds failed because packages couldn't find their dependent libraries at configure time and could not be linked with them. To fix these two problems, two things are added: * The TARGET_LDFLAGS variable was exposed as LDFLAGS at ./configure time thanks to TARGET_CONFIGURE_OPTS. The TARGET_LDFLAGS variable contains -L options with the path in the STAGING_DIR for the libraries. It allows ./configure scripts to properly compile the small test programs testing whether a dependency is properly installed. * The TARGET_CFLAGS contains a new -Wl,--rpath-link option for both $(STAGING_DIR)/lib and $(STAGING_DIR)/usr/lib. It allows library depending on other libraries to link properly. The TARGET_CFLAGS is exposed as CFLAGS in TARGET_CONFIGURE_OPTS. This new version fixes a problem encountered by hartleys <hartleys@visionengravers.com> when building the kernel. The problem was that the -Wl,--rpath-link options were added to LDFLAGS, while there are options for the C compiler, not the ld linker. Moving them to CFLAGS seems to fix the issue. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
* package/Makefile.in: revert rpath setup for toolchains.Daniel Laird2008-11-071-4/+3
| | | | | | | | | | Revert the rpath patch, it looked good up until someone tried to build a kernel as well. This seems to break as a result. Will post a new patch soon and see how that goes.. Signed-off-by: Daniel Laird <daniel.j.laird@nxp.com>
* package/Makefile.in: rpath setup for toolchains.Daniel Laird2008-11-061-3/+4
| | | | | | | | | | Apply the patch I posted some time ago that fixes rpath issues with external toolchains. Has been tested by users of buildroot and feedback looks good. Signed-off-by: Thomas Petazzoni Signed-off-by: Daniel Laird <daniel.j.laird@nxp.com>
* package/Makefile.in: Remove rpath fix as it breaks Thomas png buildDaniel Laird2008-10-221-4/+2
| | | | | | | | Remove my fix for rpath-link until I can find out why it works for me and not Thomas. Signed-off-by: Daniel Laird <daniel.j.laird@nxp.com>
* package/Makefile.in: Add -rpath-link Daniel Laird2008-10-221-2/+4
| | | | | | | | | | | As per various email discussions add -rpath-link to the LDFLAGS. This definately fixes a few issues for Thomas and myself Any objections and it can be pulled again. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@...> Signed-off-by: Daniel Laird <daniel.j.laird@nxp.com>
* package: global largefile CFLAGS handlingPeter Korsgaard2008-08-041-0/+4
|
* package/Makefile.in: cleanup MAKE/MAKE1Peter Korsgaard2008-07-111-7/+2
| | | | The extra stuff doesn't seem to be needed, so lets just get rid of it.
* package/Makefile.in: propagate -s make flag to sub makesPeter Korsgaard2008-07-011-5/+4
|
* pkgconfig: bump version and cleanupPeter Korsgaard2008-06-141-3/+1
| | | | | | | Upgrade to pkgconfig 0.23 which has native sysroot support (buggy, but easily fixable), which allows us to get rid of pkgconfig-filter.sh. At the same time cleanup the makefile.
* Makefile: honor silent (-s) flagPeter Korsgaard2008-05-311-0/+6
|
* added more debugging options for packagesJohn Voltz2008-03-121-0/+25
|
* added debug optionJohn Voltz2008-03-111-0/+5
|
* Use host ldconfig, if external toolchain is usedUlf Samuelsson2008-01-101-0/+4
|
* FIx syntax errorUlf Samuelsson2007-10-301-1/+1
|
* Allow to remove _nofpu from directories and imagesUlf Samuelsson2007-10-181-4/+10
|
* Remove debugging info from package/Makefile.inUlf Samuelsson2007-10-181-3/+0
|
* Remove hyphen from images if empty rootfs suffixUlf Samuelsson2007-10-181-1/+6
|
* Allow date to be added to ImageUlf Samuelsson2007-10-071-4/+10
|
* - fix some whitespace damage..Bernhard Reutner-Fischer2007-10-051-1/+1
| | | | - add COPYTO settings for cpio and tar and remove that ugly hardcoded DATE from that was added by Ulf
* - default to mips I for mipsel and mips III for mips Bernhard Reutner-Fischer2007-10-021-0/+4
| | | | - suggest some target flags for abi64
* - just use the strip binary to avoid confusing libtool (quotes)Bernhard Reutner-Fischer2007-10-011-4/+4
| | | | - use $(STRIPCMD) in packages to avoid clashes with $(STRIP)
* - fix quotes for STRIP.Bernhard Reutner-Fischer2007-09-291-31/+31
| | | | Sorry for any inconvenience this may have caused..
* - make sure that strip and all it's arguments are passed if used viaBernhard Reutner-Fischer2007-09-291-3/+3
| | | | | STRIP=$(TARGET_STRIP) (i.e. without quoting). Thanks to Dimitry Golubovsky for mentioning this.
* - cleanup configure optionsBernhard Reutner-Fischer2007-09-281-38/+49
|
* - add FC, remove some duplicate entries, cleanupBernhard Reutner-Fischer2007-09-281-10/+17
| | | | - fixup after Ulf: CXX doesn't take CFLAGS but CXXFLAGS
* Sort HOST/TARGET_CONFIGURE_OPTS, add some more, needed for gcc-4.1.2Ulf Samuelsson2007-09-281-10/+29
|
* - add a query for suggestions on how to deal with MALLOC_GLIBC_COMPATBernhard Reutner-Fischer2007-09-271-0/+2
|
* - revert some bad checkins, fixup bad settings in atmel targets and move the ↵Bernhard Reutner-Fischer2007-09-261-2/+2
| | | | gcc target abi back to a place where the other arch-specific settings live
* - revert r19918 for nowBernhard Reutner-Fischer2007-09-201-1/+0
|
generated by cgit v1.2.3 (git 2.39.1) at 2024-11-01 03:55:06 +0000