scripts/functions: svn retrieval first tries the mirror for tarballs
The svn download helper looks for the local tarballs dir to see if it
can find a pre-downloaded tarball, and if it does not find it, does
the actual fetch to upstream via svn.
In the process, it does not even try to get a tarball from the local
mirror, which can be useful if the mirror has been pre-populated
manually (or with a previously downloaded tree).
Fake a tarball get with the standard tarball-download helper, but
without specifying any upstream URL, which makes the helper directly
try the LAN mirror.
Of course, if no mirror is specified, no URL wil be available, and
the standard svn retrieval will kick in.
Reported-by: ANDY KENNEDY <ANDY.KENNEDY@adtran.com>
Signed-off-by: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
1 File.........: 0 - Table of content.txt
2 Copyright....: (C) 2010 Yann E. MORIN <yann.morin.1998@anciens.enib.fr>
3 License......: Creative Commons Attribution Share Alike (CC-by-sa), v2.5
12 - Referring to crosstool-NG
14 2- Installing crosstool-NG
17 - Preparing for packaging
21 3- Configuring a toolchain
22 - Interesting config options
23 - Re-building an existing toolchain
24 - Using as a backend for a build-system
26 4- Building the toolchain
27 - Stopping and restarting a build
28 - Testing all toolchains at once
29 - Overriding the number of // jobs
33 5- Using the toolchain
34 - The 'populate' script
37 - Seemingly-native toolchains
40 - Sending a bug report
46 - Architecture-specific
47 - Adding a new version of a component
50 9 - How is a toolchain constructed?
51 - I want a cross-compiler! What is this toolchain you're speaking about?
52 - So, what are those components in a toolchain?
53 - And now, how do all these components chained together?
54 - So the list is complete. But why does crosstool-NG have more steps?
59 - gcc is not found, although I *do* have gcc installed
60 - The extract and/or path steps fail under Cygwin
61 - uClibc fails to build under Cygwin
62 - On 64-bit build systems, the glibc (possibly eglibc too) build
63 fails for 64-bit targets, because it can not find libgcc
64 - libtool.m4: error: problem compiling FC test program
65 - unable to detect the exception model
66 - configure: error: forced unwind support is required
67 - glibc start files and headers fail with: [/usr/include/limits.h] Error 1
70 - Using crosstool-NG on FreeBSD (and other *BSD)
71 - Using crosstool-NG on MacOS-X
72 - Using Mercurial to hack crosstool-NG