in reply to why does PAR want make.mo anyway?
Those .mo files are compiled message catalogs (in the context of national language support). More specifically, MO stands for "machine object", as opposed to PO for "portable object" — see the GNU gettext manual for in-depth background info.
What I'm wondering is... are you sure this is really the reason that PAR is failing? Are you somehow trying to include make in the package? What you've posted looks like a line of strace output (rather than an error message of PAR (though I could be wrong...)). If so, it might not indicate the actual problem... In other words, it's pretty normal for a program to look for all kinds of files and not find them.
What command did you run, and how exactly does it "not work"?
|
|---|
| Replies are listed 'Best First'. | |
|---|---|
|
Re^2: why does PAR want make.mo anyway?
by danmcb (Monk) on Sep 14, 2007 at 19:36 UTC | |
by derby (Abbot) on Sep 14, 2007 at 19:57 UTC |