Skip to content

Confusion of installing R package in conda/mamba/miniforge3 R env in WSL #10359

@Shijie-Jian

Description

@Shijie-Jian

System details:

Positron and OS details:

Positron Version: 2025.10.1 (system setup) build 4
Code - OSS Version: 1.103.0
Commit: b13dd1c
Date: 2025-10-14T22:13:39.363Z
Electron: 37.2.3
Chromium: 138.0.7204.100
Node.js: 22.17.0
V8: 13.8.500258-electron.0
OS: Windows_NT x64 10.0.19045

Session details:

R 4.4.3 with conda

Describe the issue:

I created a R virtual env by miniforge3 in WSL Ubuntu, and properly set "Positron > R: Custom Root Folders" with "~/miniforge3/envs" (miniforge3 envs directory), so I could select specific R interpreter session (R of conda).

However, I am not able to install R package from sources in CONSOLE, as it mentioned lack of "make" compilation tool (this tool actually existed in the R virtual env but not in base env created by miniforge3 by default, checked through "make --version" in these two envs).

Surprisedly, I could install the same R package from sources in TERMINAL in the activated R virtual env. After that the package could be "library or require" properly in TERMINAL.

I am not sure whether I missed some manual setting in Positron at this case.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions