All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 0/9] Fix internal blackfin toolchain
Date: Sat, 27 Jul 2013 16:23:35 +0200	[thread overview]
Message-ID: <20130727162335.0e5bf70c@skate> (raw)
In-Reply-To: <1374324735-2286-1-git-send-email-gustavo@zacarias.com.ar>

Dear Gustavo Zacarias,

On Sat, 20 Jul 2013 09:52:06 -0300, Gustavo Zacarias wrote:
> This patchset fixes the internal blackfin toolchain build.
> It's been broken for ages (never worked maybe?)
> Testers wanted, it builds what's supposed to build but i lack hardware
> to see if it really works.
> 
> Gustavo Zacarias (9):
>   gcc/bfin: doesn't support --with-cpu defaults
>   uclibc/bfin: only supports linuxthreads.old
>   uclibc: make target utils optional
>   gcc/bfin: 4.{6,7,8}.x are broken
>   uclibc: use builtin startfiles target
>   uclibc/bfin: set the appropiate binfmt in the configuration
>   uclibc/bfin: don't install host utils if not FDPIC
>   blackfin: set GNU_TARGET_NAME accordingly
>   gcc/mudflap: disable for blackfin, it doesn't build

Committed entire series, with the minor fixes I pointed on the
individual patches.

Note that when you select FLAT format, it is still ELF binaries that
are produced in $(O)/target. Most likely related to our non-working
handling of elf2flt, as discussed recently on the list regarding ARM
noMMU platforms. So this patch series certainly improves the situation,
but doesn't fix the whole thing yet :)

Thanks!

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

  parent reply	other threads:[~2013-07-27 14:23 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-20 12:52 [Buildroot] [PATCH 0/9] Fix internal blackfin toolchain Gustavo Zacarias
2013-07-20 12:52 ` [Buildroot] [PATCH 1/9] gcc/bfin: doesn't support --with-cpu defaults Gustavo Zacarias
2013-07-21 15:35   ` Thomas Petazzoni
2013-07-21 16:26     ` Gustavo Zacarias
2013-07-20 12:52 ` [Buildroot] [PATCH 2/9] uclibc/bfin: only supports linuxthreads.old Gustavo Zacarias
2013-07-20 12:58   ` Yann E. MORIN
2013-07-27 14:21   ` Thomas Petazzoni
2013-07-20 12:52 ` [Buildroot] [PATCH 3/9] uclibc: make target utils optional Gustavo Zacarias
2013-07-20 13:08   ` Yann E. MORIN
2013-07-20 12:52 ` [Buildroot] [PATCH 4/9] gcc/bfin: 4.{6,7,8}.x are broken Gustavo Zacarias
2013-07-20 12:52 ` [Buildroot] [PATCH 5/9] uclibc: use builtin startfiles target Gustavo Zacarias
2013-07-20 12:52 ` [Buildroot] [PATCH 6/9] uclibc/bfin: set the appropiate binfmt in the configuration Gustavo Zacarias
2013-07-20 12:52 ` [Buildroot] [PATCH 7/9] uclibc/bfin: don't install host utils if not FDPIC Gustavo Zacarias
2013-07-20 12:52 ` [Buildroot] [PATCH 8/9] blackfin: set GNU_TARGET_NAME accordingly Gustavo Zacarias
2013-07-21 15:38   ` Thomas Petazzoni
2013-07-21 16:32     ` Gustavo Zacarias
2013-07-27 14:22   ` Thomas Petazzoni
2013-07-20 12:52 ` [Buildroot] [PATCH 9/9] gcc/mudflap: disable for blackfin, it doesn't build Gustavo Zacarias
2013-07-27 14:23 ` Thomas Petazzoni [this message]
2013-07-27 14:35   ` [Buildroot] [PATCH 0/9] Fix internal blackfin toolchain Gustavo Zacarias

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=20130727162335.0e5bf70c@skate \
    --to=thomas.petazzoni@free-electrons.com \
    --cc=buildroot@busybox.net \
    /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.