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
Running './configure' on external hard drive fails #16478
Comments
Does the path have spaces in it? |
Tried again without any spaces in the path and still the same error. |
The error is also including: I have tried running ./configure --without-gui however this brings back the same result. |
What does the |
And have you (re-) run |
I have re-run that I can't find any config.log or debug.log anywhere in the directory? |
Hmm, maybe the |
(ex)Fat is a very minimal file system, it likely misses some metadata, such as file permissions (especially +x) necessary to do the build. |
Running
No errors occur, however when I then run
I have tried re-formatting the drive to FAT32 but still get the same issue. I will try on a different Mac tonight and try to replicate the issue. |
FAT32 has the same problem, it's an older revision of FAT. You need a 'real' file system. FAT is only good for storing photo's and media, basically, it's not useful for development work. |
I formatted using Mac OS Extended, and this works flawlessly now. Thanks for your help. Is this something that should be looked into or is it beyond control? |
@dannmat This is likely something out of our control. Thanks for following up. |
When cloning Bitcoin Core and trying to configure/build, I get the error:
./configure: line 1: syntax error near unexpected token ('
Building from the boot disk works as expected, but if I replicate these steps exactly on my external hard drive, I get the above error
I expected the configure file to generate a makefile
Try building with MacOS 10.15 beta (build 19A512f) on an external 1TB hard drive.
Running the latest clone from GitHub (latest commit 94df084)
2015 MacBook Pro 15"
The text was updated successfully, but these errors were encountered: