Re: Testing a 4.2 build
- Posted by ghaberek (admin) 2 days ago
- 96 views
As far as I can tell, everything else built fine (certainly didn't with make -j 8, but I've learned that lesson now)
This is why I made build.mak. It's a wrapper around Makefile.gnu that corrects some of the weird circular dependencies, handles running configure for you, and allows for easier cross-compiling from Debian/Ubuntu.
You can use it like this: make -f build.mak -j$(nproc) PLATFORM=linux-x64
It doesn't make much difference as eui still works and runs, for example, queens.ex without issue.
I have not addressed unit tests at all and I assume they're all broken. I plan to address the tests and clean up the documentation after getting 4.2 beta published on GitHub.
One other odd thing is that eui takes a while to get going. Is that a side-effect of running in WSL?
No, it shouldn't be doing that. On my system a freshly built 4.2 completes in less than half a second:
~/build-linux-x64$ time ./eui hello.ex Hello real 0m0.354s user 0m0.004s sys 0m0.017s
I'm running Ubuntu 24.04 on WSL on Windows 11 Pro.
~/build-linux-x64$ head -n5 /etc/os-release PRETTY_NAME="Ubuntu 24.04.2 LTS" NAME="Ubuntu" VERSION_ID="24.04" VERSION="24.04.2 LTS (Noble Numbat)" VERSION_CODENAME=noble ~/build-linux-x64$ wslinfo --version 2.5.9.0
I think your problem is that WSL imports PATH from Windows by default, so that you can start programs directly from WSL (which is nice), and I suspect there are issues caused by conflicts in those PATHs (which is not). You probably have Euphoria installed on Windows, correct? So it's in your PATH on Windows and in Linux. The delay here may be the WSL kernel having to decide which executable to actually run when you call eui. Try running eui with its full path and see if it helps. You can disable this by setting appendWindowsPath=false under [interop] in /etc/wsl.conf. For the record, I do not have Euphoria install on Windows on this machine. I'm doing everything in WSL.
I also noticed is startup times for executables can be slow if I mount WSL as a network drive (net use W: \\wsl$\Ubuntu) to test cross-compiled apps directly in Windows, and there's a significant delay before the program starts. I don't think that's the case here but it's worth noting. Adding an exception for \\wsl$\Ubuntu in Windows Defender seems to help. It may also be the same problem with the WSL kernel that I described above.
-Greg
