public inbox for crossgcc@sourceware.org
 help / color / mirror / Atom feed
From: Martin Guy <martinwguy@gmail.com>
To: crossgcc@sourceware.org
Subject: [PATCH] Fixes for avr32 target
Date: Wed, 28 Dec 2011 22:50:00 -0000	[thread overview]
Message-ID: <CAL4-wQojmzQz+Cb2dVaQEOHqS7YF-H=B7f4myWTnx9pLYcCPRA@mail.gmail.com> (raw)

Hi again
   This patch fixes the broken avr32 target in crosstool-ng. Mostly
that had to do with replacing the dead custom tarball at
dev.doredevelopments.dk (which entire site has dissapeared!) and
downloading the avr32-headers from Atmel directly, and adding .zip
extractor logic to handle it.

I'm a bit confused by the sample configs, which seem to have some
pattern to them but don't reflect the default ct-ng menuconfig values,
so here's the procedure I used to configure it for avr32 after
launching ct-ng menuconfig in an empty directory:

        Paths and misc options ->
                Shell to use as CONFIG_SHELL = sh
        Target options ->
                Target Architecture = avr32
        Binary utilities ->
                binutils version = 2.18a
        C compiler
                gcc version = 4.2.2
        C-library
                newlib version = 1.17.0

CONFIG_SHELL is necessary to get round the "fragment: command not
found" bug when binutils-2.18 is configured using bash.

Apart from that, no other configs seem necessary. Yann, maybe you can
apply the above to whatever the template config is, in which case
martinwguy@gmail.com and martinwguy.co.uk are OK as reported-by
fields.

Cheers

    M

--
For unsubscribe information see http://sourceware.org/lists.html#faq

             reply	other threads:[~2011-12-28 22:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-28 22:50 Martin Guy [this message]
2011-12-29  0:16 ` Martin Guy
2011-12-31 18:17   ` Yann E. MORIN

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='CAL4-wQojmzQz+Cb2dVaQEOHqS7YF-H=B7f4myWTnx9pLYcCPRA@mail.gmail.com' \
    --to=martinwguy@gmail.com \
    --cc=crossgcc@sourceware.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).