libE77/Labort.o: missing

craig@jcb-sc.com craig@jcb-sc.com
Fri Apr 30 23:15:00 GMT 1999


>I am trying to compile the 1.1.2 release on a Linuxppc/4.1 machine.  It dies
>with the following error:
>make[4]: Leaving directory `/opt/src/egcs-1.1.2/powerpc-unknown-linux-gnulibc1/libf2c/libU77'
>objs=""; for i in abort derf derfc ef1asc ef1cmc erf erfc exit getarg getenv iargc signal system flush ftell fseek access besj0 besj1 besjn besy0 besy1 besyn chdir chmod ctime date dbesj0 dbesj1 dbesjn dbesy0 dbesy1 dbesyn dtime etime fdate fgetc fget flush1 fnum fputc fput fstat gerror getcwd getgid getlog getpid getuid gmtime hostnm idate ierrno irand isatty itime kill link lnblnk lstat ltime mclock perror rand rename secnds second sleep srand stat symlnk time ttynam umask unlink vxtidt vxttim alarm; do objs="$objs libE77/L$i.o"; done; \
>  ar rc libg2c.a $objs
>ar: libE77/Labort.o: No such file or directory
>make[3]: *** [libg2c.a] Error 1
>make[3]: Leaving directory `/opt/src/egcs-1.1.2/powerpc-unknown-linux-gnulibc1/libf2c'
>make[2]: *** [all] Error 2
>make[2]: Leaving directory `/opt/src/egcs-1.1.2/powerpc-unknown-linux-gnulibc1/libf2c'
>make[1]: *** [all-target-libf2c] Error 2
>make[1]: Leaving directory `/opt/src/egcs-1.1.2'
>make: *** [bootstrap] Error 2
>
>I thought I would report this - I didn't see it explicitly listed in the FAQ,
>though a mention was made of general f77 problems (which I assume this is
>related to?).

There isn't enough info for me to figure out the problem -- though I
don't have the same kind of system.  Looks like you're using GNU make,
which is important, though it's possible you need a more recent
version.

See the FAQ on reporting bugs.  In particular, a lot more than just a
snippet of the build output is needed.  A snippet like that is to
figuring out the source of the problem as a sample of blood from a
shower drain is to determining the identity of a murderer -- in rare
cases, it might be enough, but having access to the whole crime scene
usually works better.  :)

        tq vm, (burley)



More information about the Gcc-bugs mailing list