How to Compile Source Code in Empty Crust?

[tommyhill]

I recently installed Empty Crust onto a 500 meg drive and would like to install a few programs directly from the source code. SInce Empty Crust is a bare bones operating system, what exactly do I need to compile source in Empty Crust ?

Tommy

[Pizzasgood]

You need the usr_devx.sfs file for Puppy 1.0.7.
http://puptrix.org/isos/Puppylinux-offi ... velopment/

Just download that and put it in /mnt/home (the same location as pup_001). If it's a full-hd install, I believe it goes in / instead. Then reboot, and you should be set. Unless you want to recompile the kernel or something, because Puppy doesn't include the kernel headers. Those would be in a separate package, but I don't know where the ones for the Puppy 1.x.x series would be. You shouldn't need them though, unless compiling kernel modules or something.
EDIT: maybe http://puptrix.org/isos/Puppylinux-offi ... ernel-2.6/

Actually, all Puppies use an add-on module for the development tools, not just Empty Crust. In the newer ones, they're called devx_xxx.sfs instead, but it does the same thing.

[tommyhill]

Thanks Pizzagood... I always did like pizza :-)

Have you ever re-compiled the kernal on Puppy ? I was wondering if it is difficult to accomplish or is it easy to do like compiling the source code...

[caka]

I am trying to compile the kernel too. Here there is a manual:

http://www.puppylinux.com/development/compilekernel.htm

I have some problem about it.

I am Spanish and don´t understand english very well. Sorry for my bad english.

Luck.

[Gn2]

Do you want to just re-compile the modules - or the Kernel ?
BK's documentation is for modules only !

'Mrproper' or 'clean' should not be used > (reuse orignal Puppy version .config > which "should" be supplied in development tool Pkge)

Code: Select all

 make oldconfig

Once new kernel image is confirmed OK - if wished, mrproper may be used -
Keeping old build database info just takes up a bit of extra space 'tho - & speeds subsequent kernel compiles

See http://www.digitalhermit.com/linux/Kern ... HOWTO.html
Included with downloaded kernel sources is the Documentation folder containing file applying- patches.txt
Any desired module patches must be applied prior to any kernel/module compiling.

If they pertain to kernel version changes - they MUST be applied> and in proper sequence !

(The syntax for 2.6_xx kernels BTW in both Doc sources is incorrect but still usable)

If your Pkge sources are re-distributed for others - all must be compiled in "clean environment "
Ensuring no inadvertant optional dependencies are compiled in to binaries.

BACKUP old .config & bzImage before changing any system critical items such as the kernel or module !
It is highly recomended the kernel sources be stored for usage in own created folder
NOT /usr/src/linux <- which is symlink only to true full version name.

That keeps original headers & any upper-level or sub makefiles build info &/or symlinks separate from new.

HTH

[Pizzasgood]

I am trying to compile the kernel too. Here there is a manual:

http://www.puppylinux.com/development/compilekernel.htm

I have some problem about it.

I am Spanish and don´t understand english very well. Sorry for my bad english.

Luck.

Well, that post was pretty decent. If it makes you feel any better, mi español no es muy bueno tampoco. I skimmed your topic earlier today, though, and was amazed at how much I did understand. On the other hand, I couldn't remember the word "tampoco" just now, and had to look it up

I've never compiled a kernel, but I've heard both good and bad comments about it, so I guess it's one of those iffy things.