isn't the way to do this to mod Woof a bit, create a build a toolchain (chroot environment thing) and start compiling from source..? Barry does that with T2, I'm sure looking at things like ttylinux build scripts and others like will help make an arm supported woof..._________________Akita Linux, VLC-GTK, Pup Search, Pup File Search

I believe the best way for the ARM porting effort is same as the solution for the 64-bit Puppy problem.

Puppy relies on many binary packages (e.g Busybox, Bash) that were originally built on Puppy 2.x or 4.x and Barry kept using them in 4.3.1, which means they're still with us at 5.3.

I convinced Barry he should move all those to one repository, which is the "Packages-puppy-common-official" repository. My idea was to have just those annoying core packages there, but Barry put much more than that, mostly Wary packages that are compatible with most Puppies.

The fact these are binary packages means it's impossible to port Puppy to other architectures, since they aren't portable.

The solution for this problem is simple - automate the procedure needed to compile those. I wrote build scripts for most of those, which work with my package building tool, Builder. All I need to port Puppy to x86_64, theoretically, is a way to build 64-bit packages from a 32-bit Puppy.

What I'm doing now is something I've experimented already - a 32-bit Puppy with a 64-bit kernel (e.g a Puppy that can run both 32- and 64-bit stuff) that I can use to cross-compile all those packages for x86_64.

Similarly, I could build a cross-compiler that runs on x86 but produces ARM binaries. Once these are ready, I could use Woof to produce an ARM Puppy.

However, it's a 'lil bit more problematic - Woof has many executables and binary files. This is totally against any programming convention I'm aware of, but I won't criticize Barry's decisions.

The bottom line is that bootstrapping a new Puppy for another architecture requires four main things:
1) Replace all binaries in Woof with ones native to the new Puppy (well, except those used to build it - they need to match the machine Woof runs on)
2) Build that Puppy from a Puppy that can run its binaries, that's a Woof requirement.
3) All those crappy traditional packages.
4) A kernel.

Once we have all those, we can build some sane Puppy for ARM, x86_64 or any architecture, that has a compiler and everything needed to build the rest of it.

That's what I do with my current puplet, Guy Dog - it is built from Debian packages (I mean, just the base system) and all applications (and even more than that, even stuff like D-Bus and Bash) are built on top of it, automatically.

It shouldn't be that hard to port Puppy, but it's time to cut those ties between Puppy and x86._________________My homepageMy GitHub profile

I think checking out ttylinux might help here... it is based on build scripts and chroot .... libc, gcc, busybox et al can all be very easily built for arm, and the arm stuff is built from within its own toolchain (which you can build to your liking as well), as mentioned would be needed...

I have no knowledge of this sorta stuff really, but even I eventually got a working ARM based toolchain ready to go, inc busybox, gnutils, etc, etc ... I just don't have anything to test it on! (or the inclination to be honest, it's pretty 'barebones'!)

Maybe PARM artwork in the eyecandy section? (thread not created yet)
In an ideal world you would create a hosted location
such as:
http://img821.imageshack.us/img821/1644/parm2.png
. . .
which can be linked to directly from the source to wiki, forum and other interested parties as the geek party begins (Raspberry Pi and hot dogs will be served)

. . . and maybe igu would like an improved calf for his avatar?
. . . mind you 'outsider art' is big at the moment I believe . . .

However, it's a 'lil bit more problematic - Woof has many executables and binary files. This is totally against any programming convention I'm aware of, but I won't criticize Barry's decisions.

The bottom line is that bootstrapping a new Puppy for another architecture requires four main things:
1) Replace all binaries in Woof with ones native to the new Puppy (well, except those used to build it - they need to match the machine Woof runs on)
2) Build that Puppy from a Puppy that can run its binaries, that's a Woof requirement.
3) All those crappy traditional packages.
4) A kernel.

I am aware of the problem, and have posted some thoughts about fixing Woof to be multi-arch:

If I believed in such things it could only be a great omen
For those of a more sensible build of mind . . .
Barry has a new ARM motherboard and will be developing Woof power with ARM shortly . . .
http://bkhome.org/blog/?viewDetailed=02596_________________Puppy WIKI

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