NSLU2-Linux
view · edit · print · history

Puppy.BuildingPuppy History

Hide minor edits - Show changes to markup

January 30, 2007, at 06:01 AM by v12mike -- added link to alternative toolchain source
Changed lines 23-24 from:

I found that make toolchain failed a couple of times for non-existent directories, but making the required directories manually seemed to fix the problem.

to:

I found that make toolchain failed with the version for CVS above, but succeeded using the instructions at http://www.nslu2-linux.org/wiki/Optware/AddAPackageToOptware.

January 29, 2007, at 06:29 AM by v12mike --
Added line 8:
 cvs -d:pserver:anonymous@nslu.cvs.sourceforge.net:/cvsroot/nslu login
January 28, 2007, at 09:57 PM by v12mike -- added note to make toolchain step
Changed lines 22-23 from:
to:

I found that make toolchain failed a couple of times for non-existent directories, but making the required directories manually seemed to fix the problem.

January 28, 2007, at 05:25 PM by v12mike -- fixed cvs command line
Changed line 8 from:
 cvs -z3 -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/nslu co unslung
to:
 cvs -z3 -d:pserver:anonymous@nslu.cvs.sourceforge.net:/cvsroot/nslu co unslung
January 23, 2005, at 06:45 AM by peteru --
Changed lines 3-5 from:

First you need to have a working unslung development environment. Follow instructions at HowTo.CompileCrossTool to build a cross compiler environment.

After you have the crosstool environment, add /opt/crosstool/armv5b-softfloat-linux/gcc-3.3.4-glibc-2.2.5/bin to your PATH

to:

First you need to have a working unslung development environment.

Added lines 11-22:

Change into the unslung working directory: table border=0 width=100% bgcolor=#eeffee? cell?

 cd unslung

tableend?

Build the toolchain, which includes the crosscompiler and other tools. This will take quite a while and will download a large amount of data, but is only required once. table border=0 width=100% bgcolor=#eeffee? cell?

 make toolchain

tableend?

Deleted line 25:
 cd unslung
Changed line 32 from:
 scp builds/puppy_1.2-1_armeb.ipk root@slug:puppy_1.2-1_armeb.ipk
to:
 scp builds/puppy_1.6-1_armeb.ipk root@slug:puppy_1.6-1_armeb.ipk
Changed line 38 from:
 ipkg install puppy_1.2-1_armeb.ipk
to:
 ipkg install puppy_1.6-1_armeb.ipk
December 19, 2004, at 09:54 AM by peteru --
Changed line 23 from:
 scp builds/puppy_1.0-1_armeb.ipk root@slug:puppy_1.0-1_armeb.ipk
to:
 scp builds/puppy_1.2-1_armeb.ipk root@slug:puppy_1.2-1_armeb.ipk
Changed line 29 from:
 ipkg install puppy_1.0-1_armeb.ipk
to:
 ipkg install puppy_1.2-1_armeb.ipk
December 11, 2004, at 06:22 AM by peteru --
Changed lines 1-30 from:

Describe BuildingPuppy here.

to:

Building puppy is easy.

First you need to have a working unslung development environment. Follow instructions at HowTo.CompileCrossTool to build a cross compiler environment.

After you have the crosstool environment, add /opt/crosstool/armv5b-softfloat-linux/gcc-3.3.4-glibc-2.2.5/bin to your PATH

Retrieve the unslung sources from CVS: table border=0 width=100% bgcolor=#eeffee? cell?

 cvs -z3 -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/nslu co unslung

tableend?

All that remains, is to build puppy: table border=0 width=100% bgcolor=#eeffee? cell?

 cd unslung
 make puppy-ipk

tableend?

You can then copy the resulting puppy package to your slug: table border=0 width=100% bgcolor=#eeffee? cell?

 scp builds/puppy_1.0-1_armeb.ipk root@slug:puppy_1.0-1_armeb.ipk

tableend?

and install it: table border=0 width=100% bgcolor=#eeffee? cell?

 ipkg install puppy_1.0-1_armeb.ipk

tableend?

view · edit · print · history · Last edited by v12mike.
Based on work by v12mike and peteru.
Originally by peteru.
Page last modified on January 30, 2007, at 06:01 AM