I'm pulling this out of the former thread on NGW100/uboot because there were too many discussions going and I didn't want to clutter it up with questions and notes specific to SuSE 10.
This post includes some results from initial attempts to build the NGW image SuSE 10. Some solutions, some questions re: issues I hit along the way.
So, the results of my first trial build on my SuSE 10.1 using the build-linux-environment script was:
spanky:/home/ko/Documents/AVR32/scripts # ./build-linux-environment.sh ../software ../builds/ngw/ ../mybuilds U-boot - unpacking OK U-Boot - patching OK U-boot - config and make OK flash upgrade utility (u-boot upgrade) OK Creating new root for Basic OK uClibc - unpacking OK uClibc - patching OK uClibc - make oldconfig and make install OK Linux kernel - unpacking OK Linux kernel - patching OK Linux kernel - make oldconfig and make OK Busybox - unpacking OK Busybox - patching OK Busybox - make and make install OK strace - unpacking OK strace - patching OK strace - configure, make, install OK Zlib - unpacking OK Zlib - configure, make, copy library to root OK ncurses - unpack OK ncurses - patching OK ncurses - configure, make, make install OK ftpd - unpacking OK ftpd - patching OK ftpd - make and copy to target OK joe - unpacking OK joe - patching OK joe - configure, make, make install OK gdbserver - autoconf and configure OK gdbserver - make and make install OK dropbear - unpacking OK dropbear - patching OK dropbear - configure, make and make install OK ntp - unpacking tar: A lone zero block at 17300 OK ntp - patching OK ntp - configure, make and make install OK net-tools - unpacking OK net-tools - patching OK net-tools - configure, make and make install OK dnsmasq - unpacking OK dnsmasq - patching OK dnsmasq - configure, make and make install OK Creating /etc/release for Basic OK Creating runtime image for Basic FAILED e2fsimage program not found, skipping image creation.
I looked for e2fsimage via yast2, but it's not supplied.
e2fsimage isn't available directly from SuSE DVD/yast2.
Need to install e2fsimage 0.2.2 but it has dependency on e2fsprogs headers.
Solution is to install e2fsprog (e2fsprogs-devel to be precise) from yast2 or consult this link: http://support.novell.com/techce...
rpm -Fvh e2fsprogs.rpm
The home page for e2fsprogs is at:
After e2fsprogs is configured/installed with devel headers,
Then download e2fsimage-0.2.2 from http://sourceforge.net/projects/...
spanky:/tmp/e2fsimage-0.2.2 # ./configure /usr /usr/local Found: ext2fs/ext2fs.h at /usr/include Found: e2p/e2p.h at /usr/include Found: libext2fs.so at /usr/lib Found: libcom_err.so at /usr/lib The version of the e2fs library is: 1.38, 30-Jun-2005 LDFLAGS : -lext2fs -lcom_err PREFIX :/usr/local CPPFLAGS : CFLAGS :-Wall VERSION :0.2.2 GNU Make 3.80 GNU Make 3.80 A usable make executable was found in /usr/bin/make
Got much further into kernel build but then bombed on:
DirectFB - configure, make and make install OK
pong - make and make install FAILED
make failed, see make.out
make.out was complaining it couldn't find the DirectFB headers (package which got built right before pong.) In any case, when I looked at the ./build-linux-environment.sh script, this "pong" was coming from the STK1000 standard linux image build...it had already finished the Basic build used by both the STK1000 and the NGW.
So, my question is: is there any reason, if I'm working exclusively with the NGW100, that I need to be building anything for the STK1000 standard image? For the moment, I will comment out the build components for the STK1000.