insight GDB version 6.8-1 sources have apparently changed.
The original file is no longer available upstream.
Signed-off-by: Daniel Golle <dgolle@allnet.de>
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@32438 3c298f89-4303-0410-b956-a3cf2f4a3e73
When selecting a specific eglibc version, it comes with a specific SVN
revision that should not be modified as it (more or less) correspond to
a tagged release. This patch disable the possibility to select a specific
SVN revision on known eglib versions.
This patch also disables the possibility to select the trunk branch of
eglibc. There are multiple reasons for that:
* trunk/HEAD may not even compile
* the OpenWrt built system makes using trunk/HEAD a difficult thing, as
OpenWRT fetches the source tree and store it in a compressed tar archive.
Subsequent build get the source from the tar archive - not from SVN,
making the use of trunk/HEAD largelly innefective.
* we cannot know the corresponding version of trunk/HEAD, meaning that
we'll face compiling issues when we'll try to copy the libc files -
unless the build system is fixed with this specific issue in mind.
Signed-off-by: Emmanuel Deloget <logout@free.fr>
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@31502 3c298f89-4303-0410-b956-a3cf2f4a3e73
eglibc version number depends on the branch and on the maintenance release
(i.e. the SVN revision). Changing the revision may change the maintenance
version. This patch correlate the SVN revision to the correct version
number - without this change eglibc 2.14 provoke build errors when
building the base-files package (example, for 2.14):
$ make package/base-files/compile V=1
make[1] package/base-files/compile
make[2] -C package/opkg host-compile
make[2] -C package/base-files-network compile
make[2] -C package/base-files compile
cp: cannot stat `/home/me/openwrt/trunk/staging_dir/toolchain-arm_v7-a_gcc-4.6-linaro_eglibc-trunk_eabi/lib/ld-2.14.so': No such file or directory
Signed-off-by: Emmanuel Deloget <logout@free.fr>
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@31501 3c298f89-4303-0410-b956-a3cf2f4a3e73
Mentioned patch got obsoleted by commit 31300, since it went upstream meanwhile
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@31341 3c298f89-4303-0410-b956-a3cf2f4a3e73
in particular this solves the issue that eglibc version 2.x produced so-files having the version string 2.(x-1) in its names which confused the toolchain
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@31300 3c298f89-4303-0410-b956-a3cf2f4a3e73
Patch up OpenWrts own cross toolchains to always search headers
and libraries in $STAGING_DIR, this should solve most issues with
missing headers, indirect linking and not found libraries.
At a later stage, all -I and -L flags will be purged from
TARGET_LDFLAGS and TARGET_CPPFLAGS.
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@29768 3c298f89-4303-0410-b956-a3cf2f4a3e73
Use ext-toolchain.sh to wrap external toolchain commands,
abort build if certain features such as CONFIG_SOFT_FLOAT or
CONFIG_IPV6 are enabled but not supported by the toolchain.
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@29766 3c298f89-4303-0410-b956-a3cf2f4a3e73
Currently we always assume uClibc if an external toolchain is used, this breaks for non-uClibc toolchains or
even vanilla uClibc ones since they do not share the external librpc semantics as OpenWrt. Solve the problem
by defining an abstract "EXTERNAL_LIBC" which packages might or might not depend on.
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@29689 3c298f89-4303-0410-b956-a3cf2f4a3e73
