hodgesse1 / rfortran

Automatically exported from code.google.com/p/rfortran
0 stars 0 forks source link

R does not install using R-2.12.0 #84

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
*** What steps will reproduce the problem?

1. Install RFortran
2.
3.

*** What is the expected output?

*** What do you see instead?

*** What version of RFortran are you using?

v2.1.2

*** On which Windows operating system?

Either

*** What Fortran compiler (name and version number) are you using?

*** What version of R are you using?

R 2.12.0

*** Please provide any additional information below.

R-2.12.0, now includes both 32-bit and 64 bit installs of R

These means two versions of Rgui.exe in different directories R_HOME\bin\i386 
and R_HOME\bin\x64.

The installer currently looks for Rgui.exe in R_HOME\bin\ directory, hence is 
needs to be updated to ask for which version is being used 32 bit or 64 bit and 
then fill in the appropriate suffix.

Original issue reported on code.google.com by mark.th...@gmail.com on 2 Dec 2010 at 10:11

GoogleCodeExporter commented 8 years ago
[deleted comment]
GoogleCodeExporter commented 8 years ago
A work-around until the installer gets fixed is to change the last line of the 
Rfortran.set file to 
"R_HOME\bin\i386" (32 bit)
"R_HOME\bin\x64" (64 bit)

where R_HOME is the install directory for R. 

Original comment by mark.th...@gmail.com on 8 Feb 2011 at 1:02

GoogleCodeExporter commented 8 years ago
Mark, thank you for your rapid response.

I've made the modification you suggested to the last line of the Rfortran.set 
file and tried again. After making that change (from Issue 84) I'm still 
getting errors when I try to build Ex1_AustraliaRainfall_SimpleGraph. Below 
you'll see the errors produced in Visual Studio and the build log (which is 
also attached).

I greatly appreciate your help. I will admit that I'm fairly new to Visual 
Studio, totally new to the Intel compiler (I purchased it so that I could work 
with RFortran), and am in the process of learning both R and Fortran. 
Ambitious, I know. Your directions thus far have been within my abilities to 
execute, but I wanted you to be aware of my relative newbie-ness. Cheers, Abe 

p.s. let me know if there's a better format for reporting 
errors/messages/warnings which you'd prefer and I'll do that in the future.

In Visual Studio 2010 I get a whole slew of messages (1), warnings (433), and 
errors (2).

The message: 
Message 10   remark #7712: This variable has not been used.   
[FILEOPEN]  C:\RFortran\mutilslib-read-only\src\MUtilsLib_unitTestPlatform.F90  29
2   

The errors: 
Message 10   remark #7712: This variable has not been used.   
[FILEOPEN]  C:\RFortran\mutilslib-read-only\src\MUtilsLib_unitTestPlatform.F90  29
2   
Error   435  error #10014: problem during multi-file optimization compilation 
(code 4)    Link    
Error   436  error #10014: problem during multi-file optimization compilation 
(code 4)    Link

