Sunday, February 22, 2009

how to solve rmake build errors

1. First, all things have a source... all errors step from one single command failing. So, locate this failing command, find the cause and find the solution.

2. You can find out where a specific file comes from, using conary q --path or conary rq --path .

3. "No package blah found. Perhaps you should add the directory containing `blah.pc'."
Missing dependencies is a common error. Usually configure uses pkg-config to check the .pc files. The default dir containing *.pc is /usr/lib/pkgconfig (or /usr/lib64). So is /usr/lib/pkgconfig/blah.pc, apply it to conary q/rq --path and solve it.

4. Other missing file errors can be solved similarly, for example missing /usr/bin/git, missing /usr/include/GL/gl.h (from #include )

5. "flex: fatal internal error, exec failed"
Using strace/ltrace, for the particular case I encountered, the error turned out to be 'GNU M4' missing. conary q --path `which m4` tells me it's m4:runtime. Done.

6. Sometimes it fails just because of Internet problems, like this one,
InternalServerError:
There was an error contacting the repository. Either the server is
configured incorrectly or the request you sent to the server was invalid.

0 comments:

Post a Comment