All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Schuster <theBohemian@gmx.net>
To: openembedded-devel@lists.openembedded.org
Subject: outstanding avr32 issues (and their workarounds)
Date: Tue, 12 Aug 2008 09:35:23 +0200	[thread overview]
Message-ID: <48A13D3B.6040302@gmx.net> (raw)

[-- Attachment #1: Type: text/plain, Size: 2253 bytes --]

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.

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.

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

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

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.

--

Update! Although I needed evil dirty workaround the image is fine and boots:

The Angstrom Distribution atngw100 ttyS0



Angstrom 2008.1-test-20080810 atngw100 ttyS0



atngw100 login: root

root@atngw100:~# uname -a

Linux atngw100 2.6.24.3.atmel.3 #1 Tue Aug 12 09:11:56 CEST 2008 avr32
unknown

--

I hope that we can fix all the issues so people can build images for the
AVR32 systems without trouble. In the meantime people can use the
information herein to get their builds succeed.

Regards
Robert


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 268 bytes --]

             reply	other threads:[~2008-08-12  7:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-12  7:35 Robert Schuster [this message]
2008-08-12  7:44 ` outstanding avr32 issues (and their workarounds) Robert Schuster
2008-08-12  7:58 ` Robert Schuster
2008-08-13 11:14 ` Koen Kooi

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=48A13D3B.6040302@gmx.net \
    --to=thebohemian@gmx.net \
    --cc=openembedded-devel@lists.openembedded.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.