Buildroot a linux 2.6.26-lab126 kernal. (3.3)

[twobob]

Replies and Moans about "I do what with the headers? Bah :\"

Spoiler:

@knc1 exactly what you said. Oh and I spent ALL DAY looking for the post where you told me how to link recursively the arm-blah-gedoofer-gcc to gcc.

Still never found the damn thing. SO. Instead I'm doing including aalib the "proper" way. The universe was clearly telling me something.

@geekmaster. Err, okay. Sorry I thought you meant that there was some task to be undertaken. Yes reading code around a general procedural workflow is always helpful. thanks.

@Niluje okay mate. In that case I am 100% confident I am correct.
To clone or to amend is a details. amend = easiest so I may go there.

I have studied the man diff and patch till the cows come home and still am foggy about how it references paths but no doubt "readthrough 'n'" may actually sink it in to me. I have custom versions of your patch now that do the job. just need to get them applied relatively. I'll work it out. your help has been incredibly beneficial.

NOTES ON USING THE AMAZON KERNEL HEADERS:

a) Use Nilujes Patch to fix the unifdef issue - Find from top post.
(extract just that hunk or just "don't apply this patch" fail the Makefile bit)
https://svn.ak-team.com/svn/Configs/...buildfix.patch

apply it the in root of your extracted amazon kernel source folder

you@dev /usr/local/src/BUILD_KERNAL $ patch -p1 <kernel-headers.patch
(if it fails to find the file just give it the absolute path to unifdef.c - it's in scripts)

Ensure you have an X-compiler that is configured in the the way outlined here:
https://www.mobileread.com/forums/sho...&postcount=271

Then ensure your X-compiler is in your path:

you@dev /usr/local/src/BUILD_KERNAL/linux-2.6.26 $ echo $PATH
/opt/qemu111/bin:/home/you/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games

Then run:
you@dev /usr/local/src/BUILD_KERNAL/linux-2.6.26 $ DESTDIR=/opt/arm-2012.03 sudo make headers_install ARCH=arm INSTALL_HDR_PATH=/opt/arm-2012.03

where that is the path to your TC.

Bish Bash Bosh.

Thanks Niluje. Superstar.

Okay so to the thrust of this post:

Adding new packages 101 - Customising BR. (It's easy, honest).

the main docs are here:
http://buildroot.uclibc.org/download...s_to_buildroot

This reallife guide is what I intend to take the project where knc1 wanted.

The guide:

We assume that you have some knowledge.

${foo} is a reference to a variable.

you would test conditions like
if(${foo})
blar
endif

read up on Makefile and configure files. that will help.

Including AALIB in BR...

mkdir /home/you/GIT/buildroot/package/aalib

cd /home/you/GIT/buildroot/package/aalib

nano -w aalib.mk

Spoiler:

PHP Code:

#############################################################
#
# aalib
#
#############################################################
AALIB_VERSION = 1.4rc4
AALIB_SOURCE = aalib-$(AALIB_VERSION).tar.gz
AALIB_SITE = http://prdownloads.sourceforge.net/aa-project
AALIB_INSTALL_STAGING = YES
AALIB_INSTALL_TARGET = YES

AALIB_DEPENDENCIES = host-pkg-config
AALIB_MAKE = $(MAKE1)
AALIB_AUTORECONF = YES

AALIB_CONF_OPT = --enable-shared --with-x11-driver=no --exec-prefix=/mnt/us --prefix=/mnt/us 

ifeq ($(BR2_PACKAGE_SLANG),y)
AALIB_CONF_OPT+=--with-slang-driver=yes
AALIB_DEPENDENCIES += slang
else
AALIB_CONF_OPT+=--with-slang-driver=no
endif

ifeq ($(BR2_PACKAGE_CURSES),y)
AALIB_CONF_OPT+=--with-curses-driver=yes
AALIB_DEPENDENCIES += curses
else
AALIB_CONF_OPT+=--with-slang-driver=no
endif

$(eval $(autotools-package)) 


save it


nano -w Config.in

Spoiler:

PHP Code:

config BR2_PACKAGE_AALIB
    bool "aalib"
    help
      AAlib is an portable ascii art GFX library. If you wish to see some examples of AAlib technology, please browse AA-project homepage.
      
      http://aa-project.sourceforge.net/index.html 


save it.



In this next section you can choose to include it in the packages directories.
I choose LIBRARIES: GRAPHICS because I think that is the best fit.

nano /home/you/GIT/buildroot/package/Config.in

add source "package/aalib/Config.in" in the relevant section
(see pictures for my example)


Adding Support in existing BR applications:

In this next section we are optionally adding support for the new package in existing packages like so: (adding support in SDL)

nano /home/you/GIT/buildroot/package/sdl/Config.in

Spoiler:

PHP Code:

config BR2_PACKAGE_SDL
    bool "SDL"
    help
      Simple DirectMedia Layer - SDL is a library that allows
      programs portable low level access to a video framebuffer,
      audio output, mouse, and keyboard.

      http://www.libsdl.org/

if BR2_PACKAGE_SDL

config BR2_PACKAGE_SDL_FBCON
    bool "SDL framebuffer console video driver"
    default y

config BR2_PACKAGE_SDL_DIRECTFB
    bool "SDL DirectFB video driver"
    depends on BR2_PACKAGE_DIRECTFB

config BR2_PACKAGE_SDL_QTOPIA
    bool "SDL Qtopia video driver"
    depends on BR2_PACKAGE_QT

config BR2_PACKAGE_SDL_AALIB
    bool "SDL aalib ascii driver"
    depends on BR2_PACKAGE_AALIB

config BR2_PACKAGE_SDL_X11
    bool "SDL X11 video driver"
    depends on BR2_PACKAGE_XORG7
    select BR2_PACKAGE_XLIB_LIBX11
    select BR2_PACKAGE_XLIB_LIBXEXT

endif 


save it.

Edit the mk to include the call.

Run make xconfig from BuildRoot Root.

You should see the new things as pictured below.

The example I posted here also includes the use of making another application require support which is the start of integration.

HTH.

[twobob]

so I go the kernel source. and make kernel-headers

http://kernel.org/doc/Documentation/...rs_install.txt

then I point them at the right place

make headers_install ARCH=i386 INSTALL_HDR_PATH=/usr/include

so I just point that at the TC include folder? ( I think yes) answers on a postcard.

You ever get the feeling you've read every page of a manual but the relevant one?
: )

For my reference http://www.mobileread.mobi/forums/sh...=170213&page=3

[twobob]

19:55 Began rebuilding all packages for time test.
Including new aalib and SDL support for it.

This build will encompass all packages as outlined in the 2nd to top post of this thread.

EDIT: well I'm not sure the total count of stuff built but its in the high 300's.

Time to completion: 21:25. Wow. not bad. 90 minutes to compile everything.

I love you buildroot.

[knc1]

Pardon me if I mention the obvious, no insult intended, but in case you missed it:
In the top level directory of the Buildroot tree, enter:
make manual

**Then** you will have something to read that is supposed to match the version your using.

[twobob]

nothing is obvious. Obviously Also placing these things online saves the next poor fool from asking. I have no problem being the ask-the-stupid-question or get-the-sensible-answer guy. Someone has to do it.

Fortunately my lack of shame serves me well in this regard.

Hope you doing good on this fine sunny day. Well actually it was miserable and cold but meh in my mind it is sunshine...

Well the build is into hour 2 (over 1 hour that is) and going strong. Time for some tea I think

[twobob]

EDIT:

Instead of that spaomla meanderson gripe heres some raw data.

YUM

How to pull the right library 101.

Let's have a list of everything

if you were wondering what Enviroment settings there are by default. This would be they.
With a little bit of extras ie. the fix for

"relocation error: ../lib/libc-2.3.6.so: symbol _dl_out_of_memory, version GLIBC_PRIVATE not defined in file ld-linux.so.3 with link time reference"

Many thanks goes to bmoore and his Stupid_LD_Tricks for the ideas.

export DISPLAY=':0.0'
export EDITOR='/bin/vi'
export HISTFILESIZE='1000'
export HISTSIZE='1000'
export HOME='/tmp/root'
export HOSTNAME='kindle'
export INPUTRC='/etc/inputrc'
export LANG='en_US.UTF-8'
export LC_ALL='en_US.UTF-8'
export LD_LIBRARY_PATH='/lib:/usr/lib:/mnt/us/lib:/mnt/us/usr/lib'
export LD_PRELOAD='/lib/libc-2.5.so'
export LOGNAME='root'
export MAIL='/var/mail/root'
export OLDPWD='/mnt/us/bin'
export PAGER='/bin/more '
export PATH='/usr/local/bin:/bin:/usr/bin:/usr/sbin:/sbin:/mnt/us/bin:/mnt/us/usr/bin'
export PS1='[\u@\h \W]\$ '
export PWD='/mnt/us'
export SHELL='/bin/sh'
export SSH_CLIENT='192.168.1.99 9999 22'
export SSH_CONNECTION='192.168.1.99 9999 192.168.1.99 22'
export SSH_TTY='/dev/pts/4'
export TERM='xterm'
export USER='root'

Well that's eminently scriptable and should get us enough traction to make aalib work.

*SHOULD* TBC : )

