Fortran Compiler Bug? USE statement renaming

The Fortran compiler
f90: Sun Fortran 95 8.2 Patch 121020-05 2006/12/08
complain, incorrectly I believe, about a renaming in a USE statement. Here is the source code:
MODULE mod
INTEGER :: m
CONTAINS
SUBROUTINE sub_mod(m1,x)
INTEGER, INTENT(in) :: m1
REAL :: x(m)
x = 3.
END SUBROUTINE sub_mod
END MODULE mod
SUBROUTINE sub(m,isum)
USE mod, mod_m => m
INTEGER :: m, isum
isum = m + mod_m
RETURN
END
The compiler says:
f90 -c LStest16.f
USE mod, mod_m => m
^
"LStest16.f", Line = 12, Column = 11: ERROR: "M" is the name of a dummy argument to program unit "SUB", therefore it must not be use associated from module "MOD".
^
"LStest16.f", Line = 12, Column = 11: ERROR: "M" has been use associated from module "MOD" and at least one more module. It must not be referenced.
f90comp: 16 SOURCE LINES
f90comp: 2 ERRORS, 0 WARNINGS, 0 OTHER MESSAGES, 0 ANSI
Note that changing from
REAL :: x(m)
to
REAL :: x(m1)
in the sixth line makes the compiler happy.
Seems odd to me.

It looks like a bug. I'll have someone look into it.
Bob Corbett

Similar Messages

  • Bug report for SS10U1 fortran compiler

    I am getting an internal error when compiling a larger fortran source file:
    f90: Internal Error, code=fw-assert-einln-835, last src=mbd.f:14
    If I first split the file and then compile the separate routines, the compiler survives:
    fsplit mbd.f
    f95 -c addblk.f fperio.f getblk.f mbbwi.f mgmbwi.f puta2blk.f putblk.f
    I'll be happy to provide a tar-ball to a Sun engineer.
    f90 -V
    Intel(R) Fortran Compiler for 32-bit applications, Version 8.1 Build 20050309Z Package ID: l_fc_pc_8.1.025
    Copyright (C) 1985-2005 Intel Corporation. All rights reserved.
    FOR NON-COMMERCIAL USE ONLY
    GNU ld version 2.15.90.0.1.1 20040303 (SuSE Linux)
    Supported emulations:
    elf_i386
    i386linux
    elf_x86_64
    best regards
    Dieter

    uups.
    sorry for printing the intel compiler version I am running.
    I veryfied that the problem persists
    This is the release of the Sun compiler causing the problem:
    /opt/sun/sunstudio10u1/bin/f90 -V
    f90: Sun Fortran 95 8.3 __version_f9x_patch_linux Build2_0 2005/08/01

  • Local class and switch statement -- compiler bug?

    Does anybody know why the following does not compile with "LocalClass cannot be resolved to a type" error in the case 1: block
    public class ProblemClass {
         public void localClassProblem() {
                   class LocalClass {
                        void doNothing() {};          
                   int i = 0; 
                   switch (i) {                    
                        case 1: {
                             LocalClass instance1 = new LocalClass();  //ERROR: unresolved type
                                            break;
    }while the following does (I only added case 2: where LocalClass type is not referenced within an embedded block)
    public class ProblemClass {
         public void localClassProblem() {
                   class LocalClass {
                        void doNothing() {};          
                   int i = 0; 
                   switch (i) {                    
                        case 1: {
                             LocalClass instance1 = new LocalClass();
                                            break;
                        case 2:
                             LocalClass instance2 = new LocalClass();
    }Is it a compiler bug? Thanks for clarifying this.
    --Michal                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               

    I'm using 1.5.0-b64
    --Michal                                                                                                                                                                                                                                   

  • Another Compiler Bug (message: An internal build error has occurred... Unknown Flex Problem)

    I was fighting with this problem for a few days. Finally I've got it resolved. I want to describe it and fill in BUG in the bug report, but I am not sure about Adobe support options. So, I am putting bug report here.
    1. ASSUMPTION: All problems which compiler reports as unknown problem are the real compiler BUGs/Problems. Eventually MXML compiler/ActionScript compiler should be able to take C++ or FORTRAN code or an aribitrary text and nicely tell "Error: It is not ActionScript (Flex) code" or "the code is corrupted from Line so and so...". When compiler crashed, it is most probably due to one of the states not handled (or not handled correct). Keeping this in mind I assume, that my code has nothing to do with the compiler crash.
    2. PROBLEM Description.
         - I tried to port our internal project from Flex3.5/Flex Builder 3 to Flex4.1/Flash Builder 4.
         - After checking out and trying to build code I start getting weird problems like Error 1037: Packages cannot be nested.
         - After cleaning and compiling project by project, walking up dependency tree, I was able to get rid of this problem.
         - On last Project I've got another problem (An internal build error has occurred... Unknown Flex Problem). Which I stuck with for a while.
         - When I checked log file I found following messages:
    ============================================================
    !ENTRY com.adobe.flexbuilder.project 4 43 2010-12-21 15:45:24.353
    !MESSAGE Uncaught exception in compiler
    !STACK 0
    java.lang.ClassCastException: macromedia.asc.parser.InputBuffer cannot be cast to flex2.compiler.as3.CodeFragmentsInputBuffer
    at flex2.compiler.as3.AbstractSyntaxTreeUtil.lineNumberToPosition(AbstractSyntaxTreeUtil.jav a:1266)
    at flex2.compiler.mxml.ImplementationGenerator.generateBinding(ImplementationGenerator.java: 569)
    at flex2.compiler.mxml.ImplementationGenerator.generateBindingsSetupFunction(ImplementationG enerator.java:863)
    at flex2.compiler.mxml.ImplementationGenerator.generateBindingsSetup(ImplementationGenerator .java:812)
    at flex2.compiler.mxml.ImplementationGenerator.generateInitializerSupportDefs(Implementation Generator.java:1878)
    at flex2.compiler.mxml.ImplementationGenerator.generateClassDefinition(ImplementationGenerat or.java:1044)
    at flex2.compiler.mxml.ImplementationGenerator.<init>(ImplementationGenerator.java:206)
    at flex2.compiler.mxml.ImplementationCompiler.generateImplementationAST(ImplementationCompil er.java:499)
    at flex2.compiler.mxml.ImplementationCompiler.parse1(ImplementationCompiler.java:197)
    at flex2.compiler.mxml.MxmlCompiler.parse1(MxmlCompiler.java:168)
    at flex2.compiler.CompilerAPI.parse1(CompilerAPI.java:2871)
    at flex2.compiler.CompilerAPI.parse1(CompilerAPI.java:2824)
    at flex2.compiler.CompilerAPI.batch2(CompilerAPI.java:446)
    at flex2.compiler.CompilerAPI.batch(CompilerAPI.java:1274)
    at flex2.compiler.CompilerAPI.compile(CompilerAPI.java:1496)
    at flex2.tools.oem.Application.compile(Application.java:1188)
    at flex2.tools.oem.Application.recompile(Application.java:1133)
    at flex2.tools.oem.Application.compile(Application.java:819)
    at flex2.tools.flexbuilder.BuilderApplication.compile(BuilderApplication.java:344)
    at com.adobe.flexbuilder.multisdk.compiler.internal.ASApplicationBuilder$MyBuilder.mybuild(A SApplicationBuilder.java:276)
    at com.adobe.flexbuilder.multisdk.compiler.internal.ASApplicationBuilder.build(ASApplication Builder.java:127)
    at com.adobe.flexbuilder.multisdk.compiler.internal.ASBuilder.build(ASBuilder.java:190)
    at com.adobe.flexbuilder.multisdk.compiler.internal.ASItemBuilder.build(ASItemBuilder.java:7 4)
    at com.adobe.flexbuilder.project.compiler.internal.FlexProjectBuilder.buildItem(FlexProjectB uilder.java:480)
    at com.adobe.flexbuilder.project.compiler.internal.FlexProjectBuilder.build(FlexProjectBuild er.java:306)
    at com.adobe.flexbuilder.project.compiler.internal.FlexIncrementalBuilder.build(FlexIncremen talBuilder.java:157)
    at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:633)
    at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37)
    at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:170)
    at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:201)
    at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:253)
    at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37)
    at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:256)
    at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:218)
    at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:360)
    at org.eclipse.core.internal.resources.Project.internalBuild(Project.java:516)
    at org.eclipse.core.internal.resources.Project.build(Project.java:94)
    at org.eclipse.ui.actions.BuildAction.invokeOperation(BuildAction.java:221)
    at org.eclipse.ui.actions.WorkspaceAction.execute(WorkspaceAction.java:162)
    at org.eclipse.ui.actions.WorkspaceAction$2.runInWorkspace(WorkspaceAction.java:483)
    at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38 )
    at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
    !SESSION 2010-12-22 09:48:27.766 -----------------------------------------------
    eclipse.buildId=M20100909-0800
    java.version=1.6.0_16
    java.vendor=Sun Microsystems Inc.
    BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US
    Framework arguments:  -product org.eclipse.epp.package.jee.product
    Command-line arguments:  -data C:\Client_Flex4 -os win32 -ws win32 -arch x86 -product org.eclipse.epp.package.jee.product
    ================================================
    3. RESOLUTION/WORK AROUND
         - I was able to get this problem cleared by putting compiler option for Flex Application projects:  -keep-generated-actionscript
    4. SIDE NOTE
      I do not really see putting this compiler option as the solution and living with the mistery is making me fill a bit bad.

    Hi Faser,
    I just tried it on Vista with our latest FB Plugin build but
    I was unable to reproduce your issue with the following setup:
    - FB Plugin build installed by Administrator account user
    under her Documents folder
    - Administrator account user can launch, create Flex projects
    under her own workspace without any problems
    - Standard account user can launch the FB Plugin build (need
    Admin's password) and create Flex project (default location) under
    his own workspace
    If your setup is different, can you please log a bug at
    http://bugs.adobe.com/flex.
    Be sure to include what build you are using, whether it's
    reproducible, the detail of the setup, etc...
    thanks,
    Sharon

  • Unexpected Fortran compiler behavior on variable declarations.

    There are several problems concerning Sun Fortran compiler for Linux, concerning variable declarations:
    (1) A variable can be declared two or more times within the same
    program scope. Surprisingly, the compiler accepts this, without any error or
    warning message. This is clearly a bug.
    (2) There is no warning message if a variable is used but never set, even if the -w4 flag is used. This is a serious bug.
    (3) There is no warning message if a variable is declared but never
    used.
    To illustrate the bugs, compile the following simple program:
    module fooModule
    implicit none
    public :: add
    contains
    function add(x,y)
    real, intent(in) :: x,y
    real :: unused ! This variable is never used and never set; no warning message.
    real :: add
    add=x+y
    end function add
    end module fooModule
    program TryProg
    use fooModule
    implicit none
    real :: x
    integer :: i
    integer :: i ! Duplicated declaration. The compiler accepts this!
    i=3
    print*,i
    print*,add(x,2.0) ! Variable x is used but not set; no warning message.
    end program TryProg
    EXPECTED BEHAVIOR:
    (1) Something like "ERROR: Duplicate declaration of 'i'" or "ERROR:
    Symbol 'i' already has basic type of INTEGER."
    (2) WARNING: Variable 'x' is used but not set.
    (3) WARNING: Variable 'unused' is never used and never set.
    ACTUAL BEHAVIOR:
    No error or warning messages; expected one error and two warnings.
    The bugs appear in all Fortran compilers for Linux, including latest release, SSX2.

    There are several problems concerning Sun Fortran
    compiler for Linux, concerning variable
    declarations:
    (1) A variable can be declared two or more times
    within the same
    program scope. Surprisingly, the compiler accepts
    this, without any error or
    warning message. This is clearly a bug.
    The bugs appear in all Fortran compilers for Linux,
    including latest release, SSX2.You have cited a number of constraint violations. The
    Fortran standard states
    A processor conforms to this standard if
    (3) It contains the capability to detect and report the
    use within a sumitted program unit of an
    additional form or relationship that is not
    permitted by the numbered syntax rules or
    constraints, including the deleted features
    described in Annex B;
    In English, this statement means that a conforming
    implementation must be able to detect and report
    syntax errors and constraint violations. It does not
    mean that it must detect and report them by default.
    Sun f95, like most other Fortran compilers, does not
    give errors or warnings for the use of common
    extensions by default. The option -ansi enables
    the compilation mode that reports such uses.
    For example, when I compile the program
    PROGRAM MAIN
    REAL X
    REAL X
    END
    with the option -ansi, I get
    REAL X
    ^
    "t.f", Line = 2, Column = 1: ANSI: Use of the tab character is an extension of the Fortran standard.
    REAL X
    ^
    "t.f", Line = 3, Column = 7: ANSI: "X" has been given the REAL attribute more than once. This is nonstandard.
    f90comp: 4 SOURCE LINES
    f90comp: 0 ERRORS, 0 WARNINGS, 0 OTHER MESSAGES, 2 ANSI
    The caret lines up with the identifer X in the output. The column
    number is given as column 7, because the letter X is the seventh
    character in the line.

  • Can't Use Batch Rename "Rename In Same Folder" for some photos

    Have a strange problem: when using "Batch Rename…" under the "Tools" menu, "Rename In Same Folder" is unusable for some photos taken with some cameras, not for others. For one example, I shift-selected a range of photos taken at a recent vacation, some with my iPhone, some with my girlfriend's Canon PowerShot SD450. Bridge renamed the iPhone photos, but not Canon photos. For another example, if I select a single photo taken by her cell phone or Canon camera, "Rename In Same Folder" is grayed-out; if I select a single photo taken my by iPhone, not so. Does anyone understand this behavior, and is there a solution?

    Bridge Support Center in the help menu leads to a 404 error page.
    Sadly enough this is also on my system (Mac OSX 10.6.8) It should not be showing 404 but it is there...
    What Bridge help files and links, forums, communities, google searches do not do is tell you how to fix what happens with the problem
    In general restarting Bridge holding down option key (in your case alt key) to choose reset preferences solves most problems.
    Here is a page from Adobe Support about Troubleshooting (although this states you should combine option/alt with cmd/ctrl but that is not needed)
    http://kb2.adobe.com/cps/317/317912.html
    I want to use Bridge batch rename to change jpegs into Mac PC compatible jpegs.
    Although I have the option for compatibility with Unix and Windows checked in my customized presets I'm not really aware of the need for that. If you have a .JPG or .jpg extension as the extension a Mac reeds and opens the file without problems. I am aware that as a Mac user I had the need to take care of Windows files in the past. Before OSX a Mac did not need an extension to recognize and open a file. Since OSX is Unix based the need to use an extension is there and also you should only use one dot (.) in the filename and that is before the extension at the end of the filename. Using spaces, commas etc is possible but not prefered. In basic, keep it simple (and short) and the file will open on all systems without problems.
    When you select a preset, the rename and preview buttons grey out. So I start all over...clear cache, check file permissions, restart/shutdown, etc
    That should not happen, presets and batch rename should be always available, even if you have only one file selected. You should start with the refreshing of the preferences. Deleting caches and checking file permissions are not needed every time for clearing prefs (although it is wise to maintain your system on a regular basis, but that is good for the use of all apps).
    On a Mac the user defined Batch Rename settings are saved in the user library / application support / Adobe/ Bridge CS5 / Batch rename setting. (not a single clue how that translate to windows but I have no reason to believe that such a file should not be present on your system.)
    Enter the term "batch rename" in the windows Bridge forum search and I got....ZERO results.
    Well, again a disappointment, there will be many result available in both Windows and Mac forum but it sure is not easy to find them
    The forum search option is next to useless. I believe you should try to switch to the main forum page or something, I once had a result but after so many tries I forgot how I managed this (combined with getting angrier every try...)
    I could really use some help because there is no way I can convert the number of files I have to make them compatible in MACs
    As stated before, if the are .jpg they are already compatible
    it used to be in CS 3 and 4 but since I "upgraded" to Production Premium suite 5.5 none of the version work.
    If you keep having problems you might consider the clean tool option to clear PSCS 3 and 4. Check also this KB article:
    http://www.adobe.com/support/contact/cscleanertool.html
    It should be possible to use all CS versions on your system but you can have only one version of Bridge active at the time. Upgrading from a single CS to a Suite should also be possible without problems but sadly enough everything that should be possible without problems is often only happening in the ideal world...

  • Entity Framework in WPF Application - Using Statement or Implement IDisposable

    I have a WPF application that uses Entity Framework.
    I have implemented a Repository that implements IDisposable, that holds my EF context.  When the application starts up I new up a Repository, which news up an EF context, then when the application shuts down, I dispose of my Repository, which disposes
    the EF context as well.
    The end result is that my context remains open during the entire lifetime of the application.  
    I've been reading up on EF, and all the examples put the operations against the EF context in a using statement.  Is that the preferred approach?  What is the priority: to keep the context open briefly, or just to make sure you properly dispose
    of it when you're finished with it.
    Thanks.
    Aaron

    >
    https://msdn.microsoft.com/en-us/library/aa355056(v=vs.110).aspx
    That link is only for WCF and it's broken implementation of the Dispose pattern.
    >I have been burnt in doing it where the connection was not closed or disposed when it short-circuted out of the Using statement on exception
    If so, it was a bug.  You should expect that not to happen.
    'using' will close your connection, unless the connection was open before the DbContext and was passed in.  'using' is the safest way to ensure that the connections are closed in a timely manner.
    David
    David http://blogs.msdn.com/b/dbrowne/
    I absoultly do not agree with you. I have been burnt in using the Using statment. And it was along the lines that an excpetion was thrown within the Using statement and no closing of the connection or dispoiong of it ever occured, which is what the WCF example
    is showing on how a Using statement can be short-circuted and things can go wrong.
    I don't care if the Using statement issue is being shown on a WCF typed cleint. I do the same thing in using straight up ADO.NET or EF, becuase I have been burnt by the Using statement, and I dont use them to open,  close or dispose of a connection.

  • How do I link in a Fortran Compiler into MatrixX/Sy​stembuild ?

    We currently use MatrixX and have Visual C++ ver 5 installed. I would like to add a Fortran compiler to the system. How do I get MatrixX to point to the fortran compiler ? Are there environmental variables I need to set ?

    I believe that there are several things that you will need to do. I am checking on them since I did not find a lot explicit in the manual.
    First, Like the C++ compiler, I believe that you will need to set the environment variables for the Compiler path, lib and include. This will enable the compiler to be called from the command line as is the C++ Compiler. There are probably instructions with the compiler on how to do this operation.
    I believe that the compatible compiler is the Visiual FORTRAN from Microsoft. Version 6 maybe.
    Second, you may need to take a look at the makefile.mk and ensure that the appropriate changes are made.
    Finally, I think you need to call the fortran function from a C wrapper, appropriately
    configuring the User Code Block.
    Again, I hope that I hear some more definitive information back from whom I asked, once I do I'll let you know.
    There are some example files attached passed to me from a user "Chris" in Canada.
    Garrett Thurston
    [email protected]
    Phone: 781.993.5540
    Attachments:
    sa_user.c ‏3 KB
    SA_USRF.f ‏4 KB
    Makefile.mk ‏6 KB

  • Intel Fortran compiler - ifortbin: No such file or.. [solved]

    Dear all!
    I am running arch64 with updated packages (I updated this morning). I am trying to install the intel fortran compiler. I took the "ifort" PKGBUILD file from AUR and I edited it to use the "em64t" packages instead of the "i386" packages. The package building and the installation went fine, but when I launch ifort, I get the following error:
    /opt/intel/fc/9.1.036/bin/ifort: line 42: /opt/intel/fc/9.1.036/bin/ifortbin: No such file or directory
    /opt/intel/fc/9.1.036/bin/ifort: line 42: /opt/intel/fc/9.1.036/bin/ifortbin: Success
    Instead, I should get a message saying that I gave no input files (I had the compiler working on Suse, that's how I know).
    Does anyone know why this is happening?
    Thanks for your help
              Valerio
    Last edited by valmar (2007-04-03 16:41:08)

    Thank to all those who looked at the thread. It seems that even if you install a 64 bit version on a 64 bit machine, you still have to have the following packages installed:
    lib32-glibc lib32-gcc.
    Which means that the 64 bit compiler is actually designed to run in a mixed system, and not a pure 64 bit system... very bizarre
             Valerio

  • Foreach syntax + generics, Possible compiler bug?

    I'm encountering an odd problem trying to use generics and the foreach (colon) syntax. The code in question:
    for (Iterator<String> it = col.getParameterNames().iterator(); it.hasNext();) {}
    for (String paramName : col.getParameterNames()) {}col is an instance of an inner class of the class whose method this code snippet is from, getParameterNames has the signature:
    public Set<String> getParameterNames();
    The first line, using the Iterator<String> explicitly, compiles fine. The second line, when present, raises the compiler error:
    found : java.lang.Object
    required: java.lang.String
    for (String paramName : col.getParameterNames()) {
    I cannot seem to reliably reproduce this situation in other (simpler) classes I write, but this one in particular seems to trigger it. Is it possible this is a compiler bug, or might there be something I'm doing incorrectly that I'm missing? Are my expectations about how the second line should work incorrect? It seems to in other circumstances...
    javac is 1.6.0_01. Any ideas?

    Here is a quick update, I'm more inclined to think of this as bad behavior now.
    This code compiles:
    public class Test {
    Vector<InnerTest> inners = new Vector<InnerTest>();
        public class InnerTest {        
           public Set<String> someSet() { return (new HashMap<String,String>()).keySet(); }
        public Test() {
            for (InnerTest it : inners) {
                for (String s : it.someSet()) {        
    }however, the following does not:
    public class Test {
    Vector<InnerTest> inners = new Vector<InnerTest>();
        public class InnerTest<P> {        
           public Set<String> someSet() { return (new HashMap<String,String>()).keySet(); }
        public Test() {
            for (InnerTest it : inners) {
                for (String s : it.someSet()) {        
    }Again, the problem might be with my expectations (I haven't gone through the specifications yet with this in mind), but I can't fathom how or why the unused parameter would make a difference in that method's tpye matching.

  • [svn:fx-trunk] 5408: Fix for - Compiler error using Reparent in a Halo Navigator.

    Revision: 5408
    Author: [email protected]
    Date: 2009-03-18 20:57:19 -0700 (Wed, 18 Mar 2009)
    Log Message:
    Fix for - Compiler error using Reparent in a Halo Navigator.
    QE Notes: None.
    Doc Notes: None.
    Reviewer: Paul, please review.
    Bugs: SDK-20099
    tests: checkintests
    Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-20099
    Modified Paths:
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/mxml/builder/ComponentBuilder.jav a

  • SS9 CC5.6 compiler bug - algorithm count confused with struct member

    Found some code that fails to compile in CC 5.6
    CC: Sun C++ 5.6 2004/07/15
    #include <algorithm>
    using namespace std;
    struct A {
      int count;   
    struct B
      struct A *a;
    int main(int argc, char **argv)
      struct B *b = 0;
      // This line fails to build, any other operator is ok
      if ( b->a->count < 50 )
      return (1);
    }Fails with error :
    "c56_algorithm_bug.cpp", line 21: Error: Unexpected ")" -- Check for matching parenthesis.
    "c56_algorithm_bug.cpp", line 22: Error: "," expected instead of "{".
    "c56_algorithm_bug.cpp", line 22: Error: Illegal value for template parameter.
    "c56_algorithm_bug.cpp", line 22: Error: ")" expected instead of "{".
    4 Error(s) detected.The compiler is getting confused with the use of the count struct member vs the count algorithm. Changing the < to a > fixes the problem.
    Using CC5.3 works fine as well as all other compilers we use (gcc 3.4, mipspro 7.4, VC 7.1)
    Anyone seen this ?
    - mark

    This bug has been fixed in the C++ 5.6 compiler. I'm not sure if the fix is in the first patch which is about to be released. If not, the fix definitely will be in the next patch.
    The workaround is not to use
    using namespace std;That using-declaration is a pretty big hammer, and often results in conflicts with user code, compiler bugs aside.

  • Absoft fortran compiling and debugging

    Hello eveyone,
    I have recently purchased an iBook G4. My problem is that I do not know Unix or Darwin and I have witten a code using Fortran on Windows. Now that I am using a Macintosh I would like to debug and compile this code on my iBook. Can anybody advise me on how to do this and what Fortran compiler is the easiest to run on a Mac.
    Thanks for taking interest.

    I have recently purchased an iBook G4. My problem is
    that I do not know Unix or Darwin and I have witten a
    code using Fortran on Windows. Now that I am using a
    Macintosh I would like to debug and compile this code
    on my iBook. Can anybody advise me on how to do this
    and what Fortran compiler is the easiest to run on a
    Mac.
    This is a golden opportunity to learn some Unix. The Fink project
    http://fink.sourceforge.net/
    will permit you to quite painlessly install (in addition to what is already available when you install the developer tools that came with OS X) the excellent g77 (GNU Fortran 77) or g95 (GNU-related Fortran 95) compilers and crunch away.
    The learning curve for command line tools is not as steep as you might think!
    Depending on your needs, it could be as simple as
    g77 -o mybin mysource.f
    ./mybin < input.data
    Snoop around the Unix forum Apple discussion group for more info. Good luck!

  • G95 - Fortran Compiler (Based of g77)

    Hey everyone,
    I'm working on a Macbook Pro Retina of mid 2014 running OS X 10.10 Yosemite.
    Recently I tried installing the g95 fortran compiler, derived from the older g77.  I simply moved the binary file to the right folder and performed a make install. Command line instructions seemed to work fine, but when I tried to run my compiled code it gave me the following error:
    dyld: no valid entry point
    Trace/BPT trap: 5
    I figured I was missing certain gcc-libs, so I dug into my usr/local/lib folder and copied all the gcc-lib files I didn't already have (that came with the tarball for installing g95) there. However, it still doesn't work.
    When I use otool on my binary file I get this:
    g95:
      /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 125.0.1)
    I know there should be another path specified there, but I have no idea as to what I could do to solve my problem. (I'm new to unix systems and the file system is challenging to say the least ;-))
    PS: When I googled the error, it seemed to be a common problem with g77 that could only be solved by downgrading to an earlier version of OS X because of something named "Rosetta" that was no longer included. However, since g95 is "new" unlike g77, I think this rather an error caused by my inaptitude than an actual problem with my system.

    Eventually, we will, Xiangyun.
    It�s not simple to just switch it overnight. As a global enterprise, it�s a long and weary process in our shop to switch compilers, since we have to build, evaluate, compare outputs between old and new compilers, benchmark them, before we can put them into production, globally.
    Not to mention that I always have problems with code-related, system-libraries related, undefined symbols, linking errors, etc. and etc. when switching compilers.
    Therefore, if we can keep the reliable and proven compilers in the work, then we would keep it. So, if you could provide a patch to our current version; we�d keep it a year or so longer, then that would be a great great help, while we'll be working on pushing the new compilers out.
    Thanks,
    lhn

  • [svn] 3813: Update J2EE Webtier Compiler to use SWFObject2 based HTML templates.

    Revision: 3813
    Author: [email protected]
    Date: 2008-10-22 09:13:37 -0700 (Wed, 22 Oct 2008)
    Log Message:
    Update J2EE Webtier Compiler to use SWFObject2 based HTML templates. JSP tags still use the old AC_OETags.js templates since that would be a more complicated change and it is not worth the effort right now.
    QE: Yes
    Doc: Is there any?
    Checkintests: Pass
    Reviewer: Pete
    Bugs: SDK-17699
    Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-17699
    Modified Paths:
    flex/sdk/trunk/modules/webtier/servlet/build.xml
    flex/sdk/trunk/modules/webtier/servlet/src/java/flex/webtier/server/j2ee/html/MxmlRendere r.java
    flex/sdk/trunk/modules/webtier/servlet/src/java/flex/webtier/util/RendererUtil.java
    flex/sdk/trunk/webapps/webtier/WEB-INF/flex/flex-webtier-config.xml
    flex/sdk/trunk/webapps/webtier/build.xml
    Added Paths:
    flex/sdk/trunk/modules/webtier/servlet/src/java/flex/webtier/util/index.template.vm
    Property Changed:
    flex/sdk/trunk/modules/webtier/servlet/src/java/flex/webtier/util/

    Hi,
    Can you mention the eclipse version you are using? And the platform in which you are trying to build?
    I feel its always better to be platform specific when you go in for headless build. I can see that the configs value in your properties file is "configs=*,*,*". Try changing it to appropriate value and build your product. For example, I use "configs=win32, win32, x86" for building my product in 32-bit windows machine.

Maybe you are looking for