I've marked this wontfix, as it's a limitation of the ARM architecture.
Mapping the same shared memory twice in one process is stupid, anyway.
Just disable the test on armel and armhf.
Ben.
--
Ben Hutchings
Lowery's Law:
If it jams, force it. If it breaks, it needed replacing anyway
On Do, 28 Jun 2012, peter green wrote:
> I have now confirmed that rebuilding texlive-bin with -marm on armhf
> fixes the lilypond build failure.
Ok, I will uploadthe packages with the -marm change plus other changes
in a minute.
Best wishes
Norbert
Simon Baatz wrote (28 Jun 2012 18:21:28 GMT) :
> This seems to be another instance of VIVT L1 caching weirdness.
> The problem has been discussed years ago on the arm kernel mailing
> list (see [1]) and a patch has been proposed at that time.
> Apparently, that never made it into the kernel.
Thank
Norbert Preining wrote:
Hi Peter,
On Do, 28 Jun 2012, peter green wrote:
commit until I confirm that this solves the problem.
ANy progress on that? I am preparing new packages from the TL sources
now ...
I have now confirmed that rebuilding texlive-bin with -marm on armhf
fixes th
On Wed, Jun 27, 2012 at 12:20:05AM +0200, intrigeri wrote:
> shawn wrote (17 Jun 2012 03:13:04 GMT) :
> > on 3.4 (custom) + sheevaplug:
>
> > $ gcc -O0 625828.c
> > $ ./a.out
> > ok 1 - got 2000, expected 2000
>
> I asked for more thorough testing, and shawn reported
> "I ran it 500 times, it s
Hi Peter,
On Do, 28 Jun 2012, peter green wrote:
> commit until I confirm that this solves the problem.
ANy progress on that? I am preparing new packages from the TL sources
now ...
Best wishes
Norbert
Norbert Preining
6 matches
Mail list logo
