Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Help adding a prerequisite to GCC
Date: Sat, 28 Jul 2012 09:37:29 +0200	[thread overview]
Message-ID: <20120728093729.45429122@skate> (raw)
In-Reply-To: <501315CB.2080809@sri.com>

Hello Scott,

Le Fri, 27 Jul 2012 15:27:23 -0700,
Scott Moore <scott.moore@sri.com> a ?crit :

> I'm trying to compile a toolchain with LTO support in gcc.
> I tried to do this by adding the additional gcc flag "--enable-lto", but 
> the build fails (unsurprisingly) because building gcc with lto support 
> requires libelf, which is not currently a prerequisite for gcc in buildroot.
> 
> To fix this, I tried adding libelf to gcc-uclibc-4.x.mk by adding:
> GCC_HOST_PREREQ += host-libelf
> GCC_TARGET_PREREQ += libelf

This sounds good.

> The resulting build fails because their is "no make target host-libelf, 
> required for gcc_initial". Can anyone help me figure out where I went 
> wrong? I realize just hacking it in to the .mk like that probably isn't 
> ideal. I was planning to add it as a menuconfig option once I get it 
> building at all.

If you look at package/libelf/libelf.mk, you'll see that there is only
a target variant of this package, and no host variant.

So you should add a line:

$(eval $(host-autotools-package))

at the bottom of the file, and try again. You may need to define some
addition HOST_* variables to adjust the configuration options and
others, if the build fails or if the resulting host libelf doesn't work
properly for what you're trying to do.

Hope this helps,

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

  reply	other threads:[~2012-07-28  7:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-27 22:27 [Buildroot] Help adding a prerequisite to GCC Scott Moore
2012-07-28  7:37 ` Thomas Petazzoni [this message]
2012-07-28 16:43 ` 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=20120728093729.45429122@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox