From: Alexander Lukichev <alexander.lukichev@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] i686-buildroot-linux-gnu-as does not work
Date: Sun, 26 Jan 2014 19:12:50 +0200 [thread overview]
Message-ID: <52E54212.8090100@gmail.com> (raw)
In-Reply-To: <1390645407.666601332@f346.i.mail.ru>
Hi Kirill,
01/25/2014 12:23 PM, ?????? ??????? wrote:
> I have got very strange error during building of BuildRoot project.
> It happens after running following commands in
> /.../BuildRoot/output/build/infozip-30 directory:
Could you please send your Buildroot config file attached or pasted
into the message text as defconfig? You can produce defconfig by
make savedefconfig BR2_DEFCONFIG=<path-to-defconfig>
What Buildroot release / commit id do you use?
--
Best regards,
Alexander Lukichev
next prev parent reply other threads:[~2014-01-26 17:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-25 10:23 [Buildroot] i686-buildroot-linux-gnu-as does not work Кирилл Луценко
2014-01-26 17:12 ` Alexander Lukichev [this message]
2014-01-26 19:33 ` Кирилл Луценко
2014-01-27 7:37 ` Кирилл Луценко
2014-01-27 10:59 ` Romain Naour
2014-01-27 11:47 ` Alexander Lukichev
2014-01-27 12:48 ` Romain Naour
2014-01-27 22:23 ` Arnout Vandecappelle
2014-01-30 22:20 ` Romain Naour
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=52E54212.8090100@gmail.com \
--to=alexander.lukichev@gmail.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