DIY - KeK

[knc1]

Aboriginal Linux is just the development environment.

Go here:
www.linuxmint.com/download.php/

Browse around a bit.

The download comes as a "Live CD" - you can burn it to plastic and run it before committing to writing it onto your machine.

Clicking the "user manual" will tell you how to do the above.

[twobob]

I am reading - and reading - and reading : ) I'll grab me a copy of that now. then more reading

Read the filters info again. Hoping that one will make more sense when I come to need it.
The principle is very cool, well about 30 mins and I'll have a mint to install.

Are you a Mate or cinnamon man?
I went with Mate. It made me think of Sumo. or Judo. or something.

Hai!

[knc1]

This one is almost painless.

Build notes:

Spoiler:

The content of my pset.sh file:

export PATH=/opt/qemu111/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin

From the location of the AL install:

core2quad system-image-armv6l $ . pset.sh
core2quad system-image-armv6l $ ./dev-environment.sh
  * * * *
  Type exit when done.
(armv6l:1) /home # export PS1='(armv6l:1) \W \$ '
(armv6l:1) /home # export PATH=/home/bin:/bin:/sbin
(armv6l:1) /home # mkdir work/binutils
(armv6l:1) /home # cd work/binutils
(armv6l:1) binutils # wget http://drpbox.KnetConnect.com/KeK/binutils-2.22.tar.bz2
  Connecting to drpbox.KnetConnect.com (173.236.167.90:80)
(armv6l:1) binutils # mkdir bu-uclibc bu-glibc
(armv6l:1) binutils # mkdir /home/bu-222-uclibc /home/bu-222-glibc
(armv6l:1) binutils # cd bu-uclibc
(armv6l:1) bu-uclibc # CFLAGS='-mfloat-abi=softfp -mfpu=vfp -mcpu=arm1136jf-s \
 -O2 -fomit-frame-pointer' ../binutils-2.22/configure --prefix=/home \
 --disable-nls --disable-werror
(armv6l:1) bu-uclibc # make
(armv6l:1) bu-uclibc # make check
(Expect all tests to pass.)
(armv6l:1) bu-uclibc # make install
(This is how the tar-ball "release" gets made:)
(armv6l:1) bu-uclibc # DESTDIR=/home/bu-222-uclibc make install
(armv6l:1) bu-uclibc # cd /home/bu-222-uclibc/home
(armv6l:1) home # tar -cvzf ../binutils-2.22-uclibc.tar.gz .
(armv6l:1) home # cd
(armv6l:1) /home #

Installation:
Put tar-ball on /home (of the emulated environment) ;
tar -xf binutils-2.22-uclibc.tar.gz

Duh...
Going by the timestamps of the posts, it looks like our emulated armv6 running linux-3.4 got the job done in about an hour and a half.
Not bad.
Not good enough for me to try for a Kindle-OpenOffice though.

[twobob]

I was looking at http://www.creytiv.com/baresip.html again earlier today. That is a cool little box of tricks ey. I'll go and have a revisit of that in the not too distant. Thanks for the pointer.

[knc1]

Originally Posted by twobob

I was looking at http://www.creytiv.com/baresip.html again earlier today. That is a cool little box of tricks ey. I'll go and have a revisit of that in the not too distant. Thanks for the pointer.

Let me know when ready to test VoIP - I can fire up a copy of OpenVBX on KnetConnect.com
(That is one of the reasons for using that domain name.)

[knc1]

Our emulated development environment now has these suppliments:

(armv6l:1) /home # ls bin
addr2line  bin2c      gprof      m4         objdump    size       strip
ar         c++filt    ld         nm         ranlib     strace     tcc
as         elfedit    ld.bfd     objcopy    readelf    strings    xz

That should take care of the "not recent enough ld and as" messages ...

Last time (a few days ago) that I tried to build a newer compiler, I ran into:
gcc requires mpfr ;
mpfr requires gmp ;
gmp requires m4, but no m4 was on the system.

That speed bump was taken care of a few posts ago, now the most recent m4 is there.

The visibility on this road is a bit poor. Is there another speed bump around the next curve?

