-
Notifications
You must be signed in to change notification settings - Fork 119
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
insane ./configure in github circleci #1361
Comments
Using commit 08b21f8 I'm able to verify the problem is in |
Hmm. Today, the failing configure is getting used on the main repo. |
maybe it's better to migrate on CMake which supports Emscripten (and another OSes) far more better? I may try to help with it |
Hi Alex, If you create a CMake infrastructure, that wold be fine, and I'd merge the pull reqs. It's used in all the other parts of OpenCog, so that's a plus. As to Emscripten & JavaScript in general; there is no one out there that is using the javascript bindings. I think these mostly more-or-less work, and the issue is with github itself (I guess) Every now and then, Amir & I make a token effort to fix this up, but without some javascript user insisting on something, not much happens. |
Github seems to be using two different sets of autoconf macros in different instances. The one on this git repo is "sane" and seems to be the same as what I've got on my development machine. The one on
linas/link-grammar
seems to be insane. As a result, circleci fails on linas/link-grammar but works here.Working configure output:
Failing configure output:
First diff is at line 73: my configure has the message
"checking whether we are using the GNU C compiler"
at line 4193 of the configure script. It has"option to accept ISO C89"
at line 4308My configure script does not have the message
"checking whether the compiler supports GNU C"
anywhere. It also doesn't have"option to enable C11 features"
anywhere.That means ..
autogen.sh
is producing two different configures on these two instances. WTF.The text was updated successfully, but these errors were encountered: