|
Hi Don,
The libex.a file won't be built until you do a sysgen of the core
system. Remember that building iraf is essentially a three step process:
first do a NOVOS bootstrap, then a sysgen of the core system, and then do
a VOS bootstrap (one which uses the libraries compiled in the sysgen, libex.a
for example). The iraf$unix/reboot script can be used to do the bootstrap,
it will figure out whether to do a VOS/NOVOS bootstrap.
> Testing rmbin is presenting a problem, though. The command
> % rmbin -v sourcecode
> when executed from the parent directory of sourcecode ($iraf/local) gives the
> following message:
> % cannot change directory to `sourcecode/'. Silly question, but I presume the directory 'sourcecode' actually
exists? The error message is coming from rmbin itself, after the procedure
os$zfchdr.c fails (this is called from unix$boot/bootlib/oschdir.c). I don't
think this has anything to do with opendir() or os$zopdir.c, since those are
used for reading the contents of directory whereas this failure is in simply
changing directories. > Can you suggest the best place to look for the source of the problem? I am
> suspicious of differences in the opendir () system function, since I had to
> modify some of the includes for zopdir.c. Try verifying the pathname sent to ZFCHDR (os$zfchdr.c), it must be
called with the full pathname of the directory. I wouldn't worry too much
about zopdir.c unless you have some other reason to suspect it. It's also
possible that on your system library routines like opendir() and chdir()
might behave differently than under SunOS.> It appears to work correctly, until after the LIBDS update. After a message
> "check file `libds.a' into `lib$', some warnings appear since libds.a does
> not yet exist. and then it gives this:
> Fatal error, mkpkg line 31: cannot return from subdirectory
> It is not clear to me where this error is occuring. Could you give me a
> suggestion? The warning about libds.a is normal. The other error message may be
related to the above rmbin problem since zfchdr.c is once again used to
change directories.> Of these, I am not sure which I really need. Can I set USE_NSPP = no, as
> well as USE_IIS = no? It's unlikely you've got an IIS attached to your machine so it
probably safe to set USE_IIS=no. The USE_NSPP flag is only needed if you
need to build the graphics kernel for a device using the old NCAR plot package,
it's probably okay to turn this one off as well. I hope this helps. We can't really spend a lot of time helping with
port attempts (without the machine/manuals it's sometimes pure guesswork on
our end anyway), but we'll try to answer most of your questions as time
permits.Regards and good luck,
Mike Fitzpatrick
|