[knc1]

This is one of the libraries that the gcc build system **could** build during the process of building the compiler.

But if your going to build more than one compiler, one time, its better just to build and install a copy.

http://gmplib.org/
ftp://ftp.gmplib.org/pub/gmp-5.0.5/gmp-5.0.5.tar.bz2

Let the fun begin:

Spoiler:

The content of my pset.sh file:

export PATH=/opt/qemu111/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin

From the location of the AL install:

core2quad system-image-armv6l $ . pset.sh
core2quad system-image-armv6l $ ./dev-environment.sh
  * * * *
  Type exit when done.
(armv6l:1) /home # export PS1='(armv6l:1) \W \$ '
(armv6l:1) /home # export PATH=/home/bin:/bin:/sbin
(armv6l:1) /home # mkdir work/gcc ; cd work/gcc
(armv6l:1) gcc # wget http://drpbox.knetconnect.com/KeK/gcc-linaro-arm-linux-gnueabihf-2012.06-20120625_src.tar.bz2 
  Connecting to drpbox.knetconnect.com (173.236.167.90:80)
(armv6l:1) gcc # tar -xf gcc-linaro-arm-linux-gnueabihf-2012.06-20120625_src.tar.bz2
(armv6l:1) gcc # mv gcc-linaro-arm-linux-gnueabihf-2012.06-20120625_src lgcc4.7

Note:
# http://gmplib.org/
# ftp://ftp.gnu.org/gnu/gmp/gmp-5.0.5.tar.xz
(armv6l:1) lgcc4.7 # cd ..
(armv6l:1) gcc # mkdir gmp
(armv6l:1) gcc # cd gmp
(armv6l:1) gmp # wget http://drpbox.knetconnect.com/KeK/gmp-5.0.5.tar.xz
  Connecting to drpbox.knetconnect.com (173.236.167.90:80)
(armv6l:1) gmp # xz -d gmp-5.0.5.tar.xz
(armv6l:1) gmp # tar -xf gmp-5.0.5.tar
(armv6l:1) gmp # cd gmp-5.0.5
(armv6l:1) gmp-5.0.5 # export M4=/home/bin/m4
(armv6l:1) gmp-5.0.5 # export CFLAGS='-mfloat-abi=softfp -mfpu=vfp -mcpu=arm1136jf-s -O2 -fomit-frame-pointer -fexceptions'
(armv6l:1) gmp-5.0.5 # CXXFLAGS=$CFLAGS ; export CXXFLAGS
(armv6l:1) gmp-5.0.5 # mkdir ../gmp-sf-uclibc
(armv6l:1) gmp-5.0.5 # cd ../gmp-sf-uclibc
(armv6l:1) gmp-sf-uclibc # ../gmp-5.0.5/configure --prefix=/home --with-gnu-ld --enable-cxx
(armv6l:1) gmp-sf-uclibc # make
(armv6l:1) gmp-sf-uclibc # make check
(Expect all tests to pass.)

(armv6l:1) gmp-sf-uclibc # make install

(And our release tab-ball:)
(armv6l:1) gmp-sf-uclibc # mkdir /home/gmp505-uclibc
(armv6l:1) gmp-sf-uclibc # DESTDIR=/home/gmp505-uclibc make install
(armv6l:1) gmp-sf-uclibc # cd /home/gmp505-uclibc/home
(armv6l:1) home # tar -cvzf ../gmp-5.0.5-uclibc.tar.gz .

(the following properly closes the r/w hdb.img file system:)
(armv6l:1) home # cd /root
(armv6l:1) /root # umount /home
(armv6l:1) /root # exit
Restarting system.

This is another one that you "just dump" on top of /home.

Grumble: Three days later another application's configure told me I left the C++ interface out of the first gmp configuration.
That is simply not going to happen with the uClibc++ library in the emulator.

So this one is the "--without-cxx" library (again):

[knc1]

This is another of the math libraries that the gcc build system **could** build for you. Each and every time gcc was built.

http://www.mpfr.org/
http://www.mpfr.org/mpfr-current/mpfr-3.1.1.tar.xz

