I think I was caught in this exact situation after upgrading to Sequoia: tk was installed as dependency of some other port without the +x11 variant, and R build failed because of that. I’m quite sure I didn’t request a specific version of either R or tk. Then to build R I’m also quite sure I just made
sudo port install tk +x11 and after that sudo port install R and the build was successful. The current situation after that, shown by port installed, is R @4.4.2_0+aqua+builtin_lapack+cairo+gcc14+openmp+tcltk+x11 (active) tk @8.6.15_0+quartz tk @8.6.15_0+x11 (active) Ciao Franco > On 22 Dec 2024, at 21:13, Kenneth Wolcott <[email protected]> wrote: > > How to proceed? > > port installed | grep ' R ' > R @4.4.1_2+aqua+builtin_lapack+cairo+gcc14+openmp+tcltk+x11 > R @4.4.1_3+aqua+builtin_lapack+cairo+gcc14+openmp+tcltk+x11 > R @4.4.1_4+aqua+builtin_lapack+cairo+gcc14+openmp+tcltk+x11 > R @4.4.2_0+aqua+builtin_lapack+cairo+gcc14+openmp+tcltk+x11 (active) > > port installed | grep ' tk ' > tk @8.6.14_0+x11 > tk @8.6.15_0+quartz (active) > > Does this mean that I need to have a tk based on x11 to be active? > > sudo port deactivate tk > Note: It is not recommended to uninstall/deactivate a port that has > dependents as it breaks the dependents. > The following ports will break: > tkdiff @4.2_0 > tklib @0.7_0 > R @4.4.2_0 > py312-tkinter @3.12.8_0 > py313-tkinter @3.13.1_0 > maxima @5.47.0_9 > Continue? [y/N]: n > ---> Cleaning tk > > Thanks, > Ken Wolcott > <port_R_failed.log>