The warnings: 
Warning 1    warning #8208: If type specification is omitted, each ac-value 
expression  in the array constructor of type CHARACTER must have the same 
length type parameters.   ['RFortran Library v2.1.2 - 21 June 2010    
]   C:\RFortran\src\core\RFortran_globalvars.F90    54  
Warning 2    warning #6182: Fortran 2003 does not allow this edit descriptor.   
[I] C:\RFortran\mutilslib-read-only\src\MUtilsLib_StringFuncs.f90   140 
Warning 3    warning #6182: Fortran 2003 does not allow this edit descriptor.   
[F] C:\RFortran\mutilslib-read-only\src\MUtilsLib_StringFuncs.f90   149 
Warning 4    warning #6923: Fortran 2003 does not allow an expression to be used 
as part of the format list.   
[TEST_LEN]  C:\RFortran\mutilslib-read-only\src\MUtilsLib_MessageLog.f90    407 
Warning 5    warning #6923: Fortran 2003 does not allow an expression to be used 
as part of the format list.   
[TEST_LEN]  C:\RFortran\mutilslib-read-only\src\MUtilsLib_MessageLog.f90    393 
Warning 6    warning #6923: Fortran 2003 does not allow an expression to be used 
as part of the format list.   
[TEST_LEN]  C:\RFortran\mutilslib-read-only\src\MUtilsLib_MessageLog.f90    391 
Warning 7    warning #6188: Fortran 2003 requires a LOGICAL data type in this 
context.   
[SIZE]  C:\RFortran\mutilslib-read-only\src\MUtilsLib_unitTestPlatform.F90  136 
Warning 8    warning #6188: Fortran 2003 requires a LOGICAL data type in this 
context.   
[SIZE]  C:\RFortran\mutilslib-read-only\src\MUtilsLib_unitTestPlatform.F90  145 
Warning 9    warning #6188: Fortran 2003 requires a LOGICAL data type in this 
context.   
[SIZE]  C:\RFortran\mutilslib-read-only\src\MUtilsLib_unitTestPlatform.F90  155 
Message 10   remark #7712: This variable has not been used.   
[FILEOPEN]  C:\RFortran\mutilslib-read-only\src\MUtilsLib_unitTestPlatform.F90  29
2   
Warning 11   warning #6923: Fortran 2003 does not allow an expression to be used 
as part of the format list.   
[NCOL]  C:\RFortran\mutilslib-read-only\src\MUtilsLib_SettingsFiles.F90 455 
Warning 12   warning #6182: Fortran 2003 does not allow this edit descriptor.   
[G] C:\RFortran\mutilslib-read-only\src\MUtilsLib_SettingsFiles.F90 455 
Warning 13   warning #6923: Fortran 2003 does not allow an expression to be used 
as part of the format list.   
[NCOL]  C:\RFortran\mutilslib-read-only\src\MUtilsLib_SettingsFiles.F90 524 
Warning 14   warning #6182: Fortran 2003 does not allow this edit descriptor.   
[F] C:\RFortran\mutilslib-read-only\src\MUtilsLib_SettingsFiles.F90 524 
Warning 15   warning #6923: Fortran 2003 does not allow an expression to be used 
as part of the format list.   
[NCOL]  C:\RFortran\mutilslib-read-only\src\MUtilsLib_SettingsFiles.F90 590 
Warning 16   warning #7025: This directive is not standard 
F2003.  C:\RFortran\src\core\RFortran_Rput_Rget_Reval_Rcall.F90 349 
Warning 17   warning #7025: This directive is not standard 
F2003.  C:\RFortran\src\core\inc_1-3D_Rput.f90  47  
Warning 400  warning #5151: Continuation character illegal as first non_blank 
in statement    C:\RFortran\src\core\RFortran_Rput_Rget_Reval_Rcall.F90 1619    
Warning 401  warning #7416: Fortran 2003 does not allow this intrinsic 
procedure.   [LOC]  C:\RFortran\src\core\inc_1-3D_Rput.f90  50  
Warning 413  warning #6188: Fortran 2003 requires a LOGICAL data type in this 
context.    C:\RFortran\src\core\inc_0D_Rget.f90    46  
Warning 414  warning #6188: Fortran 2003 requires a LOGICAL data type in this 
context.    C:\RFortran\src\core\inc_0D_Rget.f90    46  
Warning 415  warning #6188: Fortran 2003 requires a LOGICAL data type in this 
context.    C:\RFortran\src\core\inc_0D_Rget.f90    46  
Warning 416  warning #6188: Fortran 2003 requires a LOGICAL data type in this 
context.    C:\RFortran\src\core\inc_0D_Rget.f90    46  
Warning 417  warning #7416: Fortran 2003 does not allow this intrinsic 
procedure.   [LOC]  C:\RFortran\src\core\inc_1-3D_Rget.f90  90  
Warning 418  warning #7416: Fortran 2003 does not allow this intrinsic 
procedure.   [LOC]  C:\RFortran\src\core\inc_1-3D_Rget.f90  90  
Warning 419  warning #7416: Fortran 2003 does not allow this intrinsic 
procedure.   [LOC]  C:\RFortran\src\core\inc_1-3D_Rget.f90  90  
Warning 420  warning #7416: Fortran 2003 does not allow this intrinsic 
procedure.   [LOC]  C:\RFortran\src\core\inc_1-3D_Rget.f90  90  
Warning 421  warning #7416: Fortran 2003 does not allow this intrinsic 
procedure.   [LOC]  C:\RFortran\src\core\inc_1-3D_Rget.f90  90  
Error   435  error #10014: problem during multi-file optimization compilation 
(code 4)    Link    
Error   436  error #10014: problem during multi-file optimization compilation 
(code 4)    Link    