[knc1]

Originally Posted by twobob

Well the build is into hour 2 (over 1 hour that is) and going strong. Time for some tea I think

Buildroot is not that fast.
Grab your ax, go clubbing, check it tomorrow.

[twobob]

took 90 mins to do everything I managed to include so far.

1.3 Gb of software. I now have aalib working
aafire test works

This is a big step forward.

That's a custom inclusion in buildroot. custom Config.in with a new fully customized skeleton for the kindle - targetting the correct structure now.

I also had a look how hard it might be to whip up a CATCH-ALL fixer-upper script to apply to existing and new Configure.in s automatically. Also to locally cascade the new optional dependencies satisfied by aalib, a few things support it IIRC.

It's a toughie with handballed files in the mix to do this all on-auto but I'm thinking on it. This IS something I am good at (Thank my lucky stars had to happen eventually)

On the kindle side I now can hack the right libs to start, more or less, at whim. without too much 'ld' gripes and no updating the core config.

People may well already know all about LD_PRELOAD and LD_LIBRARY_PATH and friends. for my part this is helpful info. Since stuff now works. In a large way. from FAT. Without linking. who knew.

(thanks you NiLuje for the pointers, and HIDI for a working example)

prboom is just a step away... Lots of fun being had here. Happy to share.

[twobob]

ah why not a few more shots. : )

aatest in action.

looks like i need to configure the fonts... ah yes /mnt/us/etc... how handy

[twobob]

Originally Posted by knc1

Pardon me if I mention the obvious, no insult intended, but in case you missed it:
In the top level directory of the Buildroot tree, enter:
make manual

**Then** you will have something to read that is supposed to match the version your using.

you@dev ~/BLDS/buildroot $ make manual
make -C /home/you/GIT/buildroot O=/home/you/BLDS/buildroot/. manual
Generating HTML manual...
make[1]: a2x: Command not found
make[1]: *** [/home/you/BLDS/buildroot/./docs/manual/manual.html] Error 127
make: *** [all] Error 2

I'll add it to the deathlist


EDIT OR NOT:

add asciidoc to the build-depends to fix this bug

hmm. Let me just grab that

you@dev ~/BLDS/buildroot $ sudo apt-get install asciidoc


0 upgraded, 52 newly installed, 0 to remove and 1 not upgraded.
Need to get 450 MB of archives.

Whoa. hardcore. Oh well. Time for some tea.

[knc1]

Translation: Abandon yee all ideas of running asciidoc on the Kindle.

[twobob]

Originally Posted by knc1

Translation: Abandon yee all ideas of running asciidoc on the Kindle.

HEHEHHE - FOR SURE. Even I'm not that insane.

Okay its installed!!

you@dev ~/BLDS/buildroot $ make manual

make -C /home/you/GIT/buildroot O=/home/you/BLDS/buildroot/. manual
Generating HTML manual...
Generating Split HTML manual...
Generating PDF manual...
Generating Text manual...
a2x: ERROR: w3m -cols 70 -dump -T text/html -no-graph /home/you/BLDS/buildroot/docs/manual/manual.text.html > /home/you/BLDS/buildroot/docs/manual/manual.text returned non-zero exit status 127
make[1]: *** [/home/you/BLDS/buildroot/./docs/manual/manual.text] Error 1
make: *** [all] Error 2

bah.

Honestly.

More tea.

you@dev ~/BLDS/buildroot $ sudo apt-get install w3m

[sudo] password for you: 
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following extra packages will be installed:
  libgc1c2
Suggested packages:
  w3m-img w3m-el migemo
The following NEW packages will be installed
  libgc1c2 w3m
0 upgraded, 2 newly installed, 0 to remove and 1 not upgraded.
Need to get 1,182 kB of archives.
After this operation, 2,351 kB of additional disk space will be used.
Do you want to continue [Y/n]? y

Tea Tea Tea

you@dev ~/BLDS/buildroot $ make clean-manual
make -C /home/you/GIT/buildroot O=/home/you/BLDS/buildroot/. clean-manual
you@dev ~/BLDS/buildroot $ make manual
make -C /home/you/GIT/buildroot O=/home/you/BLDS/buildroot/. manual
Generating HTML manual...
Generating Split HTML manual...
Generating PDF manual...
Generating Text manual...
Generating EPUB manual...
you@dev ~/BLDS/buildroot $ yay ;)

Happy now

[knc1]

Interesting, it churned out an epub version.

I guess that is so you can display a page of directions on the Kindle while fighting with the build system on your larger machine.

Note to the casual reader:
The Buildroot release tar-balls come with the manual already built.

This work is being done with a clone of the Buildroot repository (which does not contain generated files).

[twobob]

Okay so I got my headers in order AFAICT. shoved my experiences in the moan thread - when I am certain I have it right I will stick it in it's own thread. It was annoying enough to warrant one IMHO : )

So quick rebuild of everything I think. another 90 mins I'll never get back hehehe

Okay. I updated Buildroot via GIT. and stashed my changes.

Forked off BR with a view to long-term shallow fork to Kindle when I get my head more around it. Pushed the fork to github. reapplied my SDL wangle and AALIB inclusion.

New go-round with right headers, latest BR updates, just started. See what that brings.

[twobob]

Originally Posted by NiLuJe

@twobob:

K2/3: ARCH_FLAGS="-march=armv6j -mtune=arm1136jf-s -mfpu=vfp"
K4/5: ARCH_FLAGS="-march=armv7-a -mtune=cortex-a8 -mfpu=neon" (or -mfpu=vfpv3, which might in fact be a better choice right now, even with the latest Linaro GCC series, I have some benchmarks to do...)

The rest might start an unholy war, but I'd go with at least:
-O2 -ffast-math ${ARCH_FLAGS} -pipe -fomit-frame-pointer (unless you care about debugging stuff, in which case you'll want to replace all this with -O0 -g3 ${ARCH_FLAGS} -pipe -fno-omit-frame-pointer). (FWIW, Linaro recommends using -O3 or -Ofast on armv7... Again, I have some benchmarks to do ).

Unless you know that -ffast-math is going to break something, which should be approximately never, except for some really, really specific use cases.

This post is of constant help to me.

Thanks Niluje.