llvm dev - Jul 2015 - [LLVMdev] [3.7 Release] RC1 has been tagged, Testing Phase I begins

On Thu, Jul 16, 2015 at 3:47 PM, Dimitry Andric <dimitry at andric.com>
wrote:
> On 17 Jul 2015, at 00:31, Hans Wennborg <hans at chromium.org> wrote:
>>
>> Dear testers,
>>
>> 3.7.0-rc1 was just tagged; please start your testing engines :-)
>>
>> Upload binaries to the sftp and report your results to this thread.
>>
>> I'm sorry for the delay between branching and tagging. The changes
to
>> the release script took a little longer than I hoped.
>>
>> Thanks for helping with the release, and do let me know of any issues,
>> questions, etc.
>>
>> The tracking bug for release blockers is PR24126.
>
> Is it OK to do an autoconf build?  The CMake build tries to build various
components which do not yet work on FreeBSD, e.g. libcxxabi does not compile at
all, libcompiler-rt has a bunch of test failures, etc.  Alternatively, can I
disable these components in the CMake build locally?
Yes, go ahead and use the autoconf build.

Can you send a patch to test-release.sh that makes this default for
FreeBSD? It's already the default for Darwin.

Thanks,
Hans

On 17 Jul 2015, at 01:09, Hans Wennborg <hans at chromium.org>
wrote:
> 
> On Thu, Jul 16, 2015 at 3:47 PM, Dimitry Andric <dimitry at
andric.com> wrote:
>> On 17 Jul 2015, at 00:31, Hans Wennborg <hans at chromium.org>
wrote:
>>> 
>>> Dear testers,
>>> 
>>> 3.7.0-rc1 was just tagged; please start your testing engines :-)
>>> 
>>> Upload binaries to the sftp and report your results to this thread.
>>> 
>>> I'm sorry for the delay between branching and tagging. The
changes to
>>> the release script took a little longer than I hoped.
>>> 
>>> Thanks for helping with the release, and do let me know of any
issues,
>>> questions, etc.
>>> 
>>> The tracking bug for release blockers is PR24126.
>> 
>> Is it OK to do an autoconf build?  The CMake build tries to build
various components which do not yet work on FreeBSD, e.g. libcxxabi does not
compile at all, libcompiler-rt has a bunch of test failures, etc. 
Alternatively, can I disable these components in the CMake build locally?
> 
> Yes, go ahead and use the autoconf build.
> 
> Can you send a patch to test-release.sh that makes this default for
> FreeBSD? It's already the default for Darwin.
Here it is.  While here, I replaced the multiple calls to uname -s with a
variable assignment.

It's currently building for FreeBSD 10.x i386 and amd64.

-Dimitry
-------------- next part --------------
A non-text attachment was scrubbed...
Name: use-autoconf-on-freebsd-too-1.diff
Type: application/octet-stream
Size: 1278 bytes
Desc: not available
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20150719/33634fe8/attachment.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 194 bytes
Desc: Message signed with OpenPGP using GPGMail
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20150719/33634fe8/attachment.sig>

On 19 Jul 2015, at 00:17, Dimitry Andric <dimitry at andric.com>
wrote:
> 
> On 17 Jul 2015, at 01:09, Hans Wennborg <hans at chromium.org> wrote:
>> 
>> On Thu, Jul 16, 2015 at 3:47 PM, Dimitry Andric <dimitry at
andric.com> wrote:
>>> On 17 Jul 2015, at 00:31, Hans Wennborg <hans at
chromium.org> wrote:
>>>> 
>>>> Dear testers,
>>>> 
>>>> 3.7.0-rc1 was just tagged; please start your testing engines
:-)
>>>> 
>>>> Upload binaries to the sftp and report your results to this
thread.
>>>> 
>>>> I'm sorry for the delay between branching and tagging. The
changes to
>>>> the release script took a little longer than I hoped.
>>>> 
>>>> Thanks for helping with the release, and do let me know of any
issues,
>>>> questions, etc.
>>>> 
>>>> The tracking bug for release blockers is PR24126.
>>> 
>>> Is it OK to do an autoconf build?  The CMake build tries to build
various components which do not yet work on FreeBSD, e.g. libcxxabi does not
compile at all, libcompiler-rt has a bunch of test failures, etc. 
Alternatively, can I disable these components in the CMake build locally?
>> 
>> Yes, go ahead and use the autoconf build.
>> 
>> Can you send a patch to test-release.sh that makes this default for
>> FreeBSD? It's already the default for Darwin.
> 
> Here it is.  While here, I replaced the multiple calls to uname -s with a
variable assignment.
> 
> It's currently building for FreeBSD 10.x i386 and amd64.
Hm, strangely enough, this version of the script does not go further than the
Phase 2 installation, and does not run any tests?  This used to work fine for
the release_36 branch.

I think it is because of the "set -o pipefail" which was introduced,
but I don't yet understand why this causes the Phase 2 installation to
appear to fail, as there is no visible error.  I will investigate, or work
around it by removing the pipefail option again.

-Dimitry

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 194 bytes
Desc: Message signed with OpenPGP using GPGMail
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20150719/6d30f466/attachment.sig>

On Sat, Jul 18, 2015 at 3:17 PM, Dimitry Andric <dimitry at andric.com>
wrote:
> On 17 Jul 2015, at 01:09, Hans Wennborg <hans at chromium.org> wrote:
>>
>> On Thu, Jul 16, 2015 at 3:47 PM, Dimitry Andric <dimitry at
andric.com> wrote:
>>> On 17 Jul 2015, at 00:31, Hans Wennborg <hans at
chromium.org> wrote:
>>>>
>>>> Dear testers,
>>>>
>>>> 3.7.0-rc1 was just tagged; please start your testing engines
:-)
>>>>
>>>> Upload binaries to the sftp and report your results to this
thread.
>>>>
>>>> I'm sorry for the delay between branching and tagging. The
changes to
>>>> the release script took a little longer than I hoped.
>>>>
>>>> Thanks for helping with the release, and do let me know of any
issues,
>>>> questions, etc.
>>>>
>>>> The tracking bug for release blockers is PR24126.
>>>
>>> Is it OK to do an autoconf build?  The CMake build tries to build
various components which do not yet work on FreeBSD, e.g. libcxxabi does not
compile at all, libcompiler-rt has a bunch of test failures, etc. 
Alternatively, can I disable these components in the CMake build locally?
>>
>> Yes, go ahead and use the autoconf build.
>>
>> Can you send a patch to test-release.sh that makes this default for
>> FreeBSD? It's already the default for Darwin.
>
> Here it is.  While here, I replaced the multiple calls to uname -s with a
variable assignment.
>
> It's currently building for FreeBSD 10.x i386 and amd64.
Renato ran into the same problem of some components not working when
building on ARM and has a patch out for disabling them:
http://reviews.llvm.org/D11326

That might be a better approach actually. Since we didn't use to
include libcxx or libcxxabi in previous releases, feel free to disable
those (but please file bugs for the problems anyway). For compiler-rt,
we did include that in previous releases so it would be good if we
could make it work. What errors are you running into?

Thanks,
Hans