puglia@cunixc.cc.columbia.edu (Paul Puglia) (10/16/89)
I have run across a fustrating problem with mips ultrix 3.1 running
on a DECstation 3100 . I several groups of fortran object files that
I would like to place into seprate ar archives to be link together
at a later time. When I try to create an archive with the following
ar command: ar -q libeign.a *.o. I get the following error messages:
ar: Error: phase error on all_modes.o
ar: Error: phase error on analysis.o
ar: Info: filename check_element_range.o truncated to check_element_r
ar: Error: phase error on check_element_r
ar: Error: phase error on check_prop.o
ar: Error: phase error on comparison.o
ar: Info: filename draw_eigenmode.o truncated to draw_eigenmode.
ar: Error: phase error on draw_eigenmode.
ar: Error: phase error on edit_prop.o
ar: Error: phase error on eigen_info.o
ar: Info: filename eigenmode_scale.o truncated to eigenmode_scale
ar: Error: phase error on eigenmode_scale
ar: Info: filename eigenvalue_test.o truncated to eigenvalue_test
ar: Error: phase error on eigenvalue_test
ar: Info: filename elasticity_matrix.o truncated to elasticity_matr
ar: Error: phase error on elasticity_matr
ar: Error: phase error on examine_modes.o
ar: Error: phase error on hit_mode.o
ar: Error: phase error on i4_stiff.o
ar: Error: phase error on i6_stiff.o
ar: Info: filename individual_prop.o truncated to individual_prop
ar: Error: phase error on individual_prop
ar: Error: phase error on l4_stiff.o
ar: Error: phase error on l6_stiff.o
ar: Info: filename literal_display.o truncated to literal_display
ar: Error: phase error on literal_display
ar: Error: phase error on material_prop.o
ar: Error: phase error on overall_prop.o
ar: Error: phase error on q4_stiff.o
ar: Error: phase error on q8_stiff.o
ar: Error: phase error on s3_stiff.o
ar: Error: phase error on s5_stiff.o
ar: Error: phase error on scroll_mode.o
ar: Error: phase error on select_mode.o
ar: Error: phase error on sort.o
ar: Error: malformed archive (at 68)
I tried creating an archive with a group of c objects and the ar achive
gets created with no more then an error message complaining about the
length of a file name. Does anyone know what is going on here? Can anyone
suggest a fix?
Paul Puglia : puglia@{cucevx.civil,cunixc.cc}columbia.edu
Dept. of Civil Engineering
Columbia University