libzmq: add variants "docs", "libbsd"#28503
Conversation
|
Hi @iarspider! I noticed that the following package(s) don't yet have maintainers:
Are you interested in adopting any of these package(s)? If so, simply add the following to the package class: maintainers = ['iarspider']If not, could you contact the developers of this package and see if they are interested? You can quickly see who has worked on a package with $ spack blame libzmqThank you for your help! Please don't add maintainers without their consent. You don't have to be a Spack expert or package developer in order to be a "maintainer," it just gives us a list of users willing to review PRs or debug issues relating to this package. A package can have multiple maintainers; just add a list of GitHub handles of anyone who wants to volunteer. |
iarspider
changed the title
Head branch was pushed to by a user without write access
Head branch was pushed to by a user without write access
|
@spackbot re-run pipeline |
|
I've started that pipeline for you! |
|
Not sure why it fails to build czmq - build fine locally |
|
Random glitch probably. |
|
@alalazo could you please merge this? Thanks! |
|
@iarspider I see that the |
|
I see the platform variation was from #20893 , not here... so I think the error is combination of that change and this one. |
libbsd is *always* required when +libbsd (introduced in spack#28503) . spack#20893 had previously removed the macos dependency because libbsd wasn't always enabled. Libbsd support is only available after 4.3.2 so change it to a conflict rather than bumping the dependency.
libbsd is *always* required when +libbsd (introduced in spack#28503) . spack#20893 had previously removed the macos dependency because libbsd wasn't always enabled. Libbsd support is only available after 4.3.2 so change it to a conflict rather than bumping the dependency.
libbsd is *always* required when +libbsd (introduced in spack#28503) . spack#20893 had previously removed the macos dependency because libbsd wasn't always enabled. Libbsd support is only available after 4.3.2 so change it to a conflict rather than bumping the dependency.
libbsd is *always* required when +libbsd (introduced in spack#28503) . spack#20893 had previously removed the macos dependency because libbsd wasn't always enabled. Libbsd support is only available after 4.3.2 so change it to a conflict rather than bumping the dependency.
libbsd is *always* required when +libbsd (introduced in spack#28503) . spack#20893 had previously removed the macos dependency because libbsd wasn't always enabled. Libbsd support is only available after 4.3.2 so change it to a conflict rather than bumping the dependency.
libbsd is *always* required when +libbsd (introduced in spack#28503) . spack#20893 had previously removed the macos dependency because libbsd wasn't always enabled. Libbsd support is only available after 4.3.2 so change it to a conflict rather than bumping the dependency.
* trilinos: disable dl on macOS * py-sphinx-argparse: add explicit poetry dependency * libzmq: fix libbsd dependency libbsd is *always* required when +libbsd (introduced in #28503) . #20893 had previously removed the macos dependency because libbsd wasn't always enabled. Libbsd support is only available after 4.3.2 so change it to a conflict rather than bumping the dependency. * hdf5: work around GCC11.2 monterey fortran bug * go-bootstrap: mark conflict for monterey
* trilinos: disable dl on macOS * py-sphinx-argparse: add explicit poetry dependency * libzmq: fix libbsd dependency libbsd is *always* required when +libbsd (introduced in spack#28503) . spack#20893 had previously removed the macos dependency because libbsd wasn't always enabled. Libbsd support is only available after 4.3.2 so change it to a conflict rather than bumping the dependency. * hdf5: work around GCC11.2 monterey fortran bug * go-bootstrap: mark conflict for monterey
3 participants
docs: whether to build and install documentation.libbsd: whether to link with libbsd - libzmq will use own implementation ofstrlcpyif libbsd is not available.