attaching an interrupt in beaglebone bsp

Chris Johns chrisj at rtems.org
Wed Jun 17 04:25:22 UTC 2015


On 17/06/2015 1:57 pm, Joel Sherrill wrote:
> 
> 
> On 6/16/2015 8:52 PM, Chris Johns wrote:
>> On 17/06/2015 9:48 am, Angelo Fraietta wrote:
>>> So I replace
>>>
>>> %define qemu_version ac0bfdb9c310276521e5b089d7f36c1f610ca60b
>>>
>>> with
>>> %define qemu_version e571600c4a260d3072abbe7ecf2013e48e82bea7
>>>
>>
>> Yes.
>>
>>> (I don't want top break anything)
>>>
>>
>> The RSB should take care of the rest and it should put the git repo it
>> has cloned in the correct state.
> 
> I updated to a commit within the past 24 hours and got the same result on
> Centos 6.
> 
> lt LINK vscclient
>   LINK  qemu-bridge-helper
> /usr/bin/ld: -f may not be used without -shared
> collect2: ld returned 1 exit status
> make: *** [vscclient] Error 1
> make: *** Waiting for unfinished jobs....
> shell cmd failed: /bin/sh -ex 
> /home/joel/rtems-4.11-work/rtems-source-builder/bare/build/qemu-93f6d1c16036aaf34055d16f54ea770fb8d6d280-i686-linux-gnu-1/doit
> 
> error: building
> qemu-93f6d1c16036aaf34055d16f54ea770fb8d6d280-i686-linux-gnu-1
> 
> This appears to be the same as this issue on launchpad.
> 
> https://bugs.launchpad.net/qemu/+bug/1258168
> 
> I haven't looked into it much but that is from 2014 so should be merged
> already.
> 

Can you please check patchworks ? If the patch is in patchworks and not
merged we can include it.


> FWIW doing a make -k, it appears that this is the only build error on
> CentOS 6.
> 
> Interestingly, I moved over to the CentOS 7.1 and it failed here:
> 
> install: cannot stat
> '/data/home/joel/rtems-4.11-work/rtems-source-builder/bare/build/qemu-93f6d1c16036aaf34055d16f54ea770fb8d6d280-x86_64-linux-gnu-1/qemu-93f6d1c16036aaf34055d16f54ea770fb8d6d280/pc-bios/vgabios-virtio.bin':
> No such file or directory
> 
> Please double check me on the analysis of the launchpad report and
> see if it is the same. I have no idea what the Centos 7 issue is but
> that file does not appear to be in the current source. It could have
> been removed and the install stanza not updated.
> 

No idea. I am afraid you will have to chase this one down.

Chris


More information about the users mailing list