The only thing that changed in my setup, Virtualbox, scratchbox2, arm debian rootfs & qemu-linaro is that i pulled a newer version than march 30th and i went from some expected errors http://pastebin.com/QTt8S9kT to http://pastebin.com/2SRJRvdp
not really sure where to even start tracking it down other than comparing a last known working version, git pulled on March 30th with one that doesn't anything since April 1st.
bst rgrds Russell
On 12 April 2012 16:22, Russell Keith Davis russell@russelldavis.org wrote:
The only thing that changed in my setup, Virtualbox, scratchbox2, arm debian rootfs & qemu-linaro is that i pulled a newer version than march 30th and i went from some expected errors http://pastebin.com/QTt8S9kT to http://pastebin.com/2SRJRvdp
If you can provide me with an easy way to reproduce this on my machine I can have a look at it.
not really sure where to even start tracking it down other than comparing a last known working version, git pulled on March 30th with one that doesn't anything since April 1st.
If you could do a git bisect and identify the failing commit that would be one way to try to narrow things down.
thanks -- PMM
On 4/12/2012 11:47 AM, Peter Maydell wrote:
On 12 April 2012 16:22, Russell Keith Davisrussell@russelldavis.org wrote:
The only thing that changed in my setup, Virtualbox, scratchbox2, arm debian rootfs& qemu-linaro is that i pulled a newer version than march 30th and i went from some expected errors http://pastebin.com/QTt8S9kT to http://pastebin.com/2SRJRvdp
If you can provide me with an easy way to reproduce this on my machine I can have a look at it.
I don't actually use qemu on "real" hardware so not 100% sure it is a qemu-linaro problem really but the easiest way to replicate would be to setup a vm similar to what I have been using these instructions http://pastebin.com/4Jp1WPTb as the premade vm i released is pretty large (8GB)
pretty much anything i've built other than a simple hello,world is giving that error.
not really sure where to even start tracking it down other than comparing a last known working version, git pulled on March 30th with one that doesn't anything since April 1st.
If you could do a git bisect and identify the failing commit that would be one way to try to narrow things down.
i'm a n00b with git, only thin i ever used it for was pulling and cloning but i'll see what I can do
bst rgrds Russell
On 12 April 2012 17:08, Russell Keith Davis russell@russelldavis.org wrote:
On 4/12/2012 11:47 AM, Peter Maydell wrote:
If you can provide me with an easy way to reproduce this on my machine I can have a look at it.
I don't actually use qemu on "real" hardware so not 100% sure it is a qemu-linaro problem really but the easiest way to replicate would be to setup a vm similar to what I have been using these instructions http://pastebin.com/4Jp1WPTb
OK, I followed those and now have a scratchbox environment that runs "hello world". (I was temporarily confused by 'sb2-init raspberrypi_debian6' not setting that as the default sb2 config -- you might want to add a line saying to run 'sb2-config -d raspberrypi_debian6'...)
pretty much anything i've built other than a simple hello,world is giving that error.
So do you have an example of a program that *does* give the error, rather than one that doesn't?
thanks -- PMM
On 12 April 2012 16:22, Russell Keith Davis russell@russelldavis.org wrote:
The only thing that changed in my setup, Virtualbox, scratchbox2, arm debian rootfs & qemu-linaro is that i pulled a newer version than march 30th and i went from some expected errors http://pastebin.com/QTt8S9kT to http://pastebin.com/2SRJRvdp
For the record, this is fixed by the following patch: http://patchwork.ozlabs.org/patch/152614/ which will go into qemu-linaro 2012.05.
Thanks for reporting this bug.
-- PMM
-
Peter Maydell -
Russell Keith Davis