-
Notifications
You must be signed in to change notification settings - Fork 176
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
Compile source code #1355
Comments
Thank you @73hulu for creating this issue. If this is in regards to a defect, product question or feature request: you should use our support portal at https://support.fossa.com to file a request, as you would receive more immediate support. |
Instructions for building can be found in our contributor documentation. Note that we include a few proprietary components which will not be available for third-parties to use while building, so some functions of the FOSSA CLI will be limited. Also note that we are limited in our ability to support users using unofficial builds. Please use official releases of the CLI for production work or evaluation purposes. |
Run the cabal build command in the root directory of the project. A dependency error message is displayed. Check that there is no spectrometer package in the official dependency package warehouse。 The error log is as follows: |
spectrometer is the internal name of the package we develop in this repository. It isn't distributed on hackage and we don't currently have any plans to distribute it there. With some more details I may be able to offer assistance:
To me, this message looks like you're trying to build a version of spectrometer which requires base 4.15 when cpio-conduit requires base 4.17, which is a conflict. I checked though, and both the version of cpio-conduit we reference in |
This comment was marked as abuse.
This comment was marked as abuse.
fossa-cli is only a client, there is no way to resolve the package dependencies in the project, but now the project is running on the Intranet environment, can not access the external network, can not access https://app.fossa.com, what should I do? |
You should use the contributing guide for that version, which was using ghc 9.0 and base 4.15. Regarding accessing https://app.fossa.com, that is something I think that the team managing the intranet/firewalls would be able to help with better than I can since that configuration is specific to your organization. |
How to compile and package source code locally offline
The text was updated successfully, but these errors were encountered: