llvm dev - May 2013 - [LLVMdev] [cfe-dev] [3.3 Release] Release Candidate 2 Available

On Fri, May 24, 2013 at 4:21 PM, Bill Wendling <wendling at apple.com>
wrote:
> On May 24, 2013, at 1:19 PM, Bill Wendling <wendling at apple.com>
wrote:
>
>> Hi!
>>
>> The binaries for the 3.3 release candidate 2 are starting to role in.
Please take them and give them a go. Please file bug reports for any problems
you encounter.
>>
>> At this point, we are taking fixes only for *serious* regressions from
3.2. I will be pushing back on all requests to merge something into the 3.3
branch. In other words, you will need to do a lot to convince me that we need to
go through a third round of testing. :-)
>>
> Um...this might help. The website to get the binaries is:
>
>         http://llvm.org/pre-releases/3.3/rc2/
Please forgive my ignorance here. Filenames are not what I'm used to
seeing with past versions of Clang....

Below is the process I use to build from sources in the context of
3.2. Does clang+llvm-3.3rc2-x86.tar.gz? include everything I need? Can
I use clang+llvm-3.3rc2-x86.tar.gz, and (a): combine steps (1) and
(2); and (b): omit (4), (5), (6), and (7)?

Or do I need need to use llvm-3.3rc2-source.tar.gz and unpack
clang+llvm-3.3rc2-x86.tar.gz into llvm-3.2.src/tools/ ?

Jeff

1 wget http://llvm.org/releases/3.2/llvm-3.2.src.tar.gz
2 wget http://llvm.org/releases/3.2/clang-3.2.src.tar.gz
3 tar xvf llvm-3.2.src.tar.gz
4 cd llvm-3.2.src/tools
5 tar xvf ../../clang-3.2.src.tar.gz
6 mv clang-3.2.src clang
7 cd ..
8 ./configure --enable-optimized --prefix=/usr/local
9 make -j4

On 25 May 2013 04:59, Jeffrey Walton <noloader at gmail.com> wrote:
> 4 cd llvm-3.2.src/tools
> 5 tar xvf ../../clang-3.2.src.tar.gz
> 6 mv clang-3.2.src clang
> 7 cd ..
>
You don't need to do any of it, there are already symlinks on the llvm.src
dir to point to all others on the same root. Just unpack each source tar
ball and be happy. ;)


> 8 ./configure --enable-optimized --prefix=/usr/local
> 9 make -j4
>
Neither that. Just go into llvm.src and run ./utils/release/test-release.sh

I have written a doc on how to do that for ARM, maybe that can lead you on
the right direction:

https://wiki.linaro.org/WorkingGroups/ToolChain/LLVM/LLVMRelease

cheers,
--renato
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20130525/b906f779/attachment.html>

On Sat, May 25, 2013 at 7:51 AM, Renato Golin <renato.golin at
linaro.org>wrote:
> https://wiki.linaro.org/WorkingGroups/ToolChain/LLVM/LLVMRelease
>
>
Could you please incorporate this useful document into LLVM's official
documentation? I think that this is good content for encouraging greater
external/downstream involvement in the release process. See
docs/SphinxQuickstartTemplate.rst to get up and running fast.

Also, it's weird (possibly disingenuous) seeing linaro.org saying
"we" to
refer to the larger LLVM community (or at least that's how I understand the
"we" in "we aim to release regularly to avoid keeping stable
users away
from new features for too long").

-- Sean Silva
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20130525/82e43445/attachment.html>