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

fixed libxcb deps and added patch to remove pthread-stubs dep #1042

Closed
wants to merge 2 commits into from

Conversation

lee218llnl
Copy link
Contributor

These changes were needed to build on a TOSS3 (RHEL7) based system.

@nrichart
Copy link
Contributor

This should also help to build qt. I was working on something similar, will trying to install paraview

@davydden
Copy link
Member

something similar is done in #820, but that PR is inactive for about a month.

@luigi-calori
Copy link
Contributor

I had similar problem. I tried to use #820 and found some problems.
I have some patches but not know how to contribute to an open PR, especially now that seems that PR are accumulating and no merge happen.
Would it make sense to have a branch dedicated to ParaView / Qt that we keep in sync with develop and integrate #820 and move on?

I would like to use spack for building different flawors of ParaView: does it make sense to try to contribute here or is better to just use my private copy of packages?

Thanks

@davydden
Copy link
Member

@luigi-calori you can't contribute to an open PR unless github user grants you write access to his fork. I think it is always better to fix things upstream in Spack. My guess is that this PR will be merged faster than #820 so perhaps one could wait a bit (with a hope that PRs start merging again soon 😄) and then open a follow up PR with the changes you have.

@luigi-calori
Copy link
Contributor

Thanks. I' ll try to work on other stuff... Nevertheless, I' m quite worried about the lack of merging:
I currently already need some PR that I keep integrating locally: #984 #797 #579 #946
They can currently be merged without conflicts now and I can safely use them even if not merged. Unfortunately #820 would be useful but is not ready to be used as is and I need to patch it,

If the rate between PR submission / PR merging keeps increasing, contributing would be harder and more effort should be dedicated to merging.
would make sense to set up an intermediate merging layer?
Could we set up some thematic integration PR where specific feature are addressed and the mantainer of the PR keeps the PR in sync with develop while accepting PR-PR from contribution?
I' m a git newbie so maybe this is just nonsense...

@tgamblin
Copy link
Member

@lee218llnl @luigi-calori can you see if the current develop branch works for you? I actually ended up doing this myself, though I added pthread-stubs as a package, which is slightly different. If it does, this PR may not be needed. Sorry I didn't track this closely enough

@lee218llnl
Copy link
Contributor Author

@tgamblin The latest develop branch worked for me. I am OK with deleting/closing this PR, but we may want to wait for confirmation from @luigi-calori

@tgamblin
Copy link
Member

tgamblin commented Jun 18, 2016

@luigi-calori: I'll close this if the latest develop branch works for you.

@tgamblin tgamblin closed this Jun 20, 2016
@tgamblin
Copy link
Member

@luigi-calori: please reopen if this issue regresses.

@tgamblin tgamblin deleted the bugfix/libxcb-deps branch October 11, 2016 20:03
olupton pushed a commit to olupton/spack that referenced this pull request Feb 7, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants