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 1/1] Fix elf2flt build
Date: Thu, 27 Aug 2015 20:35:01 +0200	[thread overview]
Message-ID: <20150827203501.00528bd2@free-electrons.com> (raw)
In-Reply-To: <1440694037-9022-1-git-send-email-public.douglas.raillard@gmail.com>

Douglas,

On Thu, 27 Aug 2015 18:47:17 +0200, Douglas RAILLARD wrote:
> Add -ldl to fix elf2flt build, because libbfd
> uses dlopen and friends for plugin loading
> 
> Signed-off-by: Douglas RAILLARD <public.douglas.raillard@gmail.com>

Thanks for this patch. Great to see that there is some interest in
noMMU architecture. Which architecture are you working on?

I'm not able to reproduce the problem: here host-elf2flt builds fine.
However the build of an ARM Cortex-M3 toolchain fails during the uClibc
build (which takes place *after* host-elf2flt is built).

Thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  reply	other threads:[~2015-08-27 18:35 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-27 16:47 [Buildroot] [PATCH 1/1] Fix elf2flt build Douglas RAILLARD
2015-08-27 18:35 ` Thomas Petazzoni [this message]
2015-08-27 21:00   ` Douglas RAILLARD
     [not found]   ` <6966330.pLhB8QsgjT@raillard-dv6>
2015-08-28  8:09     ` Thomas Petazzoni
2015-08-28 10:17       ` Douglas RAILLARD
2015-08-28 11:20         ` Thomas Petazzoni
2015-08-28 13:01           ` Waldemar Brodkorb
2015-08-30 15:43             ` Douglas RAILLARD
2015-08-31  6:05               ` Waldemar Brodkorb
2015-08-31 12:08                 ` Douglas RAILLARD
2015-08-31 12:28                   ` Thomas Petazzoni

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=20150827203501.00528bd2@free-electrons.com \
    --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.