It can be that ati needs other patches also which you need to manually include into it after manually extracting ati package. It depends on kernel version and used ati package version.

OK, I found these patches catalyst-patch-3.8-legacy.tar.gzwhich you posted here
and applied them all except for the arch-fglrx-3.8.patch (i assumed i did not require it)
After applying those, i was able to create a slackware package.

For future reference, could you please explain the correct method of applying those patches.

@ Q5sys

Q5sys wrote:

What you could do is install strace from the slackware repo and have that output to a file when you run the ATI run file.
Then post that and I may be able to find out what's not being found.
I'd need to know what tools are missing to be able to provide them for you.

Thank you for the suggestion,
prior to applying the patches mentioned above, i did as you suggested and installed strace
but i didn't really know what to do with it, so i ran it like this:

What you could do is install strace from the slackware repo and have that output to a file when you run the ATI run file.
Then post that and I may be able to find out what's not being found.
I'd need to know what tools are missing to be able to provide them for you.

Thank you for the suggestion,
prior to applying the patches mentioned above, i did as you suggested and installed strace
but i didn't really know what to do with it, so i ran it like this:

Was that command correct, or should i have used something different (could you provide an example)
also do you have any decent links that explain what the output means.

So, we can say that my initial problem is solved,
but.... how did simply applying some patches miraculously resolve those 'missing tools'

Once again, thanks to you both
CatDude

P.S
Any progress on v2.0

.

You ran Strace properly, that 1000 lines of gobbledegook as you put it it should hold the answer. But I see you're problem is resolved from following the advice from the other thread. As to Strace Output and making sense from it, thats really well beyond the context of this thread, but a simple google search should give you some links which may explain what all you are seeing. Basically it logs and reports the status of all system calls that a program makes when trying to run or when its running. Also gives you a good idea of just how much is going on in the background when you dont see anything. lol.

As for how the patches fixed your 'missing tools', the problem most likely is that the installer was looking in the wrong place for the tools, so it was reporting them missing. IE, it was looking in say /usr/bin for something, and not finding it becuase it was in /usr/local/bin. I just made up that example, but if it couldnt find it in /usr/bin it may report it as missing because its not where it thinks it should be. Without looking at the patch I have no clue, but it may have been an issue like that.

V2 is taking a bit longer than I wanted, because I just havent had the time to work out the last few kinks and polish it up a bit.
And to be honest, due to the time its taken, some of the core slackware components have been updated, so I'm thinking of updating those as well. Just pulled down a local copy of the most recent slackware-current mirror to update some things.
I was previously going with the 3.9.4 kernel as shown previously, but Im thinking of maybe going with the 3.10 branch, if I can build it without issue.

smokey01 wrote:

Q5sys is there any way to increase the personal storage file in slackbones?

Thanks

Hmm... That probably would be a good thing to include. lol.
I've never used the resize script that comes with Puppies... I just manually created the pupsaveresize.txt file in my /mnt/home directory and then put in the appropiate value. Its in MB. so for 256mb you'd just type "262144"
Then save it. Then on reboot it'll increase the save file that size.
That 'SHOULD' work for SB, since it uses the same save file system as FatDog.
I've never looked into how save files got expanded during a boot cycle. I'll see if JamesBond can shed more light on that._________________

I just manually created the pupsaveresize.txt file in my /mnt/home directory and then put in the appropiate value. Its in MB. so for 256mb you'd just type "262144" Then save it. Then on reboot it'll increase the save file that size.

I tried the above, it didn't work.

I also transported the Fatdog savefile tool to SB and it didn't appear to work either. The savefile does however appear to have increased in size but it is not recognised by the save file indicator in the task bar.

Change '256M' to '1G' or '2G' or '512M' or '141M' or whatever you want Make sure you use >> (two greater-than signs) and not > (one sign), if you accidentally use only one sign then goodbye savefile, hello frustration.

The Fatdog savefile tool should work but I haven't tested it myself, it could depend on some obscure tool Fatdog that isn't in SB._________________Fatdog64, Slacko and Puppeee user. Puppy user since 2.13.
Contributed Fatdog64 packages thread

I can cross-compile them to any other architecture. The list contains some Puppy-specific packages (e.g elspci) and I'm working on more build scripts for such packages.

I want to make the building of all packages under Packages-puppy-common-official automated, so we can port Puppy to x86_64 or any other architecture easily. It's an on-'n-off project I've been working on for months now.

Could you help me find a package that includes an xdootol prerequisite of libxdo.so.2 (64 bit version) please? thx!

Have you tried: http://www.smokey01.com/software/Fatdog64-600/xdotool-fd64.pet

Thanks smokey, that has given me what I need. Not sure why I couldnt pull that lib out of other pets though. I tried several of them from various sources and could not see that lib available in any of them when I unzipped them. Mustve been doing something wrong somewhere.