Displaying 4 results from an estimated 4 matches for "fambox".
2016 Feb 24
3
[3.8 Release] RC3 has been tagged
[ Original posting see [1] ]
>From [1]:
...
Added:
llvm/tags/RELEASE_380/rc3/ (props changed)
- copied from r261685, llvm/branches/release_38/
...
The LLVM Git repositories have no "rc3" tag in "release_38" branch (as
an example llvm.git#release_38 see [2]).
Who is responsible for that or maybe better... can you activate the
responsible(s)?
Helpful is to add
2016 Feb 08
2
[LLVM v3.8-rc2] New (tar)balls, please?
On Sat, Feb 6, 2016 at 12:34 AM, Sedat Dilek <sedat.dilek at gmail.com> wrote:
> On Sat, Feb 6, 2016 at 1:55 AM, Hans Wennborg <hans at chromium.org> wrote:
>> On Fri, Feb 5, 2016 at 8:43 AM, Hans Wennborg <hans at chromium.org> wrote:
>>> On Fri, Feb 5, 2016 at 12:48 AM, Sedat Dilek <sedat.dilek at gmail.com> wrote:
>>>> sorry, but I cannot
2016 Jun 27
0
[LLVM/Clang v3.8.1] Missing Git branches/tags and source-tarballs?
On Mon, Jun 27, 2016 at 9:39 AM, Hahnfeld, Jonas
<Hahnfeld at itc.rwth-aachen.de> wrote:
> Please have a look at the dedicated mailing list:
> http://lists.llvm.org/pipermail/llvm-branch-commits/
>
OK, I clicked the offline version of that ML on the main-page of
<llvm.org>, so I knew of it.
Anyway, I think most people use Git these days.
> Please wait for the official
2016 Jun 27
5
[LLVM/Clang v3.8.1] Missing Git branches/tags and source-tarballs?
Please have a look at the dedicated mailing list:
http://lists.llvm.org/pipermail/llvm-branch-commits/
Please wait for the official release to happen, you will then find tarballs on
llvm.org. They will also contain correct version strings, though I haven't yet
tried building from the SVN branches directly. Maybe you need to use the SVN
tags, $ clang --version currently gives me "clang