Re: minimize VMS footprint

From: Ken Fairfield (my.full.name_at_intel.com)
Date: 06/11/05

  • Next message: John Santos: "Re: why are alias names a bad idea?" 
    Date: Fri, 10 Jun 2005 15:37:54 -0700

    Eberhard Heuser-Hofmann wrote:
    > In article <bi1ja15teaem8olbfdq1nris7vucq4hquo@4ax.com>, BC Berry
    > <nobody@spamcop.net> writes:
    [...]
    >>My plan - get rid of the development stuff, sample files, etc. What
    >>I'm trying to determine is what's development and what's not. E.g. Are
    >>any *.*LB or *.h or *.c or etc. files in SYS$LIBRARY required for
    >>anything other than compiling and linking? I was hoping there was a
    >>list somewhere indicating which files/libraries are used at boot/run
    >>time as opposed to compile/link time.
    >>
    >>I like the $35 idea. However, with 300+ stations plus spares. My
    >>pockets aren't that deep.
    >
    >
    > You must not forget that *.c can be a part of vmsinstalable images...

    Eberhard, what are you talking about here??? While VMS certainly
    allows one to rename MY_GREAT_PROGRAM.EXE to DONT_LOOK_IN_THERE.C,
    I've never heard of doing an INSTALL of a C-language source file...

    The OP wants to remove "developer" files, etc., that are needed in
    a turn-key sort of setup. That inplies to me no need for compilers,
    and therefore, no need for source files.

         -Ken 

    -- 
I don't speak for Intel, Intel doesn't speak for me...
Ken Fairfield
D1C Automation VMS System Support
who:   kenneth dot h dot fairfield
where: intel dot com
  • Next message: John Santos: "Re: why are alias names a bad idea?"

    Relevant Pages

    • Re: Fortran module checking
      ... Is it as simple as (mind you I'm using xlf90) ... Compiling a source file that USEs a module requires the ... Ken dot And dot Ann ...
      (comp.lang.fortran)
    • Re: ANNOUNCE: Tile widget set, release 0.7.8
      ... The "lipo" command line utility can be used to add, list or extract files embedded into this universal container. ... directly compiling universal object files from compiler doesn't produce better code than compiling separately then merge with lipo. ... Also, compiling on an Intel machine for deployment on 10.2/10.3 systems requires to build the PPC version using 10.3.9 SDK, with specific CFLAGS, and the Intel version with 10.4 SDK with other flags. ... Hence, building PPC and Intel versions separately, and merging them with lipo, was not "the very least" option but actually best option, if not the only functional solution to produce universal binary supporting deployment on all Mac platforms. ...
      (comp.lang.tcl)
    • Re: SBCL fatal error: fake_foreign_call fell through
      ... So far I've only managed to install sbcl 0.9.17 and ... the latter has a heap limit. ... edition for Intel Mac yet. ... One should never underestimate compiling things himself, ...
      (comp.lang.lisp)
    • Re: gfortran problem
      ... While the code is compiling very well in intel compiler, ... Developer Products Division ... User communities for Intel Software Development Products ... Intel Fortran Support ...
      (comp.lang.fortran)
    • Re: Database for DOS C program
      ... program and it runs in a DOS like environment. ... I'm compiling it in ... wolfgang (dot) mahringer sbg at ...
      (comp.lang.c)