Cannot set up on Catalina #471
Comments
|
Interesting; I don't think we've seen this particular failure before. Let's see if we can sort this out. The error you're getting there would seem to suggest that clang cannot create those output files. After it fails there, does the directory One other long shot: this error is very similar to another issue we saw recently on Windows, where the user's Bitdefender antivirus software was blocking the creation of new executables. Any chance you have some antivirus program running that could be interfering with the build? - Andy |
|
Yes, that directory does get created, but is empty. And yes, my employer does require antivirus software. I think we’re using Falcon and Crowdstrike. I could compile on another machine and copy the executable over, right? Except that my other machine is on a Big Sur beta... |
|
Thanks for checking back in on this issue. The similarity to other antivirus interference we've seen is certainly suspicious. I'll try to make some time today or tomorrow to install that antivirus package on my Catalina machine as a test. If I can verify that that's the issue, perhaps we can find a way to work around the conflict. And yes, you could likely build the Moddable SDK tools on another machine and copy them over. But I suspect you'll just keep running into this problem as you try to build apps using those tools... |
|
So strange. I mean, antivirus applications are awful, for sure, but I've never had any trouble building anything else on this particular setup. I'm happy to do anything I can to test/confirm/debug/log, by the way. |
|
Hi @thomasqbrady: a quick update on this on my side. I was finally able to get a trial version of Crowdstrike Falcon up and running. But I have not been able to reproduce any build issues with the AV software monitoring. And it does not seem to be generating any warning or "detections" in its admin console. The antivirus idea may be a red herring. If you're willing to work with me on this a bit, let's run through some additional possibilities. Could you:
Perhaps there will be some other clue in the verbose output when that fails. If you could share the build output here (or email it to me if there's any sensitive info in that you want to avoid posting publicly; I'm andy@moddable.com), I'd love to take a look and see if I can sort it out. Cheers! |
|
No problem! I appreciate the help, and I'm glad to do what I can. Following the instructions above, I got:
|
|
Interesting... this is failing at a slightly different place than I had thought, based on your first message. This is the linker trying to assemble the xsc executable from the listed object files, presumably after having successfully built them. Okay, next things to check:
Thanks! We'll get to the bottom of this. |
|
|
Now that is weird. If that is the immediate output of running Two ideas:
Please try:
And then send me the output of that. (Sorry, you'll have to do some redacting on the paths I'm printing there.) I'm hoping that will give some insight into why those dependencies are not being built. |
|
|
Figured it out! I had my MODDABLE environment variable set to: Instead, setting it to: |
|
@thomasqbrady - Thanks for persevering. @andycarle - Is there a way we can detect this problem, to help out others who might do something similar? |
|
@thomasqbrady Aha! That's great that you sorted it out! I had an inkling that the issue was related to the ~ in your paths, so early in this process I tested As an aside: this probably means that you have a stray directory somewhere (probably in @phoddie Yes, I think I can sort something out to throw an error on this condition. (We can also clarify in the docs that a full absolute path should be used.) |
|
I've pushed a change to provide an earlier and clearer error message for this case and for similar errors with the Thank you again for sticking it out through this, @thomasqbrady! I'm going to go ahead and close this issue. |
…resolved path when building tools. Provides an earlier error on cases like issue #471.
On step five of the environment setup for Mac instructions, and I get:
xsc debug : cc xsc
clang: error: no such file or directory: '/Users/[username]/Development/moddable/build/tmp/mac/debug/xsc/xsBigInt.o'
clang: error: no such file or directory: '/Users/[username]/Development/moddable/build/tmp/mac/debug/xsc/xsCode.o'
clang: error: no such file or directory: '/Users/[username]/Development/moddable/build/tmp/mac/debug/xsc/xsCommon.o'
clang: error: no such file or directory: '/Users/[username]/Development/moddable/build/tmp/mac/debug/xsc/xsdtoa.o'
clang: error: no such file or directory: '/Users/[username]/Development/moddable/build/tmp/mac/debug/xsc/xsLexical.o'
clang: error: no such file or directory: '/Users/[username]/Development/moddable/build/tmp/mac/debug/xsc/xsre.o'
clang: error: no such file or directory: '/Users/[username]/Development/moddable/build/tmp/mac/debug/xsc/xsScope.o'
clang: error: no such file or directory: '/Users/[username]/Development/moddable/build/tmp/mac/debug/xsc/xsScript.o'
clang: error: no such file or directory: '/Users/[username]/Development/moddable/build/tmp/mac/debug/xsc/xsSourceMap.o'
clang: error: no such file or directory: '/Users/[username]/Development/moddable/build/tmp/mac/debug/xsc/xsSyntaxical.o'
clang: error: no such file or directory: '/Users/[username]/Development/moddable/build/tmp/mac/debug/xsc/xsTree.o'
clang: error: no such file or directory: '/Users/[username]/Development/moddable/build/tmp/mac/debug/xsc/xsc.o'
make[1]: *** [/Users/[username]/Development/moddable/build/bin/mac/debug/xsc] Error 1
make: *** [debug] Error 2
where [username] is actually my username. I have XCode and the developer tools installed.
The text was updated successfully, but these errors were encountered: