May 01
On Friday, 30 April 2021 at 19:22:57 UTC, Andrei Alexandrescu wrote:
> I mentioned this in the past, apparently it hasn't been resolved.
>
> Tried to install a dev tree for dmd from complete scratch. So:
>
> $ curl https://raw.githubusercontent.com/dlang/tools/master/setup.sh
> >/tmp/setup.sh
> $ /tmp/setup.sh
>
> The script gets everything from github nice and fast but then fails to download http://downloads.dlang.org/releases/2.x/2.095.0/dmd.2.095.0.linux.tar.xz for some reason.
>
> Anyway, I then try to run:
>
> $ cd dmd
> $ make AUTO_BOOTSTRAP=1 -f posix.mak
>
> As mentioned in the title, the command fails and confusingly suggest using AUTO_BOOTSTRAP=1, which is already there.
>
> If the plan is to give up boostrapping, fine but let's eliminate the code. The way things are now we both pay for the technical debt and we don't profit from it.
>
> Of course it would be much better if bootstrapping actually worked.

Just tried in WSL2 like this at ~:

# First I just cleaned my home
sudo rm -rf *

# And made sure I had c++
apt install g++

# Then I just did this
wget https://raw.githubusercontent.com/dlang/tools/master/setup.sh && chmod +x setup.sh && ./setup.sh

Everything worked as expected
May 01

On Saturday, 1 May 2021 at 01:07:33 UTC, Andrei Alexandrescu wrote:

>

WSL2 running Ubuntu under Windows.

[..]

Something is definitely wrong with your computer. I installed a fresh instance of Ubuntu 20.04 on WSL2 and everything worked just fine. See for yourself:
https://asciinema.org/a/Poq5VWHHDO7005UjIeQulb3Ye

Here's information about my Windows installation:

> systeminfo

Host Name:                 DESKTOP-HPVQAA5
OS Name:                   Microsoft Windows 10 Pro
OS Version:                10.0.19042 N/A Build 19042
OS Manufacturer:           Microsoft Corporation
OS Configuration:          Standalone Workstation
OS Build Type:             Multiprocessor Free
> wsl --list -v
  NAME            STATE           VERSION
* Ubuntu-20.04    Running         2
  Ubuntu          Stopped         1

After installing the Ubuntu and before starting the asciinema to record the, I just had to install build-essential and python3-pip:

$ history
    1  sudo apt update && sudo apt install build-essential python3-pip
    2  sudo pip3 install asciinema
    3  asciinema rec
    4  history

I also tried on another clean Ubuntu and just installing build-essential (without python3-pip) works as well.

May 02
On 5/1/21 4:51 PM, Petar Kirov [ZombineDev] wrote:
> On Saturday, 1 May 2021 at 01:07:33 UTC, Andrei Alexandrescu wrote:
>>
>> WSL2 running Ubuntu under Windows.
>>
>> [..]
> 
> Something is definitely wrong with your computer.

Thanks to all who tested - the problem is indeed with WSL (or my installation thereof).

For some reason, network connectivity from within WSL (at least on my machine) becomes really bad after a while and I need to shutdown and restart WSL in order to restore speed. At one point I couldn't push to git anymore.

Because of that, the download performed by the installation script was not finished. When I tried to manually run make, the system was not provisioned properly.

There would be the argument that that code should belong in the makefile as opposed to the installation script (as it was before) but no matter.

Thanks!
May 02
On Sunday, 2 May 2021 at 11:49:06 UTC, Andrei Alexandrescu wrote:
> On 5/1/21 4:51 PM, Petar Kirov [ZombineDev] wrote:
>> [...]
>
> Thanks to all who tested - the problem is indeed with WSL (or my installation thereof).
>
> For some reason, network connectivity from within WSL (at least on my machine) becomes really bad after a while and I need to shutdown and restart WSL in order to restore speed. At one point I couldn't push to git anymore.
>
> Because of that, the download performed by the installation script was not finished. When I tried to manually run make, the system was not provisioned properly.
>
> There would be the argument that that code should belong in the makefile as opposed to the installation script (as it was before) but no matter.
>
> Thanks!

Are you running WSL1 or WSL2 btw?

https://docs.microsoft.com/en-us/windows/wsl/compare-versions
May 02

On Sunday, 2 May 2021 at 11:49:06 UTC, Andrei Alexandrescu wrote:

>

On 5/1/21 4:51 PM, Petar Kirov [ZombineDev] wrote:

>

On Saturday, 1 May 2021 at 01:07:33 UTC, Andrei Alexandrescu wrote:

>

WSL2 running Ubuntu under Windows.

[..]

Something is definitely wrong with your computer.

Thanks to all who tested - the problem is indeed with WSL (or my installation thereof).

Happy to help ;)

>

For some reason, network connectivity from within WSL (at least on my machine) becomes really bad after a while and I need to shutdown and restart WSL in order to restore speed. At one point I couldn't push to git anymore.

Because of that, the download performed by the installation script was not finished. When I tried to manually run make, the system was not provisioned properly.

I haven't experienced this myself (though I haven't used WSL regularly since about 1-2 years - I just rebooted to Windows to try out the setup.sh script), but looking for similar issues online it seems your computer is likely not an exception:

https://github.com/microsoft/WSL/issues/4901

From what I gather, it may have something to do with Large Send Offload, with some people reporting that disabling this feature fixed the problem for them (but it seems that you have to disable it after every reboot).

You can try if that works for you like this:

  1. Go to Control Panel -> Network and Internet -> Network Connections
  2. Right click vEthernet (WSL) -> Properties
  3. Click 'Configure'
  4. Click 'Advanced' tab
  5. Disable both 'Large Send Offload Version 2'

If that fixes the issue, but you want to automate it, this PowerShell cmdlet should do the trick: https://docs.microsoft.com/en-us/powershell/module/netadapter/disable-netadapterlso?view=windowsserver2019-ps

>

There would be the argument that that code should belong in the makefile as opposed to the installation script (as it was before) but no matter.

As far as I can see, the AUTO_BOOTSTRAP logic is still part of the dmd/src/posix.mak Makefile:
https://github.com/dlang/dmd/blob/b8ffb017c8c802827be98722b838cb120b9d918b/src/posix.mak#L46-L52

Sebastian did factor it out to a separate bootstrap.sh script, but other than that I think it should work the same as it did before.

May 02

On Sunday, 2 May 2021 at 18:22:47 UTC, Petar Kirov [ZombineDev] wrote:

> >

For some reason, network connectivity from within WSL (at least on my machine) becomes really bad after a while and I need to shutdown and restart WSL in order to restore speed. At one point I couldn't push to git anymore.

Because of that, the download performed by the installation script was not finished. When I tried to manually run make, the system was not provisioned properly.

I haven't experienced this myself (though I haven't used WSL regularly since about 1-2 years - I just rebooted to Windows to try out the setup.sh script), but looking for similar issues online it seems your computer is likely not an exception:

https://github.com/microsoft/WSL/issues/4901

From what I gather, it may have something to do with Large Send Offload, with some people reporting that disabling this feature fixed the problem for them (but it seems that you have to disable it after every reboot).

[..]

P.S. As @Imperatorn mentioned, you should check whether you're using WSL1 or 2. The difference is that WSL2 is a full Linux VM running under Hyper-V, whereas WSL1 is a Linux kernel syscall layer implemented on top of the Windows kernel.

I think LSO issue is only related to WSL2, as it has the separate Hyper-V network interface.

May 06
On 5/2/21 10:17 AM, Imperatorn wrote:
> On Sunday, 2 May 2021 at 11:49:06 UTC, Andrei Alexandrescu wrote:
>> On 5/1/21 4:51 PM, Petar Kirov [ZombineDev] wrote:
>>> [...]
>>
>> Thanks to all who tested - the problem is indeed with WSL (or my installation thereof).
>>
>> For some reason, network connectivity from within WSL (at least on my machine) becomes really bad after a while and I need to shutdown and restart WSL in order to restore speed. At one point I couldn't push to git anymore.
>>
>> Because of that, the download performed by the installation script was not finished. When I tried to manually run make, the system was not provisioned properly.
>>
>> There would be the argument that that code should belong in the makefile as opposed to the installation script (as it was before) but no matter.
>>
>> Thanks!
> 
> Are you running WSL1 or WSL2 btw?
> 
> https://docs.microsoft.com/en-us/windows/wsl/compare-versions

WSL2. I had no idea it has these odd behaviors. Thought what our unittests do is fairly common.
Next ›   Last »
1 2