buildroot.git/package/Makefile.package.in, branch master

Split Makefile.package.in in pkg-download.mk, pkg-utils.mk and pkg-gentargets.mk

2012-04-19T14:07:15+00:00

Signed-off-by: Thomas Petazzoni Signed-off-by: Peter Korsgaard

DOWNLOAD: change $1=DIRECTORY_URL, $2=FILE_NAME to $1=FULL_FILE_URL, $2=FILE_NAME

2012-03-18T21:21:16+00:00

This modifies the definition of DOWNLOAD to receive two arguments: the first one is the full URL of the file to download, whereas the second (and optional) is the name the file will have once downloaded. Same thing with the SOURCE_CHECK_WGET and SCP functions. All calls to these functions have been changed to the shortest form of the new API, except for toolchains acquisition. Since there is quite a number of different toolchains this call to DOWNLOAD is better set to the generic one. Signed-off-by: Alvaro G. M Acked-by: Arnout Vandecappelle (Essensium/Mind) Tested-by: Stephan Hoffmann Downloading Microblaze LE toolchain works on a clean install Signed-off-by: Peter Korsgaard

package: fix WGET download method

2012-03-05T19:56:28+00:00

In cf2486bf317e4bbf88c801fb96183ba62be78cc8, we changed from using the -P option of wget (to set the output *directory*) to using the -O option (to set the output *file*). Unfortunately, wget -O has a strange behaviour: it creates an empty 0-byte file even if the download fails (for example when there is no network connection). The problem is that then Buildroot thinks the download was successful and therefore goes on with extracting the tarball. The following succession of events makes Buildroot think that the download has been sucessful: * Buildroot calls the DOWNLOAD_WGET macro with the URL of the official site * It tests if the file exists in the download directory, it doesn't exist. * It calls wget. wget fails to download the file and returns an error code, but leaves an empty file with the correct name in the downloaded directory. * Since the previously download failed, Buildroot tries another download from the Buildroot mirror (sources.buildroot.net) * It tests if the file exists in the download directory... and it exists! So this second download returns with success, and Buildroot assumes the file has been downloaded properly. This scenario brings us with the following result, where the download fails, but Buildroot continues its execution and tries to extract the tarball: $ rm /opt/dl/glib-2.30.2.tar.bz2 rm: cannot remove `/opt/dl/glib-2.30.2.tar.bz2': No such file or directory $ rm -rf build/host-libglib2-2.30.2/ $ make make -C /home/thomas/projets/buildroot O=/opt/outputs/udisks/. >>> host-libglib2 2.30.2 Downloading --2012-03-03 12:06:25-- http://ftp.gnome.org/pub/gnome/sources/glib/2.30/glib-2.30.2.tar.bz2 Resolving ftp.gnome.org... failed: Name or service not known. wget: unable to resolve host address `ftp.gnome.org' >>> host-libglib2 2.30.2 Extracting bzcat /opt/dl//glib-2.30.2.tar.bz2 | tar --strip-components=1 -C /opt/outputs/udisks/build/host-libglib2-2.30.2 -xf - bzcat: Compressed file ends unexpectedly; perhaps it is corrupted? *Possible* reason follows. [...] tar: This does not look like a tar archive tar: Exiting with failure status due to previous errors make[1]: *** [/opt/outputs/udisks/build/host-libglib2-2.30.2/.stamp_extracted] Error 2 make: *** [all] Error 2 $ ls -l /opt/dl/glib-2.30.2.tar.bz2 -rw-r--r-- 1 thomas thomas 0 Mar 3 12:12 /opt/dl/glib-2.30.2.tar.bz2 Therefore, this commit modifies DOWNLOAD_WGET so that it removes the downloaded file if wget returns with an error. Signed-off-by: Thomas Petazzoni Acked-by: Luca Ceresoli Signed-off-by: Peter Korsgaard

DOWNLOAD_WGET: use -O instead of -P to set output file

2012-02-14T11:07:27+00:00

Some URLs use url-encoded arguments to specify the file to download. Wget will then use an output file name which includes all the ampersands and such. However, this is not what we see from buildroot. E.g.: FOO_SITE="http://git.foo.com/?p=foo.git;a=blob;f=" FOO_SOURCE="foo.tgz" wget will download this into $(DL_DIR)/index.html?p=foo.git;a=blob;f=foo.tgz buildroot thinks it's in $(DL_DIR)/foo.tgz To make sure the view of wget and buildroot are consistent, specify the output file explicitly. Signed-off-by: Arnout Vandecappelle (Essensium/Mind) Signed-off-by: Peter Korsgaard

dependencies: build a host-tar if no suitable tar can be found

2012-02-09T21:59:21+00:00

Some toolchains, like the one built with buildroot itself, use hardlinks (for example to link between the c++ and g++ binary). Unpacking such a toolchain with the --strip-components options does not work correctly if the system tar is too old (<1.17). Even recent releases of RedHat/CentOS still ship with tar 1.15. This patch checks for a suitable tar version (tar 1.17+) on the host system, and adds host-tar to the host dependencies if none can be found. host-tar is download and extracted as cpio.gz instead of tar.gz, to prevent chicken-egg problem. Signed-off-by: Thomas De Schampheleire v4 Acked-by: Arnout Vandecappelle (Essensium/Mind) Signed-off-by: Peter Korsgaard

pkg-infra: improve reliability of foo-install

2012-02-02T21:52:35+00:00

Running foo-uninstall has a high likelyhood of failing, because we remove a lot of directories from the target. To improve the reliability, remove the stamp files before calling the uninstall commands, and add the -k option to the sub-make. Signed-off-by: Arnout Vandecappelle (Essensium/Mind) Signed-off-by: Peter Korsgaard

Add support for package-declared devices

2012-02-01T21:55:49+00:00

Add a way for packages to declare files they need instead of relying only on device tables, which creates files no matter if the package is indeed enabled, as we can see for busybox. Signed-off-by: Maxime Ripard Acked-by: Thomas De Schampheleire Acked-by: Arnout Vandecappelle (Essensium/Mind) Signed-off-by: Peter Korsgaard

Only derrive HOST_FOO_DEPENDENCIES from FOO_DEPENDENCIES if not set, not nonempty

2012-01-18T15:02:51+00:00

In make, ifndef VAR means if 'VAR is not set to the empty string', and NOT 'VAR is not defined', which meant that you couldn't specify empty FOO_HOST_DEPENDENCIES. Signed-off-by: Peter Korsgaard

package: derive HOST_FOO_DEPENDENCIES from FOO_DEPENDENCIES

2012-01-17T22:28:47+00:00

Signed-off-by: Arnout Vandecappelle (Essensium/Mind) Signed-off-by: Peter Korsgaard

dependencies: check for extract tools as well

2011-12-04T19:27:21+00:00

Most of the extract tools (gzip/bzip/..) we already check for explicitly in dependencies.sh (as they are used outside GENTARGETS), but not for xzcat. The .xz format is used fairly rarely, and it is likely to not be available on build hosts, so an explicit (hardcoded) check for it isn't optimal. Instead, add the inflate tools used to DL_TOOLS_DEPENDENCIES, similar to how we do it for svn/git/bzr/... Signed-off-by: Peter Korsgaard