[AWS] No route to host Net.Connect failed because Net.Wait failed

[Joseph Montanez]

IPv6 is already set to false. So i just tried setting it to true and
clean / recompiling and it gives the same error. the weird part is I
compiled static version of it on that same server, put it on a debian
6 server and it runs just fine.

I don't think I use, its from a cygwin ssh terminal I run the
commands. I also use google dns, which I think still lacks ipv6.

On Thu, Apr 12, 2012 at 7:39 PM, Dmitriy Anisimkov <anisimkov at ada-ru.org> wrote:
> On 04/13/2012 07:15 AM, Joseph Montanez wrote:
>> Ok, got the newest aws and gnat 2011 install. However now I get:
>>
>> raised AWS.NET.SOCKET_ERROR : [113] No route to host Connect to
>> 127.0.0.1 127.0.0.1:39281
> Do you use IPv6 TCP/IP on your computer ?
> Do you have "IPv6 = true" in makefile.conf ?
>
> It was a some problems in AWS with IPv6 mode.
>
>
> _______________________________________________
> AWS mailing list
> AWS at lists.adacore.com
> /no-more-mailman.html



-- 
Joseph Montanez
Web Developer
Gorilla3D
Design, Develop, Deploy