User forums > Using Code::Blocks

CB suddenly will not compile any f90 module

(1/2) > >>

franko:
First, I have read the 'read this first', Mr. Mcfly. thank you for the information.

However, what I have is not a coding error, as NONE of my  (correctly compiled for years, not changed) modules will compile; they did until this week. BUT there has always, always been a warning message, whether compiling or linking, about 'cannot open file (or folder) for output...' usually something like, '..[progname].os_output_dir..' on the end. I have never consciously specified anything of the sort. I think there is something about CB settings that I do not understand here.

I have a CB v 13.12 with gfortran installation from a well-known vendor, been using it for about a month. The warnings were there from a pristine installation.
Until this week (4/1) it was a warning only. Now, it has become a full 'fatal error', and the (very simple) source code does not compile.
These modules compile (and link, and work in executables) when I use them with gfortran in Linux; they also do the same in my Windows 7 64 bit command line. But not in CB IDE, when I select 'compile current file' (ONLY file in the IDE).

To answer some obvious questions: 1) I run these as an administrator, there should be no 'permissions' errors; 2) I have tried it again while disabling antivirus (Kaspersky) completely, rebooting, checking to ensure K is disabled: same error. 3) the 'build logs' always contain, as a first step, " -J(and the strange output path/file I have not consciously requested)". I believe this is a build target of some kind. 4) There are no projects running. 5) I have removed the CB/gfortran installation and rebooted, checked for its absence on the path, etc, and reinstalled: compiling again fails with same error. 6) I have searched the CB 'settings' without any luck looking for anything relevant to 'build target (while compiling)'. 7) All the 'build target' options in the IDE are greyed-out since I am not working with a project. Finally, I have no other compilers on my system, other than python and pythonxy. Surely that is not a problem?

Here is an abbreviated first few lines from a 'build log':

"gfortran.exe -JD:\Work\F90\mods\source\jrtypes.os_output_dir   -IC:\FortranTools\lib -c D:\Work\F90\mods\source\jrtypes.f90 -o D:\Work\F90\mods\source\jrtypes.o
gfortran.exe  -o D:\Work\F90\mods\source\jrtypes.exe D:\Work\F90\mods\source\jrtypes.o   C:\FortranTools\lib\libfortrantools.a ..."...followed by other info, finally ending in a red 'error' and 'build failed.'

You can see the " -J(path is D drive to a working directory, but with a filename I do not recognize)"

I hope someone can suggest something, I am not getting any where with this problem.

Many thanks in advance,

franko

franko:
Wow. I am here about 5 minutes later to admit I forgot about 'another' compiler I have - Atmel C.

BUT this EXACT problem is happening on my laptop with an EXACT same installation, same win7 64, with NO Atmel, NO python, etc.
SAME errors, same messages.

I don't think these are the problem since they are not present on the other machine which throws the exact same error.

franko

franko:
Just for info, I have removed all of those other possible 'compilers:' - the Atmel (Norwegian makers of small 8-bit processors), and all python.
I have removed CB fortran and everything I can find about it on my machine; rebooted, reinstalled CB/gfortran, problem remains unchanged.

I notice quite a few other instances of this problem online with CB : appearance of an unknown target, "...os_output_dir", but no solutions.
Perhaps it is time to register a valid bug.

franko

stahta01:
http://wiki.codeblocks.org/index.php?title=FAQ-Compiling_%28general%29#Q:_How_do_I_report_a_compilation_problem_on_the_forums.3F

franko:
@stahta01
I think my first post contains everything in the 'template' you linked to,
except the build log which I will post.
As far as the steps to analyze the problem, I've pretty much done all that
a non-expert could do.
franko

Navigation

[0] Message Index

[#] Next page

Go to full version