REditorSupport / REditorSupport/vscode-R

LD_LIBRARY_PATH is not properly exported

Open
#1,515 6 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
TypeScript
Stars
1.2k
Forks
139
Avg merge
2h 46m
Merged PRs (30d)
5

Description

Describe the bug
Attaching R doesn't properly sets LD_LIBRARY_PATH (it leads to errors when loading libraries). When I lunch R from system (the same one which I specify in r.path and r.term) has additional libraries on path as compared to attached R. I tried to update the LD_LIBRARY_PATH in .vscode-server/extensions/reditorsupport.r-2.8.2/R/session/init.R. when I attach R afterwards Sys.getenv("LD_LIBRARY_PATH") give updated LD_LIBRARY_PATH, however it seems like the libraries are still not accessible and the same error persist:

unable to load shared object 'proj/renv/library/R-4.3/x86_64-pc-linux-gnu/igraph/libs/igraph.so':
  /lib64/libstdc++.so.6: version `GLIBCXX_3.4.29' not found (required by /proj/renv/library/R-4.3/x86_64-pc-linux-gnu/igraph/libs/igraph.so)

loading libraries in manualy launched R works with no errors.

To Reproduce

Can you fix this issue by yourself? (We appreciate the help)
No

Environment (please complete the following information):

  • OS: Linux
  • VSCode Version: 1.88.1
  • R Version: 4.3.3
  • vscode-R version: 2.8.2

Thank you and kind regards,
Amel

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Compare the environment of an attached R session with the manually launched R session, starting with Sys.getenv("LD_LIBRARY_PATH") and the shared-library loading error. Inspect .vscode-server/extensions/reditorsupport.r-2.8.2/R/session/init.R and the attach path; done means the attached R can load the same library successfully without the GLIBCXX error.

Written by the indexing model from the issue text.

Assessment

Tech stack
linux, r, vscode
Domain
devtools, operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.