Compilation errors

Compilation errors

Post by Richard Stoparczy » Fri, 02 Feb 2001 06:53:49


I am trying to compile Apache 1.3.17 on Sun 2.6 and get the following errors
with gcc:

# make
===> src
make[1]: Entering directory `/apps/apache_1.3.17'
make[2]: Entering directory `/apps/apache_1.3.17/src'
===> src/os/unix
rm -f libos.a
ar cr libos.a os.o os-inline.o
make[3]: ar: Command not found
make[3]: *** [libos.a] Error 127
make[2]: *** [subdirs] Error 1
make[2]: Leaving directory `/apps/apache_1.3.17/src'
make[1]: *** [build-std] Error 2
make[1]: Leaving directory `/apps/apache_1.3.17'
make: *** [build] Error 2

does anyone know what the command "ar" is or what I am doing wrong?



Compilation errors

Post by Dr. Peter Dintelman » Fri, 02 Feb 2001 17:48:59


Quote:> I am trying to compile Apache 1.3.17 on Sun 2.6 and get the following
> with gcc:

> # make


Quote:> make[3]: ar: Command not found

    ar is /usr/ccs/bin/ar. Add /usr/ccs/bin to your $PATH
    if it is not already included. It was installed by the
    SUNWbtool package on my box.

Quote:> does anyone know what the command "ar" is

    It comes with a manpage ;-)

    Best regards,

        Peter Dintelmann


1. Kernel compilation error: GCC Internal errors 6 and 11

Hello all-
   I'm having problems compiling the kernel in a variety of
situations. Here is the simplest: I install Slackware 2.2 off the
Infomagic March 1995 CD set (kernel 1.2.1) and then do "make config"
followed by "make dep; make clean" and finally just plain "make"

   During the last make, GCC periodically halts with an internal error
either 6 or 11. This has happenned with both GCC 2.6.3 and GCC 2.5.8.
It has also happenned when compliing the 1.3.25 kernel.
   If I delete the incomplete .o file produced at that step and
re-run make, it will crash at the same point (it will skip the files
that are already compiled becuase they are up-to-date). If I enter
the command the failed from the proper director (using cut and paste),
the object file is produced correctly, without error. I can then run
"make" again and it will crank away for a while and then crash again.
It seems to crash at the same files each time. If I continue the process
of manually compiling the .c files that there were problems with,
I *DO* end up with a working kernel!!!

   What's wrong, here? I'm worried that there may be something quirky
with my system's SIMMs. It is a fairly new system:
   P-120 with 32MB of memory, 25MB of swap.

Your comments are greatly appreciated!

Mike Phillips

2. X Problem

3. compilation error: "Error: namespace is not defined."

4. slashdot

5. AFS compilation error "configure: error: no available sys_call_table access method"

6. help with mediavision sb, cdrom

7. Kernel/compilation errors, eth0 errors

8. Help: how can I mail a file as attachment?

9. Compilation errors on Solaris2.7

10. 1.3.57: compilation error

11. -2.4.21-rc6-ac1 _critical_ compilation errors

12. Crack 5 Compilation Errors

13. kernel compilation errors