Are you sure? I know that Slacko has different libraries but
I don't have any problems with installing this version of mtpaint
in Slacko 5.6 or 5.7

I did have problems installing the debian packages in anything other than
Lucid Puppy.

But I made those packages specifically for Ubuntu Lucid and Tahr.

________________________________________________

Edit - there is a 64 bit version of Slacko. Software compiled for
32 bit won't work on a 64 bit OS (unless there some type of
emulator)
__________________________________Last edited by don570 on Sat 12 Apr 2014, 13:05; edited 1 time in total

The way to truly make sure is to run 'ldd mtpaint' on a live Slacko system. But apart from some miracle, the conflict will be there just as I described.

Quote:

I know that Slacko has different libraries but
I don't have any problems with installing this version of mtpaint
in Slacko 5.6 or 5.7

These problems can be not immediately obvious; sometimes it is GTK+, not mtPaint, that gets its PNG loader failing. In such cases, the only sign of something wrong may be broken file/directory icons in the builtin fileselector. If the theme used in GTK+ isn't itself heavily PNG-based, nothing else in mtPaint GUI will be affected, for I do not use GTK's stock icons anywhere else.
But which PNG loader is to fail, is entirely at the mercy of the dynamic loader and the Almighty Random.

Quote:

But I made those packages specifically for Ubuntu Lucid and Tahr.

Building mtPaint with a subset of libs taken from another system is simple. At least, it is when the libs are downloadable as separate packages (like those from Ubuntu or Slackware). Just unpack them into some directory, and configure mtPaint this way:
./configure --fakeroot=somedir/usr

mtPaint's "--fakeroot=" configure option is only remotely related to the eponymous program; it strives to achieve a like effect, purely through the use of shell macros and path substitutions. Precisely because I did not want to make 'fakeroot', which no distro installs by default, into a requirement.

Libtiff is a library for reading and writing Tagged Image File Format (abbreviated TIFF) image files. Maybe search "libtiff" in your Pup's PPM for an available package to install and try...?

Bob

thanks for the reply, Bob.

would that being missing alone be enough to stop it from launching? anyway, i checked the PPM and found i have one of the five things labeled with "tiff" installed, but none are that libtiff.so4 file. (i think i tried to hunt it (or whatever an earlier error message gave) down as a deb before, having already failed at getting it through the PPM (since updated at least twice and so was worth another shot).

you think installing the other four things may break something else?

...kinda sucks--i really like mtpaint.

edit: added everything with libtiff that i could find in the PPM. didn't break anything but neither did it fix the problem.

edit: added everything with libtiff that i could find in the PPM. didn't break anything but neither did it fix the problem.

How so? Do you now have an /usr/lib/libtiff.so.* at all, and if you do, then what is the number after .so. ?
Anyhow, it might have been that libtiff.so.4 is not the *only* lib that is missing on your system; running "ldd mtpaint" would report what (if anything) is missing now.

Make sure that you are running a 32 bit version of Puppy linux
because there are some 64 bit versions available but they don't
run the 32 bit version of mtpaint.

Recent versions of linux are using libtiff.so.5 however it
is much larger in size apparently to open
various compressed tiff files .

I compiled this mtpaint in Puppy linux 4.3.1
which is quite old.

Making a link is simple

Code:

ln -s libtiff.so.5 libtiff.so.4

________________________________________________

Posting from a phone with an iffy connection...

Don, I tried your suggestion and it said it couldn't do it because libtiffso4 was already installed. (Launching it gave the same error about it missing, though.) It is a 32 bit puppy (571), but after taking wjaguar's suggestion, "/.mtpaint not found" or doesn't exist--not by the machine now, but that at least seems solvable. Less of a paradox in any event.

Guess i'll try to track it down. Thanks for the help, guys.
(did; clicking the cog-like icon didn't work either)

I believe Barry Kauler made Puppy Precise differently than
his previous puppies.

He installed full files of liftiff.so.5 and libtiff.so.4 not links.
You can check this in the lib folder.

I think he did this to have compatibility with older pet packages
and with Ubunutu debian packages. Maybe an installation of a repository
package has removed the full libtiff.so.4 and replaced it with a link??

You should try my precise debian package which just needs liftiff.so.5
to be installed.

here's how: there was a libtiff.so.4.3 in usr/lib and two dead links (libtiff3, libtiff4) in /lib. i renamed a copy of libtiff.so.4.3 libtiff.so.4 and dragged the file as a link to /lib. both the dead links repaired themselves and mtpaint launched.

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot vote in polls in this forumYou cannot attach files in this forumYou can download files in this forum