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

Phasar conflicts with the pre-installed nlohmann-json during the run-time #715

Open
4 of 9 tasks
yurivict opened this issue Apr 14, 2024 · 3 comments
Open
4 of 9 tasks

Comments

@yurivict
Copy link

  • I have searched open and closed issues for duplicates
  • I made sure that I am not using an old project version (DO: pull PhASAR, update git submodules, rebuild the project and check if the bug is still there)

Bug description

Describe here the issue that you are experiencing.

Steps to reproduce

Install the built package.

Actual result:

$ sudo pkg add -A /usr/local/poudriere/data/packages/14amd64-local-workstation/.real_1713110260/All/phasar-2403.pkg
Installing phasar-2403...
pkg: phasar-2403 conflicts with nlohmann-json-3.11.3 (installs files into the same place).  Problematic file: /usr/local/share/cmake/nlohmann_json/nlohmann_jsonConfig.cmake

Failed to install the following 1 package(s): /usr/local/poudriere/data/packages/14amd64-local-workstation/.real_1713110260/All/phasar-2403.pkg

Expected result: Describe here what should happen after you run the steps above (i.e. what would be the correct behavior)

Context (Environment)

  • phasar: v2403
  • googletest: e2239ee
  • json: bc889af
  • json-schema-validator 491ac44

Operating System:

  • Linux
  • FreeBSD 14.0
  • Windows
  • macOS

Build Type:

  • cmake
  • bootstrap.sh
  • custom build

Possible solution

Use the pre-installed nlohmann-json.

@fabianbs96
Copy link
Member

Hi @yurivict,
we are aware that there are problems with installing dependencies, especially with nlohmann::json. We also have fixed some of these issues recently and merged the fixes into the development branch. Which prebuilt package are you using?

@yurivict
Copy link
Author

I am using the package built by the FreeBSD port devel/phasar, version 2403.

@fabianbs96
Copy link
Member

We created the fix after releasing v2403. Maybe the maintainers of devel/phasar can incorporate it as hotfix

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

No branches or pull requests

2 participants