The Build Log (also attached)
     Build started: Project: Ex4_AustraliaRainfall_ScriptedGraph, Configuration: Debug|Win32 

Output  
    Deleting intermediate files and output files for project 'Ex4_AustraliaRainfall_ScriptedGraph', configuration 'Debug|Win32'.
Compiling with Intel(R) Visual Fortran Compiler XE 12.0.0.104 [IA-32]...
ifort /nologo /debug:full /Od 
/I"C:\RFortran\RFortran_IVF\RFortran_IVF_LIB\Debug" 
/I"C:\RFortran\RFortran_IVF\RFortran_IVF_LIB\Debug/" /Qsave /module:"Debug/" 
/object:"Debug/" /Fd"Debug\vc100.pdb" /traceback /check:bounds /libs:static 
/threads /dbglibs /c /Qvc10 /Qlocation,link,"C:\Program Files (x86)\Microsoft 
Visual Studio 10.0\VC\\bin" 
"C:\RFortran\src\tutorial_examples\TutEx_AustraliaRainfall_ScriptedGraph.f90"
Linking...
Link /OUT:"Debug\Ex4_AustraliaRainfall_ScriptedGraph.exe /INCREMENTAL:NO 
/NOLOGO /MANIFEST 
/MANIFESTFILE:"C:\RFortran\tutorial_examples\IVF_Beginner\Ex4_AustraliaRainfall_
ScriptedGraph\Debug\Ex4_AustraliaRainfall_ScriptedGraph.exe.intermediate.manifes
t" /MANIFESTUAC:"level='asInvoker' uiAccess='false'" /DEBUG 
/PDB:"C:\RFortran\tutorial_examples\IVF_Beginner\Ex4_AustraliaRainfall_ScriptedG
raph\Debug\Ex4_AustraliaRainfall_ScriptedGraph.pdb" /SUBSYSTEM:CONSOLE 
/IMPLIB:"C:\RFortran\tutorial_examples\IVF_Beginner\Ex4_AustraliaRainfall_Script
edGraph\Debug\Ex4_AustraliaRainfall_ScriptedGraph.lib 
"C:\RFortran\RFortran_IVF\RFortran_IVF_LIB\Debug\RFORTRAN_IVF_LIB.lib" 
"Debug/TutEx_AustraliaRainfall_ScriptedGraph.obj" 
"C:\RFortran\RFortran_IVF\RFortran_IVF_LIB\Debug\RFortran_IVF_LIB.lib"
(0): internal error: backend signals

Link: error #10014: problem during multi-file optimization compilation (code 4)
Link: error #10014: problem during multi-file optimization compilation (code 4)

Ex4_AustraliaRainfall_ScriptedGraph - 2 error(s), 0 warning(s)

Original comment by Abe.Burn...@gmail.com on 8 Feb 2011 at 4:16

Attachments:

GoogleCodeExporter commented 8 years ago
Your problems maybe because in RFortran v2.1.2 the project RFORTRAN_IVF_LIB was 
missing a file. See issue 79.

This will be fixed in v3.0.0 - due to been released v. soon! 

Original comment by mark.th...@gmail.com on 14 Feb 2011 at 10:49

GoogleCodeExporter commented 8 years ago
Abe,

RFortran Installer for v2.1.2 is incompatible with R v12.2.0. 

I suggest you wait for the installer for v3.0.0 which will be compatible with R 
>v12.2.0.

Mark

Original comment by mark.th...@gmail.com on 14 Feb 2011 at 10:53