From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 9016] arceb-buildroot-linux-uclibc ld uses incorrect default format
Date: Thu, 28 Jul 2016 19:14:35 +0000 [thread overview]
Message-ID: <bug-9016-163-F0Unlo8ZHx@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-9016-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=9016
--- Comment #1 from Vlad Zakharov <Vladislav.Zakharov@synopsys.com> ---
Hi,
I built toolchain in buildroot, tried to run your examples and got the
following results:
--------------------->8-------------------
.../arceb-buildroot-linux-uclibc/bin/ld --print-output-format
elf32-bigarc
--------------------->8-------------------
Please provide more about conditions under which the failure occurred, e.g.
what toochain version and git revision were used.
That would help us to catch and fix the issue.
Thanks,
Vlad.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2016-07-28 19:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-17 14:58 [Buildroot] [Bug 9016] New: arceb-buildroot-linux-uclibc ld uses incorrect default format bugzilla at busybox.net
2016-07-28 19:14 ` bugzilla at busybox.net [this message]
2016-07-28 20:21 ` [Buildroot] [Bug 9016] " bugzilla at busybox.net
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=bug-9016-163-F0Unlo8ZHx@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--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