llvm dev - Jul 2015 - [LLVMdev] [cfe-dev] 3.6.2-rc1 has been tagged. Testers needed.

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

clang+llvm-3.6.2-rc1-mipsel-linux-gnu.tar.xz
    One test-suite run passed. One still running.

clang+llvm-3.6.2-rc1-x86_64-linux-gnu-ubuntu-14.04.tar.xz (cross compiling to
various mips)
    All good.
________________________________________
From: Tom Stellard [tom at stellard.net]
Sent: 24 June 2015 01:17
To: llvmdev at cs.uiuc.edu
Cc: cfe-dev at cs.uiuc.edu
Subject: 3.6.2-rc1 has been tagged.  Testers needed.

Hi,

I have just tagged 3.6.2-rc1, so testing can begin.  We can always use
more testers, so if you are interested in testing, let me know.

-Tom

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?

Thanks,
Dan.

Hi,

I've taken a look at the binary tarballs for clang+llvm-3.6.2-rc1-*
that have been uploaded and observed the following:

* All uploaded tarballs include the generated CMake files apart from
``clang+llvm-3.6.2-rc1-x86_64-linux-gnu-ubuntu-14.04.tar.xz``.
  These files (share/llvm/cmake/*.cmake) are missing in this tarball.

* Inside the Ubuntu tarball the directory is not consistently named
compared to the other tarballs. For example inside
``clang+llvm-3.6.2-rc1-x86_64-fedora21.tar.xz``
there is 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 ``include/llvm/Config/llvm-config.h``. It
contains paths that are almost certainly not going to exist on a
user's system. The patch will replace the temporary install directory
in files like these with ``/usr/local`` but will still place files in
the temporary install directory for tarballing.


@Ben Pope: Your uploaded binary tarball is the odd one out. Any idea
as to why the CMake files are missing and why the root directory name
inside the tarball is not consistent with the uploaded tarballs for
other platforms?

[1]
http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20150629/285597.html

Hi Tom,

On 1 July 2015 at 09:38, Dan Liew <dan at su-root.co.uk>
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
Just to note. If you were thinking of applying r240981, please hold
off for now. There appear to be some issues with it that need to be
resolved.

Thanks,
Dan.

On 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.