Once again, going to just install a copy ...

Spoiler:

The content of my pset.sh file:

export PATH=/opt/qemu111/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin

From the location of the AL install:

core2quad system-image-armv6l $ . pset.sh
core2quad system-image-armv6l $ ./dev-environment.sh
  * * * *
  Type exit when done.
(armv6l:1) /home # export PS1='(armv6l:1) \W \$ '
(armv6l:1) /home # export PATH=/home/bin:/bin:/sbin
(armv6l:1) /home # cd work/gcc
(armv6l:1) gcc # mkdir mpfr ; cd mpfr
(armv6l:1) mpfr # wget http://drpbox.knetconnect.com/KeK/mpfr-3.1.1.tar.xz
  Connecting to drpbox.knetconnect.com (173.236.167.90:80)
(armv6l:1) mpfr # xz -d mpfr-3.1.1.tar.xz
(armv6l:1) mpfr # tar -xf mpfr-3.1.1.tar
(armv6l:1) mpfr # mkdir mpfr-sf-uclibc mpfr311-sf-uclibc
(armv6l:1) mpfr # cd mpfr-3.1.1
(armv6l:1) mpfr-3.1.1 # export CFLAGS='-mfloat-abi=softfp -mfpu=vfp -mcpu=arm1136jf-s -O2 -fomit-frame-pointer'
(armv6l:1) mpfr-3.1.1 # export C_INCLUDE_PATH='/home/include'
(armv6l:1) mpfr-3.1.1 # export LIBRARY_PATH='/home/lib'
(armv6l:1) mpfr-3.1.1 # export LD_LIBRARY_PATH=$LIBRARY_PATH
(armv6l:1) mpfr-3.1.1 # cd /home/work/gcc/gmp/gmp-sf-uclibc/tune
(armv6l:1) tune # make speed
(armv6l:1) tune # cd /home/work/gcc/mpfr/mpfr-sf-uclibc

(This one ignores DESTDIR= && --enable-decimal-float needs newer compiler)
(armv6l:1) mpfr-sf-uclibc # ../mpfr-3.1.1/configure --with-gnu-ld --prefix=/home/work/gcc/mpfr/mpfr311-sf-uclibc --with-gmp-build=/home/work/gcc/gmp/gmp-sf-uclibc

