#214 fortran will not make a .mod file

[dan hayes]

get the output:

||Warning: Nonexistent include directory "-c"|
||Warning: Nonexistent include directory "C:\codeblocks-13.12-nosetup\module.os_output_dir"|
C:\codeblocks-13.12-nosetup\module.f90|12|C:\codeblocks-13.12-nosetup\module.f90 12 .18:|
||Fatal Error: Can't open module file 'C:\codeblocks-13.12-nosetup\module.os_output_dir/inc.mod0' for writing at (1): No such file or directory|
||=== Build failed: 1 error(s), 2 warning(s) (0 minute(s), 0 second(s)) ===|

[ollydbg]

Do you need a Fortran compiler?
What is the steps to reproduce this bug?
Thanks.

[dan hayes]

it is already using a fortran compiler gnu fortran compiler and i type into code::blocks as follows

module inc
integer*1 i,is ,j,j1,j2,m1,m2,np,npmx,nps
contains;subroutine sub1(ilisin,ils)
!integer*1,allocatable,dimension(:),intent(out)::ilisin(:),ils(:)
integer*1,allocatable::ilisin(:),ils(:)
npmx=2;nps=3;
allocate(ilisin(nps),ils(2*nps-min(3,nps)))
do i=1,nps;ilisin=i;enddo;do i=1,2*nps-min(3,nps);ils=1;enddo;end
subroutine wigd(ii,ilisin,imn,ils);integer*1 i,ii,imn,np,nps !,allocatable
integer*1,dimension(:),intent(in)::ilisin(:),ils(:)
!print*,"nps",nps;
end;end module inccall sub1(ilisin,ils)
use inc;end

then press f9 or else compile it first, either way it is same error and same if the last two statementscall sub1(ilisin,ils)
use inc;end

are left out. either with or without them

  From: ollydbg <ollydbg@users.sf.net>

To: [codeblocks:tickets] 214@tickets.codeblocks.p.re.sf.net
Sent: Wednesday, September 9, 2015 9:24 AM
Subject: [codeblocks:tickets] #214 fortran will not make a .mod file

Do you need a Fortran compiler?
What is the steps to reproduce this bug?
Thanks. [tickets:#214] fortran will not make a .mod fileStatus: open
Milestone: Undefined
Created: Wed Sep 09, 2015 09:27 AM UTC by dan hayes
Last Updated: Wed Sep 09, 2015 02:23 PM UTC
Owner: nobodyget the output:||Warning: Nonexistent include directory "-c"|
||Warning: Nonexistent include directory "C:\codeblocks-13.12-nosetup\module.os_output_dir"|
C:\codeblocks-13.12-nosetup\module.f90|12|C:\codeblocks-13.12-nosetup\module.f90 12 .18:|
||Fatal Error: Can't open module file 'C:\codeblocks-13.12-nosetup\module.os_output_dir/inc.mod0' for writing at (1): No such file or directory|
||=== Build failed: 1 error(s), 2 warning(s) (0 minute(s), 0 second(s)) ===|

Sent from sourceforge.net because you indicated interest in https://sourceforge.net/p/codeblocks/tickets/214/To unsubscribe from further messages, please visit https://sourceforge.net/auth/subscriptions/

[bluehazzard]

First: Your posts are nearly impossible to read. Please use some formating, and code hilightening (click on the ? in the editor). Or use at least some newlines to differ between text and code.

Second: I think your problem has nothing to do with c::b. For sure it is no bug.

Fatal Error: Can't open module file 'C:\codeblocks-13.12-nosetup\module.os_output_dir/inc.mod0' for writing at (1)

this looks as your compiler has no right to access this file. Have you disabled your Anti Virus?
Are you using windows > Vista? Then you should do anything directly in your c drive. Use your documents Folder for example

[darmar]

The current C::B v20.03 can definitely handle such simple test cases.
I would suggest to close this ticket.