On Sun, 20 Nov 2005 03:54:46 +0000 Ben Fowler <ben.the.mole@...400...> wrote:
On 11/19/05, Steven P. Ulrick <lists-inkscape@...1052...> wrote:
On Sat, 19 Nov 2005 10:52:42 -0600 aaron@...749... wrote:
Steven P. Ulrick wrote:
On Sat, 19 Nov 2005 18:03:46 +0300 Alexandre Prokoudine <alexandre.prokoudine@...400...> wrote:
On 11/19/05, Ben Fowler wrote:
Sephen, if you want to approach it from that angle then one possibility ...
Why on Earth? Just replace current ja.po with the old one
But I will gladly try it again.
This seems kinda weird to me. (
I have discovered the following:
Now I get the following error: ... then mv -f "widgets/.deps/sp-color-preview.Tpo" "widgets/.deps/sp-color-preview.Po"; \ else rm -f "widgets/.deps/sp-color-preview.Tpo"; exit 1; \ fi mv: cannot stat `widgets/.deps/sp-color-preview.Tpo': No such file or directory
That error is probably owing to the directory referenced as 'widgets/.deps' not existing.
You could create that directory and retry.
Obviously something in autogen, configure or an upstream make should have created it.
When I get this problem I remove all files in the tree called 'Makefile' using find, and recreate them with configure.
Ben
Hello, Ben After I got that error, I grabbed a fresh copy of Inkscape from CVS and recompiled, with complete success! Check out my comments in my message on this thread that has " - FIXED" appended to the end of the subject line. The release tarballs of Inkscape were "detecting" a version of intltool that does not come with FC3 and had never been installed on my system. Perhaps it is bundled with the Inkscape tarball? IF that is the case, it "could" account for the fact that I could compile from release tarballs but not from the CVS tree.
The only thing I know for sure is that a version of intltool that does not come with FC3 and that I did not install was somehow detected by the Inkscape compilation process, resulting in a perfect build (from a release tarball). Then I grabbed the SRPM of intltool from FC4 and rebuilt and updated to that version. The build attempt that you refer to in the message I am replying to immediately followed my upgrade to the FC4 version of intltool. I then got a fresh copy of Inkscape from CVS and SUCCESSFULLY compiled it :) The only known difference being the version of intltool installed from RPM on my system now matched the version that the Inkscape tarballs somehow had been detecting. How this happened, I have not a clue :) I "suspect" that that different error that I referred to in the message that you are replying to may have had to do with the, oh let's say different things I was grasping at trying to fix this. But I am sure that I have attempted compiling from fresh copies of Inkscape enough times (before and after a fresh install of FC3 last week) that the problem lies either with Fedora Core 3's version of intltool, or in Inkscape's detection of it. Oh yeah, check out a recent email of mine in this thread that shows that though autogen.sh and configure both find the same version of intltool, they seem to be looking for different versions. What all this means, I haven't a clue.....
Thank you very much for your interest and attention to this problem since I first brought it to this list. Steven P. Ulrick