| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
I'm trying to create a package for libgpiod, which uses
AC_CONFIG_AUX_DIR macro, which is probably leading to the following
configure error:
autoreconf: running: /openwrt.git/staging_dir/host/bin/libtoolize --force
OpenWrt-libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, `autostuff'.
OpenWrt-libtoolize: linking file `autostuff/ltmain.sh'
OpenWrt-libtoolize: putting macros in `m4'.
...
configure: error: cannot find install-sh, install.sh, or shtool in autostuff "."/autostuff
>From the build output it's clear, that libtoolize isn't installing
install-sh symlink, because libtoolize would install install-sh only if
it's being run with --install parameter. Corresponding part in
libtoolize:
if $opt_install; then
func_config_update config.guess \
"$pkgdatadir/config" "$auxdir" pkgconfig_header
func_config_update config.sub \
"$pkgdatadir/config" "$auxdir" pkgconfig_header
func_install_update install-sh \
"$pkgdatadir/config" "$auxdir" pkgconfig_header
fi
func_ltmain_update ltmain.sh \
"$pkgdatadir/config" "$auxdir" pkgconfig_header
Adding --install parameter to libtoolize fixes this build issue:
autoreconf: running: /openwrt.git/staging_dir/host/bin/libtoolize --install --force
OpenWrt-libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, `autostuff'.
OpenWrt-libtoolize: linking file `autostuff/config.guess'
OpenWrt-libtoolize: linking file `autostuff/config.sub'
OpenWrt-libtoolize: linking file `autostuff/install-sh'
OpenWrt-libtoolize: linking file `autostuff/ltmain.sh'
OpenWrt-libtoolize: putting macros in `m4'.
Cc: Felix Fietkau <nbd@nbd.name>
Signed-off-by: Petr Štetiar <ynezz@true.cz>
(cherry picked from commit 5cf897779eacf63cdbcdebd1af68c109096665c6)
|
|
|
|
|
|
|
| |
Build depends must refer to source packages rather than binary package
names.
Signed-off-by: Matthias Schiffer <mschiffer@universe-factory.net>
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
directory for all targets
Using a single host package staging dir (and build dir) significantly speeds up
builds when multiple targets are built in succession, especially for large host
packages like NodeJS.
$(STAGING_DIR)/host is kept in addition to $(STAGING_DIR_HOSTPKG) in most
places; it is still used as destination for host files in Build/InstallDev.
Signed-off-by: Matthias Schiffer <mschiffer@universe-factory.net>
|
|
|
|
|
|
|
| |
Make sure binaries install to STAGING_DIR_HOSTPKG are still found when
this variable is eventually modified.
Signed-off-by: Matthias Schiffer <mschiffer@universe-factory.net>
|
|
|
|
|
|
|
| |
0.19.8.1 gettext-full uses "archive-version" of 0.19.8
to replace makros, leading to breakage of PKG_FIXUP:=gettext-version
Signed-off-by: Dirk Neukirchen <dirkneukirchen@web.de>
|
|
|
|
|
|
| |
Signed-off-by: Felix Fietkau <nbd@openwrt.org>
SVN-Revision: 48421
|
|
|
|
|
|
| |
This reverts commit r48403
SVN-Revision: 48412
|
|
|
|
|
|
| |
Signed-off-by: Felix Fietkau <nbd@openwrt.org>
SVN-Revision: 48403
|
|
|
|
|
|
|
|
|
|
|
| |
* enclose the fixup in brackets
* match anything in the call to AM_GNU_GETTEXT_VERSION
* call it early (before autoreconf if both are specified)
* chain a call to autoreconf since it messes with configure.ac
Signed-off-by: Nicolas Thill <nico@openwrt.org>
SVN-Revision: 44225
|
|
|
|
|
|
|
| |
This fixup aligns the required gettext version in shipped macros to the one
available in $(STAGING_DIR_HOST).
SVN-Revision: 33708
|
|
|
|
| |
SVN-Revision: 32207
|
|
|
|
|
|
| |
this
SVN-Revision: 29835
|
|
|
|
|
|
| |
ABOUT-NLS - needed by minidlna CVS version
SVN-Revision: 28464
|
|
|
|
|
|
| |
already applied
SVN-Revision: 28419
|
|
|
|
|
|
| |
OpenWrt, Buildroot and OE libtool fixes to packages which fail badly at autoreconf. The fixup covers the common libtool versions 1.5, 2.2 and 2.4 and automatically determines the correct version to use.
SVN-Revision: 27855
|
|
|
|
|
|
| |
PKG_AUTOMAKE_PATHS
SVN-Revision: 26589
|
|
|
|
|
|
| |
need it, especially users of lib-link.m4 or iconv.m4
SVN-Revision: 25753
|
|
|
|
|
|
| |
PKG_MACRO_PATHS
SVN-Revision: 25312
|
|
|
|
|
|
| |
to ./m4, add LIBTOOL to AM_TOOL_PATHS
SVN-Revision: 24830
|
|
|
|
|
|
| |
libiconv stub
SVN-Revision: 24708
|
|
|
|
|
|
| |
the libtool fixup
SVN-Revision: 24700
|
|
|
|
| |
SVN-Revision: 24676
|
|
|
|
|
|
| |
makes autoreconf fail if not present, it also needs cvs which isn't installed on all hosts either
SVN-Revision: 24664
|
|
|
|
| |
SVN-Revision: 24588
|
|
|
|
|
|
| |
AMFLAGS (or any at all..)
SVN-Revision: 24574
|
|
|
|
| |
SVN-Revision: 24573
|
|
|
|
|
|
| |
libtoolize, ... to autoreconf
SVN-Revision: 24570
|
|
|
|
|
|
| |
for host build - move separator declaration to rules.mk
SVN-Revision: 24551
|
|
|
|
| |
SVN-Revision: 24547
|
|
|
|
|
|
| |
PKG_AUTOMAKE_PATHS which defaults to '.'
SVN-Revision: 24534
|
|
|
|
|
|
| |
keep the host aclocal as include path for now
SVN-Revision: 24474
|
|
|
|
| |
SVN-Revision: 24458
|
|
|
|
| |
SVN-Revision: 24434
|
|
|
|
| |
SVN-Revision: 24423
|
|
|
|
|
|
| |
applying patches and before doing any fixups
SVN-Revision: 24348
|
|
|
|
| |
SVN-Revision: 24344
|
|
|
|
| |
SVN-Revision: 24321
|
|
|
|
| |
SVN-Revision: 24320
|
|
|
|
|
|
| |
configure.in or configure.ac exists
SVN-Revision: 24319
|
|
|
|
|
|
| |
libtool fixup, this should solve a number of issues ranging from linking into the host, syntax errors in libtool and missing make targets
SVN-Revision: 24317
|
|
|
|
|
|
| |
warning. Packages must specify PKG_BUILD_DEPENDS:=libtool
SVN-Revision: 24246
|
|
|
|
|
|
| |
removed afterwards - this actually should be done within respective package-Makefiles itself, however they need to stay compatible with libtool v1.5.x which is used in backfire, since it (may) require those files
SVN-Revision: 24241
|
|
|
|
| |
SVN-Revision: 24234
|
|
|
|
| |
SVN-Revision: 22732
|
|
|
|
| |
SVN-Revision: 20570
|
|
|
|
|
|
| |
because those .la files shouldn't go there anyway.
SVN-Revision: 19785
|
|
|
|
|
|
|
|
|
|
|
| |
PKG_LIBTOOL_PATHS can be used to specify to tell libtool_fixup where to look
for libtool scripts of a package. This is useful if a package has it's libtool
script in a non-standard location or has multiple libtool scripts.
The value should be a space seperated list of paths which are relative to
$(PKG_BUILD_DIR). It defautls to $(CONFIGURE_PATH).
SVN-Revision: 19713
|
|
|
|
|
|
| |
packages which use libtool and link against packages which link against libstdc++
SVN-Revision: 19399
|
|
|
|
|
|
|
|
|
| |
was linked against libstd++ even though if it should have been linked against uclibc++. This is fixed by providing a special version of libtool fixup for packages which should use uclibc++. Not pretty but functional. Packages linking against uclibc++ should use PKG_FIXUP:=libtool-ucxx instead of PKG_FIXUP:=libtool
Somebody should probably check all packages using c++ with a dependency on stdlibc++
if uclibc++ can be used instead now.
SVN-Revision: 16317
|
|
|
|
| |
SVN-Revision: 15242
|