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

Build process on Linux includes shared libraries not in library path. #424

Open
rbrittain opened this issue Nov 30, 2023 · 1 comment
Open
Labels
bug an unexpected problem or unintended behavior

Comments

@rbrittain
Copy link

rbrittain commented Nov 30, 2023

When building xml2 on Linux (tested with RHEL7 and R 4.1,4.2,4.3), the compile and link steps will include libraries associated with directories in $PATH, but which aren't in the library search path for anything else. For example, if conda is in use, we have /optnfs/common/miniconda3/bin in $PATH. Building xml2 finds and uses header files in /optnfs/common/miniconda3/include/ and library (.so) files in /optnfs/common/miniconda3/lib (explicitly passed to linker with -L option). The compile succeeds, but then the test load fails with a missing library. Disabling conda makes the build locate the library in one of the default places (/usr/lib64) and it works.

The first library affected in libicui18n.so, but there are many other duplicated libraries between the standard system location and private copies installed by applications.

@hadley hadley added the bug an unexpected problem or unintended behavior label Oct 21, 2024
@jeroen
Copy link
Member

jeroen commented Oct 21, 2024

If you are using conda you should install xml2 from conda as explained on: https://anaconda.org/conda-forge/r-xml2

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug an unexpected problem or unintended behavior
Projects
None yet
Development

No branches or pull requests

3 participants