[Release-testers] [4.0.0 Release] Release Candidate 1 source and binaries available

[Mehdi Amini via Release-testers]

I don’t think it is build setup problem: it is likely an incompatible change made in libc++. I haven’t had a chance to catch Justin yet to talk about it but possible this afternoon.

Félix: feel free to CC me on the PR if you file it.

Thanks,

— 
Mehdi

> On Jan 26, 2017, at 8:43 AM, Hans Wennborg <hans at chromium.org> wrote:
> 
> Félix, can you file a bug about this as a blocker of
> http://llvm.org/pr31622 ? Even if it turns out to be a build setup
> problem, it would be good to track it there.
> 
> Thanks,
> Hans
> 
> On Wed, Jan 25, 2017 at 6:58 PM, Félix Cloutier <felixcca at yahoo.ca> wrote:
>> Well, to be clear, there are 200ish occurrences of it from a clean build.
>> I'm building with the libc++ version that ships with Xcode 8.2.1. With it, I
>> could build my project against LLVM 3.9 without issues.
>> 
>> Should I be building with a different libc++?
>> 
>> Félix
>> 
>> Le 25 janv. 2017 à 09:45, Mehdi Amini <mehdi.amini at apple.com> a écrit :
>> 
>> Hi,
>> 
>> There has been a change in the libc++ header about  __call_once_proxy
>> visibility, I suspect this is not a clean build?
>> 
>> Otherwise it means that your foo.o didn’t use the same libc++ headers as the
>> one used to build libLLVMAnalysis.a.
>> 
>> —
>> Mehdi
>> 
>> 
>> 
>> On Jan 24, 2017, at 8:46 PM, Félix Cloutier via Release-testers
>> <release-testers at lists.llvm.org> wrote:
>> 
>> Hello,
>> 
>> I've switched a project from LLVM 3.9.0 to LLVM 4.0.0 RC1 and I'm seeing a
>> ton of these:
>> 
>> ld: warning: direct access in function
>> 'llvm::initializeExternalAAWrapperPassPass(llvm::PassRegistry&)' from file
>> '/Users/.../Projets/clang+llvm-4.0.0-rc1-x86_64-apple-darwin/lib/libLLVMAnalysis.a(AliasAnalysis.cpp.o)'
>> to global weak symbol 'void
>> std::__1::__call_once_proxy<std::__1::tuple<void* (&)(llvm::PassRegistry&),
>> std::__1::reference_wrapper<llvm::PassRegistry>&&> >(void*)' from file
>> '/Users/.../Library/Developer/Xcode/DerivedData/fcd-aagtzwcwgbftbkcrfnkqbgvqpfbm/Build/Intermediates/.../Objects-normal/x86_64/foo.o'
>> means the weak symbol cannot be overridden at runtime. This was likely
>> caused by different translation units being compiled with different
>> visibility settings.
>> 
>> I don't think that I've changed debug settings very much between the two
>> releases. Has something changed in LLVM's build settings?
>> 
>> I'm testing the macOS release.
>> 
>> Félix
>> 
>> Le 23 janv. 2017 à 15:01, Hans Wennborg via Release-testers
>> <release-testers at lists.llvm.org> a écrit :
>> 
>> Source, binaries and docs for LLVM-4.0.0-rc1 are now available at
>> http://www.llvm.org/pre-releases/4.0.0/#rc1
>> 
>> Please try it out, run tests, build your favourite projects and file
>> bugs about anything that doesn't work and needs to be fixed before the
>> release, marking them as blockers of http://llvm.org/pr31622.
>> 
>> Thanks,
>> Hans
>> _______________________________________________
>> Release-testers mailing list
>> Release-testers at lists.llvm.org
>> http://lists.llvm.org/cgi-bin/mailman/listinfo/release-testers
>> 
>> 
>> _______________________________________________
>> Release-testers mailing list
>> Release-testers at lists.llvm.org
>> http://lists.llvm.org/cgi-bin/mailman/listinfo/release-testers
>> 
>> 
>>