Re: busting sp datatypes

"e p chandler" <epc8@xxxxxxxx> wrote in message
news:4df24e40-5602-4a99-8203-dc445b013a8d@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

If you are using the gfortran/gcc from equation.com, that's a
different story. It installs in \gfortran w/o requiring CPATH to be
set to compile C programs, etc. It also creates "stripped" .exe files
(w/o debug symbols) unless some key files are replaced.

I keep 4 different versions of gfortran around, one each from
http://www.equation.com and http://gcc.gnu.org/wiki/GFortran and two
from http://sourceforge.net/projects/mingw-w64/ . Each has its own
advantages and disadvantages. To keep build environments straight,
I emulate what ifort does for command-line environments: first I
create a separate directory for each compiler, like C:\gfortran,
C:\gcc_equation, C:\gcc_mingw64, and C:\gcc_mingw64a . The equation
version tries to take over your computer anyway, do I let it set up
the invironmental varaibles the way it wants to. For the others, I
drag and drop a cmd.exe from C:\WINDOWS\system32 to the root of the
compiler's directory tree and right-click the shortcut and change
some things. Let's see... for the gcc_mingw64 version, under the
General tab the title is set to "64-bit build environment for MinGW
64" and under the Shortcut tab the Comment field also bears that
title. The important thing is the Target field:

C:\WINDOWS\system32\cmd.exe /K ""C:\gcc_mingw64\Shortcut.bat""

Also under the options tab I check the QuickEdit mode and Insert
mode boxes. Having done this I also need C:\gcc_mingw64\Shortcut.bat
file:

@echo off
Title Build environment for MinGW 64 (64-bit host)
set path=C:\gcc_mingw64\bin;%path%

Now double-clicking on the new shortcut to cmd.exe starts up a
command prompt all set up for this particular version of gfortran.
Maybe I should also try experimenting with setting up CPATH and
others because some versions don't seem to be able to link correctly
at this point unless I explicitly name the libraries libkernel32.a
and libuser32.a, but all the compilers are at least rendered
serviceable by this approach.

--
write(*,*) transfer((/17.392111325966148d0,6.5794487871554595D-85, &
6.0134700243160014d-154/),(/'x'/)); end


.

Relevant Pages

  • RE: Compiler Switch for a Visual Studio 2005 Class Project
    ... Would you please tell me which documentation you mentioned here? ... There should be no "Compile" tab in a .NET class project properties pages. ... PLEASE NOTE the newsgroup SECURE CODE and PASSWORD will be updated at 9:00 ...
    (microsoft.public.vsnet.general)
  • Re: Access 2007 Object Model Issue.
    ... Try a decompile, followed by a compact. ... Still in the code window, choose Compile from the Debug menu. ... On the General tab, make sure Error Trapping is set to: ...
    (microsoft.public.access.formscoding)
  • Re: Recommendation for build environment(s)
    ... > I'd like to get a recommendations on build environments setups, ... You should search the Debian archives which contains 16,000+ packages. ... compile features of their code using some form of tags / switches. ... Make generators ...
    (Debian-User)
  • Re: First-class macros
    ... around and calling macroexpand at runtime is a conversion from s-expressions to s-expressions at runtime. ... The resulting s-expressions could, in principle, be executed, but the environments are not available anymore in which you would want to execute them. ... the code can be compiled but you still get some of the advantages of macros. ... Instead at compile time, the parameters to functions are preprocessed in a preparation phase at compile time so that such functions can assume that some of their arguments are not evaluated yet, but are passed as thunks / closures. ...
    (comp.lang.lisp)
  • Re: Problem when compiling
    ... On the Environment tab, under "When a Program ... To run the program in the IDE, always use "Start With Full Compile", ... In Options, on the General tab, uncheck both "Background ... Compile" and "Compile On Demand" (Compile on Demand is the important one to ...
    (microsoft.public.vb.general.discussion)