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

Build system failure related to neurondemo. #2495

Open
1uc opened this issue Sep 12, 2023 · 0 comments
Open

Build system failure related to neurondemo. #2495

1uc opened this issue Sep 12, 2023 · 0 comments
Labels

Comments

@1uc
Copy link
Collaborator

1uc commented Sep 12, 2023

During a build we run "${PROJECT_BINARY_DIR}/bin/neurondemo". This script is generated via a configure command. The script contains an optimization to not run nrnivmodl if a certain file neuron exists:

if [ ! -f "${NRNDEMO}neuron" ] ; then
	(cd "${NRNDEMO}release" ; "${NRNBIN}nrnivmodl" ; cd .. ; rm -f neuron ; touch neuron)
fi

However, this has the following downside. If we configure and build in a directory build while NEURON is broken, it will generate a special that's broken. Which is expected. However, when we fix the error. We'll not recreate the special because the file "${NRNDEMO}neuron" still exists. Hence, we're left with a broken build, even if we've fixed the issue.

I only know the workaround to delete the entire build directory and start over with configuring.

The preferred solution would be to either not optimize running nrnivmodl and see if that works; or clear the file "${NRNDEMO}neuron" if anything relevant changed during compilation.

@1uc 1uc added the bug label Sep 12, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant