Skip to content
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

Parenthesis in PATH causes build of libgfortran to fail in WSL #33581

Closed
BioTurboNick opened this issue Oct 16, 2019 · 5 comments
Closed

Parenthesis in PATH causes build of libgfortran to fail in WSL #33581

BioTurboNick opened this issue Oct 16, 2019 · 5 comments

Comments

@BioTurboNick
Copy link
Contributor

I don't know how much this matters per se, but having a parenthesis in the PATH variable (as sometimes occurs on Windows) seems to cause building of libgfortran to fail with

/bin/sh: 1: Syntax error: "(" unexpected

Changing line 267 of Makefile to place PATH in quotation marks appears to resolve the issue:
Current: -$(CUSTOM_LD_LIBRARY_PATH) PATH=$(PATH):$(build_depsbindir) $(JULIAHOME)/contrib/fixup-libgfortran.sh --verbose $(build_libdir)
Works(?): -$(CUSTOM_LD_LIBRARY_PATH) PATH="$(PATH):$(build_depsbindir)" $(JULIAHOME)/contrib/fixup-libgfortran.sh --verbose $(build_libdir)

This is in Windows Subsystem for Linux (Ubuntu) on Windows 10 x64. I'm not cross-compiling because that gave me other issues and I wanted to keep things simple.

@StefanKarpinski
Copy link
Member

Is this a Julia issue? It doesn't seem to be.

@BioTurboNick
Copy link
Contributor Author

Is there another place to register problems with the Makefile?

@StefanKarpinski
Copy link
Member

I misunderstood, I thought it was just that /bin/sh on WSL didn't like some path names, in which case there would be little we could do about it. That line number has changed—I think it's now line 272—but it also looks like this is fixed on master:

julia/Makefile

Line 272 in 220681f

-$(CUSTOM_LD_LIBRARY_PATH) PATH="$(PATH):$(build_depsbindir)" $(JULIAHOME)/contrib/fixup-libgfortran.sh --verbose $(build_libdir)

Can you check if the latest release candidate has this problem?

@BioTurboNick
Copy link
Contributor Author

Apologies, it was apparently fixed 5 months ago. I'm building from v1.2. Thanks!

@StefanKarpinski
Copy link
Member

xref-ing issues: #32100

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants