This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [PATCH] fix #69251 - [6 Regression] ICE in unify_array_domain on a flexible array member
- From: Mike Stump <mikestump at comcast dot net>
- To: Martin Sebor <msebor at gmail dot com>
- Cc: Gcc Patch List <gcc-patches at gcc dot gnu dot org>
- Date: Thu, 4 Feb 2016 09:39:10 -0800
- Subject: Re: [PATCH] fix #69251 - [6 Regression] ICE in unify_array_domain on a flexible array member
- Authentication-results: sourceware.org; auth=none
- References: <569D9FAB dot 90705 at gmail dot com> <56A16774 dot 8040609 at redhat dot com> <56A16A86 dot 3030102 at gmail dot com> <56A6538C dot 9030602 at gmail dot com> <56B0A0E7 dot 9010606 at redhat dot com> <56B15600 dot 5070509 at gmail dot com> <20160204110515 dot GK3017 at tucnak dot redhat dot com> <56B36F26 dot 4080101 at gmail dot com>
On Feb 4, 2016, at 7:32 AM, Martin Sebor <msebor@gmail.com> wrote:
> FWIW, I keep having trouble with the repository.
> $ svn switch --relocate svn://gcc.gnu.org/svn/gcc svn+ssh://msebor@gcc.gnu.org/svn/gcc
> svn: E170013: Unable to connect to a repository at URL 'svn+ssh://msebor@gcc.gnu.org/svn/gcc/trunk'
> svn: E210002: To better debug SSH connection problems, remove the -q option from 'ssh' in the [tunnels] section of your Subversion configuration file.
> svn: E210002: Network connection closed unexpectedly
You forgot to do:
ssh -oPubkeyAcceptedKeyTypes=+ssh-dss YOUR_ID@gcc.gnu.org append-key <~/.ssh/id_rsa.pub
Isn’t that obvious? Be sure you have an id_rsa key first, of course. Once you do this, then, you can use svn as normal.
If you want to double check first before doing the above, you can add:
ssh = /usr/bin/ssh -oPubkeyAcceptedKeyTypes=+ssh-dss
right after:
[tunnels]
in ~/.subversion/config, and then do an svn up ChangeLog, and see if it works. If it does, then you will want to do the first command. Once you do the first, you will then want to comment out the line you just added to the ~/.subversion/config file, if you added it. If it does not work, you will want to use:
ssh = /usr/bin/ssh -v
and then have an expert read through the 50 lines of goop and figure it out for you. If you use some other ssh, and not the one in /usr/bin, you will want to update the full path to ssh above to use the one you actually use. For example, I happen to use:
ssh = /opt/local/bin/ssh
If you do email the ssh -v output, don’t send to the full list, you can send it to me privately, if you don’t know where to go from there.