On Tuesday 9. January 2018 18.28.52 James Cowgill wrote:
>
> Thanks for this. I think I know what's going on now.
Thanks for replying and figuring it out from my notes!
[...]
> The problem here is that the assembler and GCC don't agree on whether
> thread2 is a global or local symbol. In GCC
Hi,
On 08/01/18 18:09, Paul Boddie wrote:
> On Thursday 21. December 2017 00.08.09 Paul Boddie wrote:
>> On Wednesday 20. December 2017 14.46.12 James Cowgill wrote:
>>> It would be useful to have a reduced .c file which can reproduce this
>>> bug and then decide if its a bug in gcc or binutils.
On Thursday 21. December 2017 00.08.09 Paul Boddie wrote:
> On Wednesday 20. December 2017 14.46.12 James Cowgill wrote:
> > It would be useful to have a reduced .c file which can reproduce this
> > bug and then decide if its a bug in gcc or binutils.
>
> The offending program is this one:
>
>
On Wednesday 20. December 2017 14.46.12 James Cowgill wrote:
>
> There are probably two bugs here. Firstly, ld shouldn't trigger an
> internal error when printing the error message...
Perhaps. I didn't know how to interpret that.
> > Relocation section '.rel.text.startup' at offset 0x5398
Hi,
On 20/12/17 01:06, Paul Boddie wrote:
> Package: binutils-mipsel-linux-gnu
> Version: 2.29.1-12
> Severity: normal
>
> Dear Maintainer,
>
> I have been attempting to build L4Re with the mipsel cross-toolchain, which
> has so far worked well, but after updating the L4Re sources to a newer
>
Package: binutils-mipsel-linux-gnu
Version: 2.29.1-12
Severity: normal
Dear Maintainer,
I have been attempting to build L4Re with the mipsel cross-toolchain, which
has so far worked well, but after updating the L4Re sources to a newer
revision, I now get the following error:
6 matches
Mail list logo
