gomatam@ecs.umass.edu (04/10/91)
I have the foll problem with archive ar:
I have a bunch of files compiled under the foll:
f77 -O3 *.f
this is for a MIPS fortran compiler running on DEC 5000
this produces a bunch of .u files (NOT the usual .o)
supposedly, these are "ucode" optimized for speed, etc
I need to link these files with other fortran source code; the problem is
creating a library of these files using ar
I get an error "*.u is not in archive format"
The man page for "uld" has no info: although there is info on dealing
with the "nonoptimized" .o files
so my problem is :"How do i archive a set of files produced under the
above compiler option to create a library ?"
I tried looking at the manuals, but I'm new to this, and I couldn't find
one specifically for this: even suggestions for what to consult will
help me a lot
thanks
Badri
trevc@tecate.mips.com (Trevor Cotton) (04/17/91)
In article <13160.2803307b@ecs.umass.edu>, gomatam@ecs.umass.edu writes: |> I have the foll problem with archive ar: |> |> I have a bunch of files compiled under the foll: |> |> f77 -O3 *.f |> |> this is for a MIPS fortran compiler running on DEC 5000 |> |> this produces a bunch of .u files (NOT the usual .o) |> |> supposedly, these are "ucode" optimized for speed, etc |> |> I need to link these files with other fortran source code; the problem is |> creating a library of these files using ar |> |> I get an error "*.u is not in archive format" |> I don't know where this would be in the DEC documentation, but its documented in the MIPS Language programmers guide chapter 4. You should use the -j option to the compiler. The resultant .u files can then be archived e.g cc -j one.c cc -j two.c cc -j three.c ar crs libfoo.b one.u two.u three.u Not that the convention for ucode libraries is libname.b To load from a ucode library, use the -kl flag e.g cc -O3 file1.u file2.u -klfoo -o outprog Regards, -- --trevc--