From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] new package not built, AR prefix not passed to make
Date: Thu, 03 Apr 2014 12:50:24 -0300 [thread overview]
Message-ID: <533D8340.8060400@zacarias.com.ar> (raw)
In-Reply-To: <130678126.102439.1396539806273.JavaMail.root@mail>
On 04/03/2014 12:43 PM, ?meric Vigier wrote:
>> Why is AR prefix not passed to make here? Is this related to the
>> generic-package?
>
> I believe I found part of my answer on gnu.org libc manual:
> You may need to set AR to cross-compiling versions of ar if the native tools
> are not configured to work with object files for the target you configured for.
>
> $ ar --help
> [...]
> ar: supported targets: elf64-x86-64 elf32-i386 elf32-x86-64 a.out-i386-linux pei-i386 pei-x86-64 elf64-l1om elf64-k1om elf64-little elf64-big elf32-little elf32-big plugin srec symbolsrec verilog tekhex binary ihex
>
> So I guess buildroot makes such a sanity check, right?
You just need to use $(TARGET_AR) the same way you're using $(TARGET_CC)
and others.
Snip:
define LIBFPGA_BUILD_CMDS
$(MAKE) CC="$(TARGET_CC)" LD="$(TARGET_LD)" \
AR="$(TARGET_AR)" -C $(@D) all
endef
Or better still what usually works...
$(MAKE) $(TARGET_CONFIGURE_OPTS) -C $(@D)
Regards.
next prev parent reply other threads:[~2014-04-03 15:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1080754998.70934.1396536817436.JavaMail.root@mail>
2014-04-03 15:32 ` [Buildroot] new package not built, AR prefix not passed to make Émeric Vigier
2014-04-03 15:43 ` Émeric Vigier
2014-04-03 15:50 ` Gustavo Zacarias [this message]
2014-04-03 15:53 ` Émeric Vigier
2014-04-03 17:21 ` Lionel Orry
2014-04-03 18:11 ` Émeric Vigier
2014-04-04 5:46 ` Lionel Orry
2014-04-04 5:30 ` Arnout Vandecappelle
2014-04-04 19:36 ` Émeric Vigier
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=533D8340.8060400@zacarias.com.ar \
--to=gustavo@zacarias.com.ar \
--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.