archive-edu.com » EDU » R » ROCKEFELLER.EDU

Total: 626

Choose link from "Titles, links and description words view":

Or switch to "Titles and links view".
  • fastlink readme: AIX
    minor changes to the Makefile are necessary for compilation Change 1 Use the xlc compiler instead of gcc Change the line CC gcc to CC xlc Change 2 Uncomment the line SYSDEP D POSIX SOURCE Change 3 When compiling the auxiliary program OFM you will need to provide an additional argument to make Instead of make ofm use make ofm EXTRAFLAGS D XOPEN SOURCE FASTLINK user Helge Sachau has contributed

    Original URL path: http://linkage.rockefeller.edu/soft/fastlink/fl_aix.html (2012-11-26)
    Open archived version from archive


  • fastlink readme: Alpha VMS
    Note that there may be problems in porting this utility to VMS on a VAX Here are the instructions I got via Kimmo The top level directory after you untar the FASTLINK package is called fastlink The main source code files can be found in the subdirectory 3 0P src In the subdirectory 3 0P alphavms you will find the following extra files checkpointdefs h intended to replace the checkpointdefs h that comes with FASTLINK maketool vms com command file to assist with Make maketool vms c little C program to assist with make Here are the instructions as I understand them Read comments in maketool vms com and maketool vms c Among other things these comments refer you to an ftp site from which you can retrieve a version of make for OpenVMS Install the make that you retrieve Make sure all the 3 files from the alphavms directory are in the same directory as the main FASTLINK source code files Note that you will overwrite checkpointdefs h with the new version Unlike in version 2 2 you may now use the regular Makefile provided with the FASTLINK distribution Find the section in the Makefile marked VMS Specific Follow the directions there to uncomment all of the lines below up to but not including the line that starts END VMS Now you can make any of the targets in Makefile as on UNIX Note that you should make the make tool target first since it is used to make all the FASTLINK targets Caution The file commondefs h includes certain h files which have definitions that come with any C compiler The way these files are included in commondefs h makes standard assumptions about the user s search path and where the files are found If you get compilation

    Original URL path: http://linkage.rockefeller.edu/soft/fastlink/fl_alphavms.html (2012-11-26)
    Open archived version from archive

  • fastlink readme: DOS
    how to get the executables are given below The source code for FASTLINK for DOS is the same as the non DOS source code However if you wish to get source code and compile it you should use the djgpp C compiler this is a port of the gcc compiler to DOS Instructions for retrieving and installing the compiler are in README djgpp djgpp is freely available over the Internet by ftp DOS FASTLINK does not support crash recovery We are distributing only the slow versions of FASTLINK for now These are still measurably faster than LINKAGE Cautions FASTLINK is derived from LINKAGE 5 1 for UNIX and not from LINKAGE for DOS We have tested FASTLINK on DOS but we have not investigated to what extent LINKAGE for UNIX and LINKAGE for DOS are incompatible If FASTLINK and LINKAGE give different answers you should not assume that FASTLINK is wrong LINKAGE may be wrong I have fixed 2 significant bugs in LINKAGE LODSCORE ILINK and 1 significant bug in LINKAGE LINKMAP MLINK These bug fixes are described in README updates There is also an inconsistency in scaling in LINKAGE LINKMAP which is fixed in FASTLINK LINKMAP see README scaling You must a have 386 or higher machine The code was tested on several different 486 machines I am fairly certain that it won t work on 286 and below machines You should have a Math co processor on the machine Most recent 486 machines will have this We strongly recommend trying the programs outside of Windows i e in vanilla DOS first They probably work from Windows too but it may be the case that the compiler makes some assumptions about how the video monitor environment is set up which are not consistent with the setup of your machine

    Original URL path: http://linkage.rockefeller.edu/soft/fastlink/fl_dos.html (2012-11-26)
    Open archived version from archive

  • fastlink readme: IRIX
    line in the Makefile that reads SYSDEP and changing it to SYSDEP cckr It may be the case that gcc works on IRIX too but David has not verified this The changes beyond version 2 1 should not create any new problems I am not aware of any available versions of the auxiliary programs for IRIX David reports that with the assistance of a system administrator at his site he

    Original URL path: http://linkage.rockefeller.edu/soft/fastlink/fl_irix.html (2012-11-26)
    Open archived version from archive

  • fastlink readme: Linux
    Shriram Krishnamurthy and Kurt Hornik the main programs in FASTLINK port fine to Linux No change in the Makefile is needed Porting the auxiliary programs is a problem Kurt Hornik has succeeded in getting most of them to work with some modifications to the source code Detailed instructions can be found in the file hornik txt in the subdirectory linux under fastlink Valerio Aimale has packaged up executables and made

    Original URL path: http://linkage.rockefeller.edu/soft/fastlink/fl_linux.html (2012-11-26)
    Open archived version from archive

  • fastlink readme: OSF
    to work I do not yet have a recommendation on which of these to use Unfortunately there are some problems with the implementation of floating point on the Alpha which may interact badly with any or all of the compilers and FASTLINK The bad behavior you get is a floating point exception and a core dump I recoded some lines in FASTLINK to work around one manifestation of the problem however Martin Farrall reports that he still has a problem using the cc compiler with O2 level of optimization interestingly both O1 and O3 seem to work If you hit a floating point exception please perform as many of the the following experiments as you can before reporting the problem to me You can recompile the program with the following compiler flags added Flag ieee compliant and without O Without O and ieee compliant With O1 and without ieee compliant With O2 and without ieee compliant With O3 and without ieee compliant and rerun in each case to see if a crash occurs These flags should be added by editing the line in the Makefile that reads SYSDEP For example to add the flag ieee compliant change it to SYSDEP

    Original URL path: http://linkage.rockefeller.edu/soft/fastlink/fl_osf.html (2012-11-26)
    Open archived version from archive

  • fastlink readme: VAX
    of commondefs h In particular the section VMS MAY NEED TO CHANGE possibly uncomment the following 2 lines include unixio include file include Shriram begin include include VMS MAY NEED TO CHANGE possibly remove sys from the next 3 lines include include include Shriram end if defined vms include endif include VMS MAY NEED TO CHANGE comment out the any of the next 3 lines for files your system can t find include include include includes 3 possible places you might need to edit marked VMS MAY NEED TO CHANGE If you have trouble compiling as is this is the first place to look You may consult with your system administrator for help on how to make this modification for your VMS machine COMPILING The VMS command file FASTLINK BUILD VMS will compile and link all the source code to produce the 10 executables The DEC C compiler is fussy and produces a small heap of warnings and informational messages As far as I can tell these are all perfectly ignorable It should be possible to use the distributed makefile with a few minor changes if you have a unix compatible make facility There are a number of make facilities on the net and the VMS POSIX interface also provides one I have not yet got this approach to work but if you have any of these facilities working then give it a go VMS POSIX has a feature that means you cannot give the object file produced by the C compiler a name different from the input source file so the supplied makefile will need some modification You will need to add references to VMS C and its object file in the appropriate places RUNNING The VMS command file FASTLINK START VMS will define symbols for all the executables The line defining the source code directory will need modifying for your local installation This file needs to be run before using the programs We define a global command FASTLINK fastlink dir FASTLINK START VMS in Sylogin com then our users just need to type the command FASTLINK to set up their environment to run the programs The programs are run by simply typing the program names The datafiles Datafile pedfile etc all require a DAT filetype datafile dat pedfile dat etc CHECKPOINTING With the changes outlined above the checkpointing code will run and not cause any problems However I am not sure yet that the checkpointing will allow you to recover from a crash under VMS I am still working on this OUTSTANDING ISSUES Checkpointing has not been tested see above The CKPT program will not work Instructions for VAX C AUTHOR Alejandro Schaffer with lots of help from Shriram Krishnamurthi PREREQUISITES Must have VAX C compiler and MMS compilation utility installed DISCLAIMER Testing has been somewhat limited and I know very little about VMS SETUP Before compiling you must run the commands DEFINE LNK LIBRARY SYS LIBRARY VAXCRTLG DEFINE LNK LIBRARY 1 SYS LIBRARY VAXCRTL It may be

    Original URL path: http://linkage.rockefeller.edu/soft/fastlink/fl_vax.html (2012-11-26)
    Open archived version from archive

  • fastlink readme: VMS
    largely due to the super effort of three adventuresome FASTLINK users Steve Roberts in the United Kingdom Kimmo Kallio in Finland and Anita Destefano in the U S and to Shriram Krishnamurthi a student at Rice Steve provided instructions for VAXen and Kimmo for Alphas All three users did extensive testing and troubleshooting Thanks to Steve Kimmo and Anita You can find the top level instructions for VAX VMS in

    Original URL path: http://linkage.rockefeller.edu/soft/fastlink/fl_vms.html (2012-11-26)
    Open archived version from archive