From: Baruch Siach <baruch@tkos.co.il>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2014-02-23
Date: Tue, 25 Feb 2014 08:03:41 +0200 [thread overview]
Message-ID: <20140225060341.GP4869@tarshish> (raw)
In-Reply-To: <CAMo8BfJKYb9=iUNr3vnMkPqQGERhD4mY-NsGFxpa-0MDg+=znw@mail.gmail.com>
Hi Max,
On Tue, Feb 25, 2014 at 09:47:06AM +0400, Max Filippov wrote:
> On Tue, Feb 25, 2014 at 9:22 AM, Baruch Siach <baruch@tkos.co.il> wrote:
> > On Mon, Feb 24, 2014 at 09:36:01PM +0100, Thomas Petazzoni wrote:
> >> > > wireshark-1.10.5 | 1
> >> > xtensa | wireshark-1.10.5 | NOK |
> >> > http://autobuild.buildroot.net/results/3bbba270745d96a08ff6eb98f9f3d39ca3a3ea9e/
> >> >
> >> > {standard input}:119517: Error: operand 1 of 'j' has out of range
> >> > value '4294825646'
> >> > {standard input}:119521: Error: operand 1 of 'j' has out of range
> >> > value '4294828543'
> >> > {standard input}:119525: Error: operand 1 of 'j' has out of range
> >> > value '4294829836'
> >> > {standard input}:119529: Error: operand 1 of 'j' has out of range
> >> > value '4294830953'
> >> > {standard input}:119533: Error: operand 1 of 'j' has out of range
> >> > value '4294832702'
> >> > {standard input}:119537: Error: operand 1 of 'j' has out of range
> >> > value '4294834399'
> >> > {standard input}:119541: Error: operand 1 of 'j' has out of range
> >> > value '4294835783'
> >>
> >> Compiler problem. Should we disable wireshark for now?
> >
> > This problem appeared after the last wireshark version bump, and may as well
> > disappear after the next. The same goes for kmod
> > (http://autobuild.buildroot.net/results/1a6/1a6e7119feeb8c6098daf0d5cdc41aa778a30693/)
>
> I had a look at these two issues,
> kmod triggers a real bug in xtensa ld, by specifying --gc-sections option.
Thanks for investigating the issue. I'll try to come up with a patch for this.
> Disabling this option might be a workaround.
> With wireshark gcc generates 'j' jumps instead of 'jx' when jump
> targets are too far.
> Looks like gcc bug.
As you can see from the error message above, the target addresses seem to be
wrong (i.e., < 0).
> > and mplayer
> > (http://autobuild.buildroot.net/results/9d2/9d2cf930d51274e119a98f63c06741bf2014ca64/).
> > Disabling wireshark on xtensa for now is OK if it's enabled again on the next
> > version update.
baruch
--
http://baruch.siach.name/blog/ ~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -
next prev parent reply other threads:[~2014-02-25 6:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-24 7:30 [Buildroot] [autobuild.buildroot.net] Build results for 2014-02-23 Thomas Petazzoni
2014-02-24 8:38 ` Thomas De Schampheleire
2014-02-24 10:30 ` Peter Korsgaard
2014-02-24 11:37 ` Thomas De Schampheleire
2014-02-24 19:16 ` Arnout Vandecappelle
2014-02-25 5:50 ` Thomas De Schampheleire
2014-02-24 20:37 ` Thomas Petazzoni
2014-02-24 20:44 ` Yann E. MORIN
2014-02-24 20:36 ` Thomas Petazzoni
2014-02-25 5:22 ` Baruch Siach
2014-02-25 5:47 ` Max Filippov
2014-02-25 6:03 ` Baruch Siach [this message]
2014-02-25 6:15 ` Max Filippov
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=20140225060341.GP4869@tarshish \
--to=baruch@tkos.co.il \
--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