On Thu, Mar 03, 2005, Faux_Pseudo wrote:

> make install bombs because 
> cp AUTHORS BUGREPORT COPYING CREDITS ChangeLog FAQ NEWS README REQUIREMENTS 
> TODO /usr/local/share/plucker/doc
> cp: cannot stat `TODO': No such file or directory
> make: *** [install-data] Error 1

This is my fault; I removed the TODO file from the source package,
but forgot to remove it from the Makefile. Still, most users that
"build" Plucker on their own would probably use the snapshot to
get a more recent package than what is included in 1.8. In that
case you wouldn't run into this problem.

> Each of those links is a dead link. The actual locations should point
> to files in /usr/lib/python2.3/site-packages/PyPlucker/ 

'make install' doesn't create any symlinks, so those links you
probably created when running install-plucker.

> So then we try and continue 
> plucker-build -f file
> 
> Which results in:
> exactly the same error as above

I don't know why you can't remove files from your /tmp dir; never
seen that problem before.

> But this does work.

Well, when you run plucker-build with the -c argument it will just
write the data to the cache directory; don't know *why* you want to
do that, but if you look in ~/.plucker/cache I guess you will find
some files in it...

When you use -f it will, as you found out, create a Plucker document.

> Version two:  this one is mostly a rant because using the 
> install-plucker in the unix dir shouldn't have so many issues.

The install-plucker script has been deprecated for quite a while
and is not included in any of the binary packages any longer...

> running it as sudo results in:
> 
> gmake: *** [palmos_client] Error 2
> Traceback (most recent call last):
>   File "./install-plucker", line 140, in ?
>     os.symlink(os.path.join(MOD_DIR, "PyPlucker", "Spider.py"), 
> os.path.join(BIN_DIR, "plucker-build"))
> OSError: [Errno 17] File exists

Once again, I don't know why you can't remove files on your system...

> Why is it going into viewer-GTK+2-POSIX ? 

Because you told it to.

> Didn't I tell it to not
> build gtkviewer with the --disable-gtkviewer option?  

Nope, not when you *after* running the configure command decide to
run the install-plucker script (that will run the configure script
using the settings you select and since the script is deprecated 
it has not been updated to include any options for the GTK viewer).

> So I add a "install-prc-files: : " section in
> /home/faux/plucker-1.8/viewer-GTK+2-POSIX/Makefile just to get past
> it.  I get the same error again.  Why?  Because
> /home/faux/plucker-1.8/viewer-GTK+2-POSIX/Makefile was overwritten by
> some portion of theinstall-plucker script.

Because the script will run configure...

/Mike

_______________________________________________
plucker-list mailing list
[email protected]
http://lists.rubberchicken.org/mailman/listinfo/plucker-list

Reply via email to