-
Notifications
You must be signed in to change notification settings - Fork 156
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Tests failing (Ubuntu 20.04) #175
Comments
Ubuntu 20.04 in WSL2 on Windows, The
|
I don't do Windows, so I don't have an environment to test it in, but I know for sure that all the source files were checked in with Unix line endings. Is there a setting in WSL2's Git Bash (or whatever you used to download the sources) that quietly "corrects" line endings in text files to Windows standard? |
line 16 is the first empty line in the file, and the other line numbers correspond to empty lines as well. I tend to also think something has extracted those Crazy idea: |
Unfortunately, I suspect the entire file has CR/LF line endings; see the line 30 @isotopp, if you checked out the |
Hm, nothing weird shows:
|
Aaargh.
That's set so that the Linux- and Windows-Side of the machine can both git the files. If not set, bad things happen with everything else.
and
Ok, so something in that test script thingie is incredibly sensitive to line endings. |
Meh. No Jetbrains CLion for you, then. |
bash (being a Unix shell) is sensitive to line endings. I'm actually surprised Microsoft didn't patch bash to use Windows line-endings; perhaps they found that it would break too many other WSL utilties. |
I am running
autoreconf -i
,./configure
,make
, andmake check
.The final lines of the configure output are
The
make
succeeds.A
make check
then explodes.There is no \r in tap-driver.sh, and the line numbers emitted are not really helpful.
What's going on?
The text was updated successfully, but these errors were encountered: