Re: [Mono-dev] Git error 14090086 when pulling Mono source
Hi, On Wed, 19 Oct 2011 16:05:37 -0700 (PDT), "Lee V. Andrus" wrote: > Please help. I receive the following error message when trying to do a git > pull of the Mono source: > > mono $ git pull > error: SSL certificate problem, verify that the CA cert is OK. Details: > error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify > failed while accessing https://github.com/mono/mono.git/info/refs > > fatal: HTTP request failed > mono $ > > I believe I have pulled from that repository in the past, but have not > tried > recently. I definitely was able to clone the repository. Is this a > certificate that is supposed to be with the repository or on my computer? > Currently I am only interested in read access to the repository. The error message indicates that the SSL certificate from github has problems. Usually SSL problems can be traced to one of the following causes: * Stupid attacker * Broken proxy * local time skew * broken local installation * error at github I could access https://github.com just now and was presented a certificate from DigiCert with the SHA1 Fingerprint CE:67:99:25:2C:AC:78:12:7D:94:B5:62:2C:31:C5:16:A6:34:73:53, valid from 05/27/2011 thru 07/29/2013. Best Regards, David ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] LLVM with current Mono
Hi, You should use the branch in the LLVM repo corresponding to your mono version, i.e. mono-2-10. Zoltan 2011/10/19 Konrad M. > Hi, > which branch of mono's LLVM repository should I use to compile mono > 2.10.6 with --enabled-llvm? mono-2-10 one gives me: > mini-llvm-cpp.cpp: In function ‘LLVMOpaqueExecutionEngine* > mono_llvm_create_ee(LLVMOpaqueModuleProvider*, unsigned char* > (*)(LLVMOpaqueValue*, int), void (*)(LLVMOpaqueValue*, void*, void*), > void (*)(void*))’: > mini-llvm-cpp.cpp:469: error: cannot allocate an object of abstract type > ‘MonoJITMemoryManager’ > mini-llvm-cpp.cpp:59: note: because the following virtual functions > are pure within ‘MonoJITMemoryManager’: > /usr/include/llvm/ExecutionEngine/JITMemoryManager.h:115: note: > virtual > void llvm::JITMemoryManager::deallocateFunctionBody(void*) > /usr/include/llvm/ExecutionEngine/JITMemoryManager.h:131: note: > virtual > void llvm::JITMemoryManager::deallocateExceptionTable(void*) > > Regards, > Konrad > > ___ > Mono-devel-list mailing list > Mono-devel-list@lists.ximian.com > http://lists.ximian.com/mailman/listinfo/mono-devel-list > ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] LLVM with current Mono
Hi Zoltan, 2011/10/20 Zoltan Varga : > Hi, > You should use the branch in the LLVM repo corresponding to your mono > version, > i.e. mono-2-10. > Zoltan > Generally it was what I did. Specifically: LLVM from mono-2-10 branch, last commit ab6947203a665efa0d7676f19cabf2fa70e3af60 configured with: ./configure --enable-optimized --enable-targets="x86 x86_64" --prefix=/usr/ Mono 2.10.5 tarball from mono site. Configured with: ./configure --prefix=/usr/ --enable-llvm=yes LLVM compilation went fine, hovewer Mono's ended with error attached in previous message. -- Regards, Konrad ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] LLVM with current Mono
Hi, I can't reproduce this. Zoltan 2011/10/20 Konrad Kruczyński > Hi Zoltan, > > 2011/10/20 Zoltan Varga : > > Hi, > > You should use the branch in the LLVM repo corresponding to your mono > > version, > > i.e. mono-2-10. > > Zoltan > > > > Generally it was what I did. Specifically: > LLVM from mono-2-10 branch, last commit > ab6947203a665efa0d7676f19cabf2fa70e3af60 > configured with: > ./configure --enable-optimized --enable-targets="x86 x86_64" --prefix=/usr/ > Mono 2.10.5 tarball from mono site. Configured with: > ./configure --prefix=/usr/ --enable-llvm=yes > LLVM compilation went fine, hovewer Mono's ended with error attached > in previous message. > > -- > Regards, > Konrad > ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] Git error 14090086 when pulling Mono source
But is there something I can do about it, and how can I tell? I also can access github (even the specific URL) without an error message in the Safari web browser. I have some local changes to preserve that would complicate trashing and re-cloning my local repository. I did a "git fsck" in the local repository. After a few hours it produced only a long list of "dangling commits". David Schmitt wrote: > > Hi, > > On Wed, 19 Oct 2011 16:05:37 -0700 (PDT), "Lee V. Andrus" >wrote: >> error: SSL certificate problem, verify that the CA cert is OK. Details: >> error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate > verify >> failed while accessing https://github.com/mono/mono.git/info/refs > > > The error message indicates that the SSL certificate from github has > problems. Usually SSL problems can be traced to one of the following > causes: > * Stupid attacker > * Broken proxy > * local time skew > * broken local installation > * error at github > > I could access https://github.com just now and was presented a certificate > from DigiCert with the SHA1 Fingerprint > CE:67:99:25:2C:AC:78:12:7D:94:B5:62:2C:31:C5:16:A6:34:73:53, valid from > 05/27/2011 thru 07/29/2013. > -- View this message in context: http://mono.1490590.n4.nabble.com/Git-error-14090086-when-pulling-Mono-source-tp3920419p3923467.html Sent from the Mono - Dev mailing list archive at Nabble.com. ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] Git error 14090086 when pulling Mono source
On 20.10.2011 23:22, Lee V. Andrus wrote: > But is there something I can do about it, and how can I tell? > I also can access github (even the specific URL) without an error message in > the Safari web browser. I have some local changes to preserve that would > complicate trashing and re-cloning my local repository. I did a "git fsck" > in the local repository. After a few hours it produced only a long list of > "dangling commits". Did you bother to search the interwebs for "Git error 14090086"? The first Google hit contains the solution... For the impatient: http://stackoverflow.com/questions/3777075/https-github-access/4454754#4454754 Robert > > > David Schmitt wrote: >> >> Hi, >> >> On Wed, 19 Oct 2011 16:05:37 -0700 (PDT), "Lee V. Andrus" >>wrote: >>> error: SSL certificate problem, verify that the CA cert is OK. Details: >>> error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate >> verify >>> failed while accessing https://github.com/mono/mono.git/info/refs >> >> >> The error message indicates that the SSL certificate from github has >> problems. Usually SSL problems can be traced to one of the following >> causes: >> * Stupid attacker >> * Broken proxy >> * local time skew >> * broken local installation >> * error at github >> >> I could access https://github.com just now and was presented a certificate >> from DigiCert with the SHA1 Fingerprint >> CE:67:99:25:2C:AC:78:12:7D:94:B5:62:2C:31:C5:16:A6:34:73:53, valid from >> 05/27/2011 thru 07/29/2013. >> > > > -- > View this message in context: > http://mono.1490590.n4.nabble.com/Git-error-14090086-when-pulling-Mono-source-tp3920419p3923467.html > Sent from the Mono - Dev mailing list archive at Nabble.com. ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list