Toby, I know this is not what you're asking for, but when I build R from source within a conda environment I make sure I use the conda compilers. I think what you might be doing is using system compilers with conda libraries that may have been built using a different compiler. Not saying this is related to your issue.
Best, Kasper On Mon, Apr 14, 2025 at 9:42 AM Ivan Krylov via R-devel < r-devel@r-project.org> wrote: > On Mon, 14 Apr 2025 14:10:56 +0200 > Toby Hocking <tdho...@gmail.com> wrote: > > > /usr/bin/ld : ../../lib/libR.so : référence indéfinie vers > > « u_getVersion_73 » > > Strange that it's complaining about symbols from libicu when the > problem is due to libcurl-related flags. What was the command line used > to link libR.so somewhere above in the log? I think it's not being > correctly linked with libicu, but since shared libraries are allowed to > have undefined imports in them, this is only found out later, when > linking the R.bin executable. > > > It seems that the libcurl package in conda provides the curl-config > > command line program, which R is using to get this flag: > > -I/home/local/USHERBROOKE/hoct2726/miniconda3/include > > With libcurl installed from conda, what do the following commands print? > > curl-config --built-shared > curl-config --static-libs > curl-config --libs > > > To fix the build, I did "conda remove libcurl" and then "make clean" > > and then "configure" and "make" worked. > > It should also be possible to override the path to curl-config using > the CURL_CONFIG environment variable. > > -- > Best regards, > Ivan > > ______________________________________________ > R-devel@r-project.org mailing list > https://stat.ethz.ch/mailman/listinfo/r-devel > -- Best, Kasper [[alternative HTML version deleted]] ______________________________________________ R-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-devel
