Opened 2 years ago

Last modified 2 years ago

#65044 assigned defect

R @4.1.3 fails to configure on 10.4.11: Failed to configure R: Invalid value for configure.compiler

Reported by: barracuda156 Owned by: kjellpk (Kjell Konis)
Priority: Normal Milestone:
Component: ports Version: 2.7.2
Keywords: powerpc, tiger Cc: i0ntempest, cooljeanius (Eric Gallager)
Port: R

Description

--->  R-4.1.3_0+builtin_lapack+cairo+gcc7+openmp+recommended+x11.darwin_8.ppc.tbz2 doesn't seem to exist in /opt/local/var/macports/incoming/verified
--->  Attempting to fetch R-4.1.3_0+builtin_lapack+cairo+gcc7+openmp+recommended+x11.darwin_8.ppc.tbz2 from http://packages.macports.org/R
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0   126    0     0    0     0      0      0 --:--:--  0:00:01 --:--:--     0
--->  Attempting to fetch R-4.1.3_0+builtin_lapack+cairo+gcc7+openmp+recommended+x11.darwin_8.ppc.tbz2 from http://nue.de.packages.macports.org/R
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0   278    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
--->  Attempting to fetch R-4.1.3_0+builtin_lapack+cairo+gcc7+openmp+recommended+x11.darwin_8.ppc.tbz2 from http://atl.us.packages.macports.org/R
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0   387    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
--->  Fetching distfiles for R
--->  R-4.1.3.tar.gz does not exist in /opt/local/var/macports/distfiles/R
--->  Attempting to fetch R-4.1.3.tar.gz from https://cran.rstudio.com/src/base/R-4/
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 33.4M  100 33.4M    0     0   844k      0  0:00:40  0:00:40 --:--:--  847k
--->  Verifying checksums for R
--->  Checksumming R-4.1.3.tar.gz
--->  Extracting R
--->  Extracting R-4.1.3.tar.gz
Executing:  cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_math_R/R/work" && /usr/bin/gzip -dc '/opt/local/var/macports/distfiles/R/R-4.1.3.tar.gz' | /usr/bin/gnutar --no-same-owner -xf - 
/usr/bin/gnutar: Read 7168 bytes from -
--->  Patching Rscript.c: s|R_HOME|"/opt/local/Library/Frameworks/R.framework/Versions/4.1/Resources"|
--->  Patching Defn.h: s|<libintl.h>|"libintl.h"|
--->  Configuring R
Error: Failed to configure R: Invalid value for configure.compiler: 
Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_math_R/R/main.log for details.

Change History (4)

comment:1 Changed 2 years ago by barracuda156

That is, gcc-4.x have to be blacklisted, apparently. When invoked with sudo port -v upgrade R configure.compiler=macports-gcc-7, compiler value error does not occur.

comment:2 Changed 2 years ago by ryandesign (Ryan Carsten Schmidt)

Cc: i0ntempest added
Owner: set to kjellpk
Port: R added; r removed
Status: newassigned

I don't think MacPorts chose gcc-4.2 as the compiler, and therefore I'm not convinced that blacklisting it would fix anything; it looks like MacPorts chose the empty string as the compiler, which shouldn't happen. One cause of that was fixed in MacPorts 2.7.2 in #63281 but if you're seeing this with MacPorts 2.7.2 then maybe there is a second cause that we haven't found yet. Could you attach the main.log? Maybe it would help us understand what went wrong.

comment:3 in reply to:  2 Changed 2 years ago by barracuda156

Replying to ryandesign:

I don't think MacPorts chose gcc-4.2 as the compiler, and therefore I'm not convinced that blacklisting it would fix anything; it looks like MacPorts chose the empty string as the compiler, which shouldn't happen. One cause of that was fixed in MacPorts 2.7.2 in #63281 but if you're seeing this with MacPorts 2.7.2 then maybe there is a second cause that we haven't found yet. Could you attach the main.log? Maybe it would help us understand what went wrong.

Yes, this is in Macports 2.7.2. I will attach logs once back to PPC machine.

comment:4 Changed 2 years ago by cooljeanius (Eric Gallager)

Cc: cooljeanius added
Note: See TracTickets for help on using tickets.