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.

Sign up for GitHub

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

Jump to bottom

boost: auto-detect and disable ~/user-config.jam #888

Closed
eschnett opened this issue May 3, 2016 · 5 comments
Closed

boost: auto-detect and disable ~/user-config.jam #888

eschnett opened this issue May 3, 2016 · 5 comments
Labels
build-error good first issue help wanted up-for-grabs

Comments

@eschnett
Copy link
Contributor

eschnett commented May 3, 2016

I was trying to build Boost via Spack on a system where I previously had created a file ~/user-config.jam. This file overrides Spack's configuration options for Boost, leading to a build failure. (The build failure is somewhat hard to detect since it doesn't mention this file, the symptoms are just that the build options that Boost reports are slightly different than what they should be.)

Spack should detect the presence of that file, and should either abort with an error, or should temporarily disable it.
@tgamblin
Copy link
Member

tgamblin commented May 5, 2016

@scheibelp: FYI -- I think we've talked about this before right?

@scheibelp
Copy link
Member

I don't recall specifically talking about how to resolve this issue. Looking around briefly I don't see any way to disable the file other than moving it elsewhere, so I'd be in favor of aborting. This also seems boost specific so IMO it makes the most sense to add to boost's package.py.

@alalazo alalazo changed the title Auto-detect and disable ~/user-config.jam boost: auto-detect and disable ~/user-config.jam Nov 22, 2017
@adamjstewart
Copy link
Member

@hainest maybe you could take a look at this old boost issue?

@hainest
Copy link
Contributor

hainest commented Aug 14, 2020

@adamjstewart My bjam-foo isn't great, but I'll see if I can replicate this.

olupton pushed a commit to olupton/spack that referenced this issue Feb 7, 2022
@anilbey
updated BGLibPy to 4.3.12 (spack#888)
2a973fd 
BGLibPy Changelog:
 4.3.9:
 - Add support for a* targets in connection blocks

 4.3.8:
 - Vectorised usage of bluepy api for get_sonama_mecombo_emodels

 4.3.4:
 - Add node_properties_available to check if nodes.h5 can be used
 - Add get_sonata_mecombo_emodels to extract nodes.h5 properties
 - setup.py to use bluepy[sonata]>=0.14.12, needed for bluepysnap
 - Add bglibpy/tests/examples/sim_sonata_node/ test directory

 4.3:
 - Add ability to read inh/exc minis from sonata nodes file
 - Add use scaling based on hill coefficient / extracellular calcium concentration
 - Add ability to read conductance ratio from sonata nodes file
 - Rely on BluePy to read nrn.h5 version
 - Execute nosetests in parallel
 - Add OMP_NUM_THREADS=1 to test to avoid running out of resources
 - Stop testing for deprecation warning when using .syns
 - Use lru_cache to optimize bluepy query
 - Add CHANGELOG
@alalazo
Copy link
Member

alalazo commented May 13, 2022

Closing, since there has been no activity in a while. Feel free to reopen if you want to continue work on this.

@alalazo alalazo closed this as completed May 13, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
build-error good first issue help wanted up-for-grabs
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
6 participants
@eschnett @tgamblin @scheibelp @hainest @alalazo @adamjstewart