search for: r241080

...Wed, Jul 01, 2015 at 09:38:15AM -0700, Dan Liew wrote: > Hi Tom, > > I'd like to backport some fixes in LLVM trunk to the 3.6 branch. These > changes only effect the generation of CMake files and should not > change the generated binaries. The changes are > > r240981 > r241080 > > which need to be applied in order. > > Is this okay? > No, it is too late to backport fixes. I'm about to tag 3.6.2 -final. -Tom > Thanks, > Dan.

clang+llvm-3.6.2-rc1-mipsel-linux-gnu.tar.xz The second test run finally finished (the machine lacks an FPU). All good. ________________________________________ From: Daniel Sanders Sent: 28 June 2015 18:51 To: Tom Stellard; llvmdev at cs.uiuc.edu Cc: cfe-dev at cs.uiuc.edu Subject: RE: 3.6.2-rc1 has been tagged. Testers needed. clang+llvm-3.6.2-rc1-mips-linux-gnu.tar.xz All good

Hi, @CC'ing Hans because this will likely be of interest to you. Right I've started trying to build LLVM inside an Ubuntu chroot (Ubuntu 14.04LTS Docker image) and I've already come across a pretty bad bug in the ``test-release.sh`` script which potentially means that builds and/or tests could potentially fail without anyone noticing (unless someone carefully looks through the logs)

...a directory named ``clang+llvm-3.6.2-rc1-x86_64-fedora21``. Inside ``clang+llvm-3.6.2-rc1-x86_64-linux-gnu-ubuntu-14.04.tar.xz`` the directory is named ``clang+llvm-3.6.2-rc1-x86_64-linux-gnu``. * In the tarballs that do include the CMake files they are broken because they contain absolute paths. r241080 needs to be back ported in order to fix this. * All tarballs are packaged incorrectly because --prefix is being misused by ``test-release.sh``. I have a patch for this [1] which is awaiting review (look at V2, the original patch doesn't work). You can observe this by taking a look at ``inclu...