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
Troubleshooting Compilation of libhdf5.a
#52
Comments
hdf5.a
libhdf5.a
This will depend on your source Dockerfile; could you link that directly? Likely you will need to |
@nick123pig thanks here's my Dockerfile: I did install
|
What's the processor arch of the machine you're running docker on? The install script is making hard binding to x86_64. For instance on my m1 macbook docker, the lib is installed at If you're good on that, could you try without that |
I'm on an M1 Macbook but this dockerfile is compiled with
I've had the same outcome with or without the |
Where does the
The entire point the {Rhdf5lib} package is that you shouldn't need a HDF5 system library. The package provides the library, compiled with a (pretty much) fixed set of options and a known versions, which makes maintaining the {rhdf5} package a lot easier. One thing I note is that are a lot of double quotes in your build log output e.g.
On the Bioconductor build report that same line appears as below, which doesn't start with
Maybe that's a red-herring, but perhaps some paths are getting mangled somehow and this is a symptom. As a general statement, if you're using conda to install R, it's also much easier to install the package from bioconda as well. It's quite common for people to run into issues when trying to mix the two. |
I see I fixed the double quoting issue in 6bef8cf which is available in Bioc 3.17 but not 3.16, which you are using. |
I think this issue was because the package was not automatically identifying the version of I've now fixed it in the latest version of Rhdf5lib in both Bioconductor 3.17 and 3.18. Unfortunately I can't backport the change to 3.16, which is what is used by R-4.2 in your container. I think you'll either have to use a newer R, install Rhdf5lib from GitHub, or use the version distributed via bioconda. |
Thanks I’ll look into upgrading the environment. 👍🏼Sent from my iPhoneOn Sep 8, 2023, at 1:46 PM, Mike Smith ***@***.***> wrote:
I think this issue was because the package was not automatically identifying the version of ar provided by conda. This in turn was causing libtool to fail to generate the static libraries. Why it did this without any sort of error elludes me.
I've now fixed it in the latest version of Rhdf5lib in both Bioconductor 3.17 and 3.18. Unfortunately I can't backport the change to 3.16, which is what is used by R-4.2 in your container. I think you'll either have to use a newer R, install Rhdf5lib from GitHub, or use the version distributed via bioconda.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>
|
I'm attempting to install Rhdf5lib on a docker container based on the ubuntu:focal image. I am stuck on a compilation issue regarding the internal hdf5 library included in this package. For some reason the
hdf5/src/.libs/libhdf5.a
file is not getting generated in thesrc/.libs
directory. I can't find anything in the build.log that is clearly a red flag. Is there something obvious I might be overlooking?Complete details on the docker environment and specifics of the issue can be found on the repo we're working on:
levisimons/eDNAExplorer#9
But I'll repost a summary here:
The text was updated successfully, but these errors were encountered: