summaryrefslogtreecommitdiffstats
path: root/llvm/utils/release/test-release.sh
Commit message (Collapse)AuthorAgeFilesLines
* test-release.sh: Add ability to do a test build using the trunk or branches.Daniel Sanders2015-07-171-3/+19
| | | | | | | | | | | | | | | | | | | | | Summary: Adds '--svn-path BRANCH' that causes the script to export the specified path from each project. Otherwise the tag specified by -release, -rc, etc. will be used. The version portion of the package name will be 'test-$path' (any forward slashes in the branch name are replaced with underscores), for example: -svn-path trunk => clang+llvm-test-trunk-mips-linux-gnu.tar.xz -svn-path branches/release_35 => clang+llvm-test-branches_release_35-mips-linux-gnu.tar.xz This is primarily useful for bringing new release packages up to standard without needing to create and maintain a tag for the purpose. Reviewers: tstellarAMD, hans Subscribers: llvm-commits Differential Revision: http://reviews.llvm.org/D6563 llvm-svn: 242518
* test-release.sh: Run both .o files through sed before comparing themHans Wennborg2015-07-151-3/+4
| | | | | | | | | | On some systems (e.g. Mac OS X), sed will add a newline to the end of the output if there wasn't one already. This would cause false cmp errors since the .o file from Phase 2 was passed through sed and the one from Phase 3 wasn't. Work around this by passing both through sed. llvm-svn: 242341
* Switch the release script to build with CMake by default (PR21561)Hans Wennborg2015-07-151-48/+66
| | | | | | | | | | | | | | | | | | | | It retains the possibility to use the autoconf build with a command-line option ('-use-autoconf'), and uses that by default on Darwin since compiler-rt requires it on that platform. This commit also removes the "Release-64" flavour and related logic. The script would previously do two builds unless the '-no-64bit' flag was passed, but on my machine and from those I asked this always ended up producing two 64-bit builds, causing much confusion. It also removes the -build-triple option, which caused the --build= flag to get passed to ./configure. This was presumably intended for cross-compiling, but none of the release testers use it. If someone does want to pass it, they can use '-configure-flags --build=foo' instead. Differential Revision: http://reviews.llvm.org/D10715 llvm-svn: 242331
* test-release.sh: Remove the InstallDir parameter from configure_llvmCoreHans Wennborg2015-07-141-16/+5
| | | | | | After r242187, it's never set. llvm-svn: 242194
* Fix several issues with the test-release.sh scriptDan Liew2015-07-141-68/+63
| | | | | | | | | | | | | | | | | | | * Use the default install prefix (/usr/local) and use DESTDIR instead to set a temporary install location for tarballing. This is the correct way to package binary releases (otherwise the temporary install path ends up in files in the binary release). * Remove ``-disable-clang`` option. It did not work correctly (tarballing assumed phase 3 was run) and when doing a release we should always be doing a three-phased build and test. Note: Technically we should only be using DESTDIR for the third phase and use --prefix for the first and second phase because we run the built clang from phase 1 and 2 (and in general an application's behaviour may depend on the install prefix). However in the case of clang it seems to not care what the install prefix was so to simplify the script we use DESTDIR for all three stages. llvm-svn: 242187
* Fix bug in test-release.sh where the script would not exit if anyDan Liew2015-07-071-1/+5
| | | | | | | | | | | | | | of the build stages that are sent through a pipe (e.g. tee) failed. This potentially allowed builds and/or tests to fail without anyone noticing. It appears that for the LLVM 3.6.[01] releases this actually happened for the Ubuntu 14.04LTS binary releases. The essence of the issue is that without ``set -o pipefail`` the following command in bash has a zero exit code. false | tee /dev/null ; exit $? llvm-svn: 241599
* test-release.sh: Minor fixes.Hans Wennborg2015-06-221-6/+3
| | | | llvm-svn: 240334
* Drop remaining Dragonegg support in release scriptsHans Wennborg2015-06-011-12/+0
| | | | | | | | | | r236077 and r236081 dropped Dragonegg support from the release scripts but left some pieces. The most notable change is that Dragonegg won't be tagged any more. Patch by David Wiberg <dwiberg@gmail.com>. llvm-svn: 238753
* Drop Dragonegg support from the release scriptHans Wennborg2015-04-291-113/+2
| | | | | | | | | It doesn't have a maintainer and none of the release testers test it, so I don't think it should be part of the release. http://reviews.llvm.org/D9331 llvm-svn: 236077
* test-release.sh: Drop some unused command-line options.Hans Wennborg2015-04-281-12/+0
| | | | | | These haven't done anything since before r142165. llvm-svn: 236061
* test-release.sh: Add a way to specify --build to configureDaniel Sanders2014-12-041-18/+29
| | | | | | | | | | | | | | | | Summary: I currently have to specify --build=mips-linux-gnu or --build=mipsel-linux-gnu to configure in order to successfully recurse a 32-bit build of the compiler on my mips64-linux-gnu and mips64el-linux-gnu targets. This is a bug and will be fixed but in the meantime it will be useful to have a way to work around this. Reviewers: tstellarAMD Subscribers: llvm-commits Differential Revision: http://reviews.llvm.org/D6522 llvm-svn: 223369
* test-release.sh: Correct the logged configure command to match the one ↵Daniel Sanders2014-12-041-1/+2
| | | | | | | | | actually issued. --disable-timestamps was added to the configure command way back in r142647 but the command that echos this command to the log was not updated at the time. llvm-svn: 223351
* Update projects lists.Bill Wendling2014-08-201-1/+4
| | | | llvm-svn: 216048
* test-release.sh: Add support for dot releasesTom Stellard2014-07-211-1/+1
| | | | llvm-svn: 213580
* Display the name of the project failing the url check in the release scriptArnaud A. de Grandmaison2014-04-141-1/+1
| | | | llvm-svn: 206164
* Remove superfluous label.Bill Wendling2013-12-031-1/+1
| | | | llvm-svn: 196227
* Default to a better compression algorithm.Bill Wendling2013-11-241-2/+15
| | | | llvm-svn: 195567
* Add -triple option.Bill Wendling2013-11-201-3/+38
| | | | | | | | The -triple option is used to create a named tarball of the release binaries. Also disable the RPATH modifications on Mac OS X. It's not needed. llvm-svn: 195193
* test-release.sh: tweak RPATH for the binary packages.Arnaud A. de Grandmaison2013-11-181-0/+32
| | | | | | | | libtool sets RPATH to "$ORIGIN/../lib:/the/directory/where/it/was/built/lib" so that a developper can use the built or the installed version seamlessly. Our binary packages should not have this developer friendly tweak, as the users of the binaries will not have the build tree. Beside, in case the development tree is a possibly on an automounted share, this can create very bad user experience : they will incur an automount timeout penalty and will get a very bad feeling of llvm/clang's speed. llvm-svn: 194999
* Correct comment.Duncan Sands2013-07-101-1/+1
| | | | llvm-svn: 185987
* Add libcxx and clang-tools-extra to the testing thing.Bill Wendling2013-05-081-3/+10
| | | | llvm-svn: 181418
* Fix a typo (the the => the)Sylvestre Ledru2012-07-231-1/+1
| | | | llvm-svn: 160621
* Download and build the compiler-rt project.Bill Wendling2012-04-171-1/+4
| | | | llvm-svn: 154905
* As Eric pointed out, even a Debug build should be equal. Leave the flag that ↵Bill Wendling2012-04-031-10/+8
| | | | | | can turn off comparisons though. llvm-svn: 153927
* Compare the .o files only for release builds. Add an option to bypass the ↵Bill Wendling2012-04-021-16/+26
| | | | | | comparison altogether. llvm-svn: 153909
* Support a 'final' release candidate tag.Bill Wendling2011-11-281-23/+27
| | | | llvm-svn: 145243
* Do a relative path ln command instead of an absolute path one. Some people ↵Bill Wendling2011-10-291-2/+2
| | | | | | strangely enough have different directory layouts... llvm-svn: 143302
* Ensure timestamps are not embedded into files when doing a release build.Duncan Sands2011-10-211-0/+1
| | | | llvm-svn: 142647
* Also compare the built dragonegg objects between phases 2 and 3.Duncan Sands2011-10-201-1/+2
| | | | llvm-svn: 142608
* Reset the system compiler each time we start a new flavour. OtherwiseDuncan Sands2011-10-201-2/+3
| | | | | | | | | | the last compiler built for the previous flavour is used for the next, for example the Debug clang compiler was being used for the initial build of the Release LLVM. Flavors should be independent of each other. This especially matters if the compiler built for the previous flavour doesn't actually work! llvm-svn: 142607
* Add support for testing dragonegg. This is disabled by default.Duncan Sands2011-10-201-37/+174
| | | | | | | In fact this commit is not intended to change anything unless you use one of the new command line flags. llvm-svn: 142577
* Duncan pointed out that sometimes CC and CXX are used to specify the ↵Bill Wendling2011-10-191-20/+2
| | | | | | compiler. Also that the configure script takes care of finding an appropriate compiler if one's not specified. llvm-svn: 142489
* Use bash instead.Bill Wendling2011-10-191-1/+1
| | | | llvm-svn: 142486
* Make changes so that this runs on FreeBSD.Bill Wendling2011-10-191-7/+13
| | | | llvm-svn: 142482
* Don't exit just because some early commands fail. Use the -k flag when ↵Bill Wendling2011-10-181-4/+6
| | | | | | running the checks. llvm-svn: 142369
* Forgot to add the project name to the 'svn ls' command.Bill Wendling2011-10-171-1/+1
| | | | llvm-svn: 142282
* Don't download and compile compiler-rt, libcxx, and libcxxabi by default.Bill Wendling2011-10-171-2/+2
| | | | llvm-svn: 142185
* Update to disable asserts. Build a phase 3 compiler, and compare phase 2 ↵Bill Wendling2011-10-171-2/+40
| | | | | | files against phase 3. llvm-svn: 142173
* Overhaul the 'test-release' script.Bill Wendling2011-10-161-158/+96
| | | | | | | This removes support for building llvm-gcc. It will eventually add support for building other projects. llvm-svn: 142165
* Partially revert commit 127155: I think it is much more convenientDuncan Sands2011-03-271-9/+26
| | | | | | | to have structured log files rather than one big file produced by piping output. llvm-svn: 128378
* Don't show commands.Bill Wendling2011-03-081-1/+0
| | | | llvm-svn: 127224
* Don't keep the log files around. Just pipe to a log file instead.Bill Wendling2011-03-071-31/+15
| | | | llvm-svn: 127155
* Release-Asserts no longer exists.Duncan Sands2010-09-151-1/+1
| | | | llvm-svn: 113965
* Nowadays a release build has assertions off.Duncan Sands2010-09-131-3/+3
| | | | llvm-svn: 113747
* This script is executable.Duncan Sands2010-09-091-0/+0
| | | | llvm-svn: 113479
* Remove --with-gxx-include-dir option because it's causing problems on ↵Bill Wendling2010-09-081-3/+1
| | | | | | non-Darwin platforms. llvm-svn: 113401
* Add an option to not test ObjC for those platforms which don't support it.Bill Wendling2010-09-081-1/+9
| | | | llvm-svn: 113398
* Correct variable name.Duncan Sands2010-09-081-1/+1
| | | | llvm-svn: 113395
* Move the number of cpus logic to somewhere more logical.Duncan Sands2010-09-081-9/+10
| | | | llvm-svn: 113393
* A script that tests a certain release candidate in several modes. It does aBill Wendling2010-09-081-0/+391
2-phase build of llvm and llvm-gcc, similar to what the buildbots do, and runs the regression testsuite. Things to do: - Work out some bugs with llvm-gcc flags. - Not all platforms support ObjC. - Run the test-suite. llvm-svn: 113382
OpenPOWER on IntegriCloud