-
Notifications
You must be signed in to change notification settings - Fork 137
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
configuration fails #138
Comments
Please, download the file Now, if you really want to start from the git tree (say to modify the code of Jellyfish, rather than using the software), then you need the |
Thank you. I downloaded the package that you recommend and the installation worked.
…--
ETH Zurich, Dr. sc. ETH Samuel Fux
High Performance Computing, Scientific IT Services
WEC D 13, Weinbergstrasse 11, 8092 Zurich, Switzerland
Phone +41 44 632 57 63, http://www.id.ethz.ch/
samuel.fux@id.ethz.ch
________________________________
Von: gmarcais <notifications@github.com>
Gesendet: Mittwoch, 13. Februar 2019 17:40:55
An: gmarcais/Jellyfish
Cc: Fux Samuel (ID SIS); Author
Betreff: Re: [gmarcais/Jellyfish] configuration fails (#138)
Closed #138<#138>.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub<#138 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/ALZDq-ZCL1Nedcb-XZbhb6bPyqTnIpFiks5vNEAXgaJpZM4a4_kE>.
|
freebsd-git
pushed a commit
to freebsd/freebsd-ports
that referenced
this issue
Sep 17, 2021
The GitHub-generated tarballs require reautoconf and more dependencies including gettext, regardless whether the NLS knob is turned off. gmarcais/Jellyfish#138 (comment) This update also fixes a build issue when the NLS knob was turned off. http://pkg.ftfl.ca/data/13amd64-default/2021-09-16_13h45m55s/logs/errors/Jellyfish-2.3.0_1.log Differential Revision: https://reviews.freebsd.org/D31984 Co-authored-by: Jason W. Bacon <jwb@FreeBSD.org>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The text was updated successfully, but these errors were encountered: