[oe] outstanding avr32 issues (and their workarounds)

[Koen Kooi]

Robert Schuster wrote:
> Hi,
> for the last 4 days or so I am trying to build Angstrom 2008.1 (uclibc)
> for Atmel's NGW100 board featuering an AVR32 CPU.
>
> I have not been able to boot the image I built with OE yet but these are
> the issues I encountered so far:
>
> 1) binutils-cross 2.17
> Something is b0rken with the configure script code that puts the
> arguments to configure into a variable. The variable contains
> environment variables. This in turn causes the binutils build to fail
> afterwards. There is a workaround which does a little bit of sed magic
> on the generated Makefile. This fixes the wrong variable and lets the
> build succeed.

This should be 'solved' now

> 2) gcc-cross 4.2.2
> When the objective c language is enabled the build of gcc-cross will
> fail because the compiler crashes when compiling some objective c source
> file.
> I have not examined this in detail. Maybe this is fixable with a patch
> to gcc.

This should be 'solved' now as well (ugh, it overrides a variable and 
unweaking it in the process :()

> 3) util-linux-ng 2.14 (when building console-image)
> Needs UCLIBC_HAS_PROGRAM_INVOCATION_NAME=y in uclibc.distro.

Fixed

> 4) console-image
> When the rootfs is generated it will fail with:
>
> Collected errors:
>   * ERROR: Cannot satisfy the following dependencies for task-base-extended:
>     *  libgcc *
>
> There is no libgcc package because it is empty and OE normally does not
> create empty packages. Unfortunately I am not experienced enough with
> uclibc to say why there are no files for libgcc nor do I understand why
> some package requests it. I did a very dirty workaround by declaring
> ALLOW_EMPTY = "1" in gcc-cross.inc

Try a clean rebuild, Khems toolchain changes should have fixed this.

> and optional:
>
> 5) linux
> This is only important if you want to boot from SD/MCC like me. The
> defconfig should say that ext2 or 3 (or both) is built-in. Otherwise you
> cannot boot from such a filesystem.

I tried to update the stk1000 kernel a few weeks ago and ran into 
'funny' issues. If you build in the ps/2 module (the board has 3.3V ps/2 
connectors) the kernel fails to boot. If you enable keyboard drivers 
(HID) the kernel fails to boot. If you enable scsi (for usb storage) the 
kernel fails to boot. If you build in usb support (if have a cf-usb 
adaptor) the kernel fails to boot. I now have a defconfig that builds 
with the current kernel *and* manages to boot, but updating the avr32 
patch makes it unbootable again.
So changing the ngw defconfig is ok, but please test on a stk1000 before 
updating kernel sources.

regards,

Koen