Puppy Linux Discussion Forum

[PeterSieg]

Howto fead Puppy to become a 'fat Puppy'
---------------------------------------------------

Or, how to install GCC compiler

*** Use this at your own risk ***

Get the following slackware packages from:
http://ftp.gwdg.de/pub/linux/slackware/slackware-10.1/slackware/d/

[PeterSieg]

PS

[Lobster]

Good job Peter

I was just about to try this

- then I thought
You are too young and inexperienced in the ways of the Puppy 'Force'
(I wanted a print out ) but could not . . .

So what I am gonna do, as a half way house, is fire up the olde
Vector Linux 5.00 beta and try some compiling in there
Then If I am able, will try out your stuff - I did have a look at tinycc
('av a look at the How to section)
which is VERY cool and easy - but I can not find sufficient info on
C programming with it
and C is pretty hard for me - "ellow Whirled" is about my limit . . .

- however this is real c
real c in Puppy - Yo Ho ho
(Christmas has come early)

[PeterSieg]

Now we will continue to X11 programming...

from:
http://ftp.gwdg.de/pub/linux/slackware/slackware-10.1/slackware/x/

get:

[BarryK]

The next Pup, v1.0.3, will have Bash, so post-install scripts will be happier maybe.

Note, I have kept Busybox Ash, and /bin/sh still runs Ash/ /bin/bash is now the full Bash.
I will upload News page with this right now...

Oh and yes, this is great what you're doing...
I'm keen to follow your instructions and fatten up Puppy also!

[GuestToo]

bash scripts often will not work quite right with the busybox replacements for the gnu utils

i symlinked /bin/sh to bash so bash runs whether it's called by /bin/bash or /bin/sh

i set SHELL=/bin/bash so it is the default shell that rxvt uses

i symlinked /bin/ash to busybox so i still have busybox's ash if i want it (i mostly use it to see if a script will work in ash as well as bash)

bash could be put in /usr (or could even be on the hard drive) ... if you symlink /bin/sh to a drive that will be unmounted when Puppy shuts down, /bin/sh needs to be symlinked to busybox before the drive is unmounted

[PeterSieg]

Hi.

get TinyGL from:
http://fabrice.bellard.free.fr/TinyGL/

untar it and cd into it. Then just say 'make' and wait a few minutes

See the results here:


The colors are not correct in x24 display? Hardcopy was taken in x16.
For the one's, that just want's to see 'mech' in Puppy, I have
attached the compile app...

PS

[PeterSieg]

Here is 3d_clock...

PS

[Lobster]

It is not right. It is not even fair.

I managed to get Puppy on the HD (previously holding Vector 4.6) using the John Murga Opera Puplet (by using a selection 2 boot - no reading or saving from HD) Thus it was easy to do a Number 2 Install and Grub install (I found installing to hda1 rather than MBR worked OK)

Now to C
I tarred - and untarred(detarred?) and eh . . .
went wrong somewhere . . . [grumble . . .mutter . . .]

Humph!
So I thought I would do some sulking - luckily Menno has shown me how to do a random function in tinycc - no time to sulk - programming to experiment with . . .

PS. (I hear GCC is not that fast anyway . . . sour grapes? . . . moi? . . .)

[BarryK]

[BarryK]

[GuestToo]

it sounds like you are not making full use of bash

i have /bin/ash symlinked to busybox, but the only time i use ash is to see if a script i wrote will also run in ash

if you put SHELL=/bin/bash in /etc/profile, then rxvt and aterm will use bash

if you have bash in /usr/bin (that's the way i did it, for the same reason, to not make image.gz bigger ... except i have bash in /root now) ... you can symlink bash to /bin/sh, and bash will completely replace busybox's sh (scripts starting #!/bin/sh will use bash instead of busybox) ... i've been running Puppy like that for a long time, and have not had problems with it

what i do is basically this:

i have a script (/usr/bin/bash-on) to enable bash (note that it executes /usr/bin/bash not /bin/sh):

#!/usr/bin/bash
ln -sf /usr/bin/bash /bin/bash
ln -sf /usr/bin/bash /bin/sh
ln -sf /bin/busybox /bin/ash

and i have a script (/usr/bin/bash-off) to disable bash

#!/usr/bin/bash
ln -sf /bin/sh /bin/busybox
# fix /bin/bash if rc.reboot is likely to run a script that runs /bin/bash

bash-on would probably execute from rc.sysinit or maybe rc.local0 and bash-off would execute from rc.reboot (you need this or you lose the shell when /usr unmounts ... if you copy bash to /bin/bash then bash-off isn't needed ... i don't know whether this really uses more ram or not, with the way the kernel caches stuff)

when bash is symlinked to /bin/sh, a script that runs /bin/sh will really be running bash ... but bash will behave as though it was sh ... so it will use /etc/profile like sh would ... it will not use .bashrc ... you might find that if you kill X and restart X, that the environment variables in /etc/profile have been lost ... it might be necessary to source /etc/profile in $HOME/.bash_profile

anyway, the way i did it was to completely replace busybox with bash ... and Puppy seems to run with little or no problems that way

actually, i find the main benefit of using bash is .bash_history

[Jesse]

Hi Lobster,

Now that I'm using 1.0.2 (off CD) and I have it set up to use tinycc, I could tar up my /root/.usr directory so that you could easilly have tcc for your computer.
If I bz2 it the file is about 2.2MB. There are lots of C header files in it. Installing would be as easy as downloading and untaring once.

Jesse

[Lobster]

That would be kewl - have sent you a private message.

`What the MasterPups are up to is all very well (I am just jealous - 'coz I can't do it) but a tcc with a Gui interface IDE type environment would be one of the (yet more things) that makes puppy unique

. . . now all I have to do is learn C
gosh you sure have to be smart to be penguinated

[Flash]