Sorry if this is a repost -- it is not clear if the first one actually went
through.

I have been unsuccessful in compiling the boinc server several times.  I
finally got configure to not give any warnings.  There were previous
attempts to 'make' in spite of them.  I pulled the latest git this morning
(previous pull was Aug 21), and the file lib/md5.c was renamed to md5.cpp.
There were traces of the old name somewhere (possibly from my own previous
failed installs).  I did 'make clean' before each attempt.

Make wants to remake the target md5.c as well as md5.cpp.  Simply copying
the lib/md5.cpp file to lib/md5.c made it get past this part without
complaints (I did a diff of the cpp and a backup of the c file, and their
contents were identical).

I don't know if this is something I caused by trying to install so many
times, or if it's a bug.  To me, it is unexpected that it tries to rebuild
md5.c.  Is there something I need to clean up that isn't taken care of with:
make clean && ./_autosetup && ./configure --disable-client
--disable-manager && make

A snipped of the relevant portion of `make -d` when it was failing is below:

       File `libboinc_la-md5.lo' does not exist.
        Considering target file `md5.cpp'.
         Looking for an implicit rule for `md5.cpp'.
         Trying pattern rule with stem `md5.cpp'.
         Trying implicit prerequisite `md5.cpp,v'.
         Trying pattern rule with stem `md5.cpp'.
         Trying implicit prerequisite `RCS/md5.cpp,v'.
         Trying pattern rule with stem `md5.cpp'.
         Trying implicit prerequisite `RCS/md5.cpp'.
         Trying pattern rule with stem `md5.cpp'.
         Trying implicit prerequisite `s.md5.cpp'.
         Trying pattern rule with stem `md5.cpp'.
         Trying implicit prerequisite `SCCS/s.md5.cpp'.
         No implicit rule found for `md5.cpp'.
         Finished prerequisites of target file `md5.cpp'.
        No need to remake target `md5.cpp'.
        Considering target file `md5.c'.
         File `md5.c' does not exist.
         Looking for an implicit rule for `md5.c'.
         Trying pattern rule with stem `md5'.
         Trying implicit prerequisite `md5.w'.
         Trying pattern rule with stem `md5.c'.
         Trying implicit prerequisite `md5.c,v'.
         Trying pattern rule with stem `md5.c'.
         Trying implicit prerequisite `RCS/md5.c,v'.
         Trying pattern rule with stem `md5.c'.
         Trying implicit prerequisite `RCS/md5.c'.
         Trying pattern rule with stem `md5.c'.
         Trying implicit prerequisite `s.md5.c'.
         Trying pattern rule with stem `md5.c'.
         Trying implicit prerequisite `SCCS/s.md5.c'.
         Trying pattern rule with stem `md5'.
         Trying implicit prerequisite `md5.w'.
         Looking for a rule with intermediate file `md5.w'.
          Avoiding implicit rule recursion.
          Trying pattern rule with stem `md5.w'.
          Trying implicit prerequisite `md5.w,v'.
          Trying pattern rule with stem `md5.w'.
          Trying implicit prerequisite `RCS/md5.w,v'.
          Trying pattern rule with stem `md5.w'.
          Trying implicit prerequisite `RCS/md5.w'.
          Trying pattern rule with stem `md5.w'.
          Trying implicit prerequisite `s.md5.w'.
          Trying pattern rule with stem `md5.w'.
          Trying implicit prerequisite `SCCS/s.md5.w'.
         No implicit rule found for `md5.c'.
         Finished prerequisites of target file `md5.c'.
        Must remake target `md5.c'.
make[2]: *** No rule to make target `md5.c', needed by
`libboinc_la-md5.lo'.  Stop.
make[2]: Leaving directory `/usr/local/src/boinc/lib'
Reaping losing child 0x7796d0 PID 35173
make[1]: *** [all-recursive] Error 1
Removing child 0x7796d0 PID 35173 from chain.
make[1]: Leaving directory `/usr/local/src/boinc'
Reaping losing child 0x21ad690 PID 35172
make: *** [all] Error 2
Removing child 0x21ad690 PID 35172 from chain.
_______________________________________________
boinc_dev mailing list
[email protected]
http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.

Reply via email to