From mboxrd@z Thu Jan 1 00:00:00 1970 From: Baruch Siach Date: Tue, 25 Feb 2014 08:03:41 +0200 Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2014-02-23 In-Reply-To: References: <20140224073008.3ECD8100F60@stock.ovh.net> <20140224213601.6c287457@skate> <20140225052234.GO4869@tarshish> Message-ID: <20140225060341.GP4869@tarshish> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: buildroot@busybox.net 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 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 -