iraf.net

Hi Don,
I've been following your mail exchange with Jeannette about your
port attempt, I hope you'll find these comments useful.> Particular mention is made of testing MKPKG, but I am not sure of the best
> way to do this. Could you send me some suggestions?
I think the passage you refer to suggests that you test the bootstrap
utilities thoroughly (mkpkg, xc, generic, etc). Once the bootstrap prog-
rams are working you will have an easier time with the rest of the port,
although you may find that later on you'll need to make minor changes (e.g.
adding a new compiler flag). Test these as you would any other program,
there's nothing specific I could suggest as a test procedure> Also, could you clarify the entries in the file $iraf/unix/hlib/mkpkg.inc
> for XFLAGS, XVFLAGS, and LFLAGS?
The "XFLAGS" entries are those that get used for compiling ALL iraf
code. Specific packages may change these as needed, but a minimal value is
usually "-c" (i.e. produce an object file), other options may also need to
be set flags needed by your compiler. XVFLAGS is similar but only applies to
the code in sys$vops (i.e. if you have a vector processor that may require
special flags). Similarly, LFLAGS is used to set linker flags.> In the same mkpkg.inc file under LFLAGS the distribution copy has an entry
> of -/Bstatic. Can I delete that,
The "Bstatic" option is Sun specific and probably doesn't apply to
your machine. This is a Sun C compiler option that links programs statically.> Finally, within xc.c, can you advise as to correct use of flags in the
> arglist?
The flags used by XC are compiler dependent so I can't really give
you any advice. Usually these are set to define things like optimization
levels, turn on/off ANSI C, etc. I hope this helps.Regards,
Mike Fitzpatrick