(This one turns out to be non-fatal:)
checking format of `long double' floating point... IEEE double, little endian
configure: WARNING: oops, unrecognised float format: IEEE double, little endian

(armv6l:1) mpfr-sf-uclibc # make
(armv6l:1) mpfr-sf-uclibc # make check

  ====================
  All 160 tests passed
  (1 test was not run)
  ====================

(armv6l:1) mpfr-sf-uclibc # make install
(armv6l:1) mpfr-sf-uclibc # cd /home/work/gcc/mpfr/mpfr311-sf-uclibc
(armv6l:1) mpfr311-sf-uclibc # tar -czvf ../mpfr-3.1.1-uclibc.tar.gz .
(armv6l:1) mpfr311-sf-uclibc # cd /home

(Now "install" our own distribution tar-ball.)
(armv6l:1) /home # tar -xvf work/gcc/mpfr/mpfr-3.1.1-uclibc.tar.gz

(To ensure the hdb.img file system gets fully written and closed:)
(armv6l:1) /home # cd /root
(armv6l:1) /root # umount /home
(armv6l:1) /root # exit
Restarting system.
core2quad system-image-armv6l $

This is another one that you just dump onto the /home directory of the emulator.

Note inside of the spoiler the things that need to be set which are not indexed by the ld.so.conf cache.
We can't update the cache in the emulator because that is part of the ro filesystem.
So setting those variables was the way to get mpfr to find and use the new gmp libraries.

[knc1]

This is another one that the gcc build system **could** build for you.
Again, going to just install a copy of the current release for the compiler building to come.

http://www.multiprecision.org/index.php?prog=mpc
http://www.multiprecision.org/mpc/do...mpc-1.0.tar.gz

Ah, that one went relatively smoothly:

Spoiler:

The content of my pset.sh file:

export PATH=/opt/qemu111/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin

From the location of the AL install:

core2quad system-image-armv6l $ . pset.sh
core2quad system-image-armv6l $ ./dev-environment.sh
  * * * *
  Type exit when done.
(armv6l:1) /home # export PS1='(armv6l:1) \W \$ '
(armv6l:1) /home # export PATH=/home/bin:/bin:/sbin
(armv6l:1) /home # cd work/gcc
(armv6l:1) gcc # mkdir -p mpc/mpc-1.0-uclibc mpc/mpc10-uclibc
(armv6l:1) gcc # cd mpc
(armv6l:1) mpc # wget http://drpbox.knetconnect.com/KeK/mpc-1.0.tar.gz
  Connecting to drpbox.knetconnect.com (173.236.167.90:80)
(armv6l:1) mpc # tar -xf mpc-1.0.tar.gz
(armv6l:1) mpc # cd mpc-1.0
(armv6l:1) mpc-1.0 # export CFLAGS='-mfloat-abi=softfp -mfpu=vfp -mcpu=arm1136jf-s -O2 -fomit-frame-pointer'
(armv6l:1) mpc-1.0 # export C_INCLUDE_PATH='/home/include'
(armv6l:1) mpc-1.0 # export LIBRARY_PATH='/home/lib'
(armv6l:1) mpc-1.0 # export LD_LIBRARY_PATH=$LIBRARY_PATH
(armv6l:1) mpc-1.0 # export LDFLAGS=-L/home/lib
(armv6l:1) mpc-1.0 # export CPPFLAGS='-I/home/include -mfloat-abi=softfp -mfpu=vfp -mcpu=arm1136jf-s -O2 -fomit-frame-pointer'
(armv6l:1) mpc-1.0 # export DESTDIR=/home/work/gcc/mpc/mpc-uclibc
(armv6l:1) mpc-1.0 # cd ../mpc-1.0-uclibc
(armv6l:1) mpc-1.0-uclibc # ../mpc-1.0/configure --prefix=/home --with-gnu-ld
(armv6l:1) mpc-1.0-uclibc # make
(armv6l:1) mpc-1.0-uclibc # make check
  * * * *
  GMP: include 5.0.5, lib 5.0.5
  MPFR: include 3.1.1, lib 3.1.1
  MPC: include 1.0, lib 1.0
  C compiler: gcc
  GCC: yes
  GCC version: 4.2.1
  PASS: tget_version
  ===================
  All 64 tests passed
  ===================

(armv6l:1) mpc-1.0-uclibc # make install
(armv6l:1) mpc-1.0-uclibc # cd $DESTDIR/home
(armv6l:1) home # pwd
  /home/work/gcc/mpc/mpc-uclibc/home
(Whoot!  That worked, even with the libtoolized build!)

(Our release tar-ball:)
(armv6l:1) home # tar -cvzf ../mpc-1.0-uclibc.tar.gz .

(Install it for ourselves:)
(armv6l:1) home # cd ..
(armv6l:1) mpc-uclibc # tar -xf mpc-1.0-uclibc.tar.gz -C /home

(Ease on out of the emulator:)
(armv6l:1) mpc-uclibc # cd /root
(armv6l:1) /root # umount /home
(armv6l:1) /root # exit
Restarting system.
core2quad system-image-armv6l $

And the only things lost along the way so far was 'long double' and 'decimal float'.

This is another one that you install by 'dumping' it on the emulator's /home directory.

[knc1]

http://www.kotnet.org/~skimo/isl/user.html
ftp://gcc.gnu.org/pub/gcc/infrastruc...l-0.10.tar.bz2

This one will not be a part of the first round of emulator updates.

[knc1]

(A.K.A: Cloog-ppl)

http://www.bastoul.net/cloog/download.php
http://www.bastoul.net/cloog/pages/d...-0.16.1.tar.gz

This will not be part of the first round of the updating the emulator.

[twobob]

*Rubs Hands Gleefully from shiny new 32 bit-PITA-to-build-but-now-it´s-done system *

Okey dokey time to get me some kek action for this baby.

Thanks muchly for this excellent resource, it truly is an outstanding effort.

*runs off like happy teenager*

Notes on building a 32 mint system:

It´s simple, go get the ISO, burn it, shove the biscuit in the DVD drive, ¨boot from DVD¨ via bios, When it´s booted click the install icon and follow the very simple instructions.


Side Note: In my case I had a defective drive so I ended up chasing weird boot errors for a couple of days till I just switched out devices until I found one that was happy - I highly doubt anyone else will have this experience.

I also could not get my bios to boot from USB stick using the custom bootloaders (that was using cinnamon or mate MINT 13, Starting with the release of Linux Mint 12 KDE RC, Linux Mint switched to Hybrid ISO images. I could have gone KDE but that wasn´t much of a change from my previous slackware install defaults, this route was not for me, thought I would indicate the option though)


I have installed Mint Cinnamon for now and Mate on another machine, probably going to switch over to another window manager in the medium term. If there are any details that are worth noting I´ll pop them on this thread but so far it´s been a HIGHLY painless experience to use. (Other than the silly hw fail)

Thanks for the tip!

[knc1]

http://bugseng.com/products/ppl/download
http://bugseng.com/products/ppl/down...ppl-1.0.tar.xz

This one will not be part of the first round of emulator updates.

[twobob]

So. I know I´m a bit slow, but did we say that buildroot did NOT support the processor type? I´m just checking.

Working my way back through this thread bit by bit now.

Good stuff in here

[knc1]

Originally Posted by twobob

So. I know I´m a bit slow, but did we say that buildroot did NOT support the processor type? I´m just checking.

Working my way back through this thread bit by bit now.

Good stuff in here

I saw more updates go in for the i.MX2* series this past week but haven't seen any for the i.MX3* or i.MX5* series of freescale chips.

Disclaimer: I may have missed the updates, I don't always read every Buildroot commit message.

- - - -

Buildroot (and the like) are systems that use cross-compilation.

The KeK project is focused on providing an emulated native compilation environment.

Out of the box (actually, out of Rob's ./build.sh script) the emulated native environment (Aboriginal Linux) works, provided:
Your code can be compiled with a gcc-4.2 tool-chain.

For native (compiled) code applications that run on the Kindle(s) the out-of-the-box emulated native environment can only produce "statically linked" Kindle executables.

This long thread is my complaining and moaning about the problems of updating that environment to be based on a current tool-chain.

At the moment, the project status is:
End-user downloads and un-archives:

• Either the 32bit or 64bit qemu-1.1.1 that is posted in this thread;
• The system-image-armv6l A.L. image;
• Opens a terminal and in the directory created by un-archiving the A.L. image types: ./dev-environment.sh

That's it. Three steps. Each of the posts in this thread are worked examples of building ARM software in that emulated environment, for execution in the same emulated environment.

The "work-in-progress" (what GM likes to call: Vaporware);
New "system-image-armv6" (no "l") images in three flavors:

• system-uclibc-armv6 :: The current image with newer tool-chain.
• system-glibc-armv6 :: The newer tool-chain for the glibc based Kindle native applications.
• system-eglibc-armv6 :: The newer tool-chain for the eglibc based Kindle native applications.

For the ARMv7 Kindles, (K4, K5) with the newer VFPv3 co-processor :
That is a single item edit in the ./run-environment.sh script (now or later).
But if the end-user's code doesn't need the better floating point vector processor - then all Kindles can run the ARMv6 code.


When completed, this will add one more step to the first 3 step process:

"pick the correct one of the three directories before typing: ./dev-environment.sh"


This is the simplest DIY-KeK environment I can think of for the person with just one or a few small native code Kindle applications to compile.

• Download and un-pack two archives
• Make one decision (which directory of the three)
• Type one shell script command.

PS: Not (yet) Kindle specfic - all of the above can be used to develop for the Raspberry Pi.

PPS: For the reader that just stumbled into this thread, see:
https://wiki.mobileread.com/wiki/Tools_Index#Development