search

steelewool / iraf-v216

IRAF v2.16 / PCIX release
Other
0 stars 0 forks source link

Branch track/olebole/merge-all #34

Open RobSteele49 opened 7 years ago

RobSteele49 commented 7 years ago

Getting the following warning and error when building. The steps I used ./install make linux64 make sysgen

' Updated 26 files in libpkg.a xc -c -w -/g -/m64 -p vo -p noao x_votools.x x_votools.x: sys_runtask: x_votools.f: sysruk: xc -Nz -/g -/m64 -p vo -p noao x_votools.o libpkg.a -lasttools -lxtools -lstg -lds -ltbtables -lslalib -o xx_votools.e /usr/bin/ld: cannot find -lasttools collect2: error: ld returned 1 exit status Warning, mkpkg line 7: module relink' not found or returned error movexx_votools.e' to vobin$x_votools.e' $move: filexx_votools.e' not found Warning, mkpkg line 20: error moving file xx_votools.e Warning, mkpkg line 8: module install' not found or returned error Warning, mkpkg line 10: moduleupdate@votools' not found or returned error Warning, mkpkg line 3: module `update' not found or returned error

Start: Tue May 23 11:00:15 PDT 2017 End: Tue May 23 11:16:43 PDT 2017

Tue May 23 11:16:43 PDT 2017'

RobSteele49 commented 7 years ago

I was able to get the two libraries libsmw.a and libasttools.a to build by created the directories:

./noao/astutil/noaolib ./noao/onedspec/noaolib

RobSteele49 commented 7 years ago

Question for Zach: How do you think I should do this, should the ./install script be creating these files or should the makefile create the two directories if they don't exist?

This did not fix things because files that depend on libsmw.a cannot find that object.

zcsteele commented 7 years ago

In this particular case, I think it makes more sense to modify the Makefiles specific to those two libraries to ensure that the directories are present. If those libraries are building through scripts, we can change the scripts to check-and-copy instead of blindly copying.

Also, I did a build on my local system last night from olebole/merge-all (with my environment fully reset) and the build seems to be fine from there. I also started the process of merging that branch into track/olebole/merge-all - there were merge conflicts so the activity isn't yet complete. I suspect this issue will simply go away once that activity is finished.

RobSteele49 commented 7 years ago

I grabbed a copy of Ole's repository and did a checkout on his merge-all branch. I compiled it, with warnings, but the build seems to work just fine. The additions I had added to his branch in our local area are no longer necessary.