(hi edmund, i'm reinstating debian-devel on the cc list as this is not
a debian-arm problem, it's *everyone's* problem)
On Mon, Jan 7, 2019 at 12:40 PM Edmund Grimley Evans
wrote:
> > i spoke with dr stallman a couple of weeks ago and confirmed that in
> > the original version of ld that he
The Haskell CP15 failures might be this:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=864847
Since it is claimed there that the CP15 instructions come from LLVM,
the Mono failures might have a very similar cause and solution.
On Sun, Jan 6, 2019 at 11:46 PM Steve McIntyre wrote:
>
> [ Please note the cross-post and respect the Reply-To... ]
>
> Hi folks,
>
> This has taken a while in coming, for which I apologise. There's a lot
> of work involved in rebuilding the whole Debian archive, and many many
> hours spent
> i spoke with dr stallman a couple of weeks ago and confirmed that in
> the original version of ld that he wrote, he very very specifically
> made sure that it ONLY allocated memory up to the maximum *physical*
> resident available amount (i.e. only went into swap as an absolute
> last resort),
On Mon, Jan 07, 2019 at 09:54:32AM +, Edmund Grimley Evans wrote:
>The Haskell CP15 failures might be this:
>
>https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=864847
>
>Since it is claimed there that the CP15 instructions come from LLVM,
>the Mono failures might have a very similar cause and
On Tuesday, January 8, 2019, Mike Hommey wrote:
> .
>
> Note that Firefox is built with --no-keep-memory
> --reduce-memory-overheads, and that was still not enough for 32-bts
> builds. GNU gold instead of BFD ld was also given a shot. That didn't
> work either. Presently, to make things link at
On Mon, Jan 07, 2019 at 10:28:31AM +, Luke Kenneth Casson Leighton wrote:
> On Sun, Jan 6, 2019 at 11:46 PM Steve McIntyre wrote:
> >
> > [ Please note the cross-post and respect the Reply-To... ]
> >
> > Hi folks,
> >
> > This has taken a while in coming, for which I apologise. There's a lot
Hi Debian ARM List
I'm running debian stretch on my QNAP TS-210.
Under QNAP firmware I was able to get the system temperature using this
command:
# cat /proc/tsinfo/systemp
Where (filename) can I read out the system temperature under debian?
(I wasn't able to find the aswer by my self.)
On Mon, Jan 07, 2019 at 11:46:41PM +, Luke Kenneth Casson Leighton wrote:
> On Tuesday, January 8, 2019, Mike Hommey wrote:
>
> > .
> >
> > Note that Firefox is built with --no-keep-memory
> > --reduce-memory-overheads, and that was still not enough for 32-bts
> > builds. GNU gold instead of
On Tuesday, January 8, 2019, Mike Hommey wrote:
> On Mon, Jan 07, 2019 at 11:46:41PM +, Luke Kenneth Casson Leighton
> wrote:
>
> > At some point apps are going to become so insanely large that not even
> > disabling debug info will help.
>
> That's less likely, I'd say. Debug info *is*
On Tue, Jan 8, 2019 at 6:27 AM Luke Kenneth Casson Leighton
wrote:
> i'm just running the above, will hit "send" now in case i can't hit
> ctrl-c in time on the linker phase... goodbye world... :)
$ python evil_linker_torture.py 2000 50 100 200
$ make -j8
oh, err... whoopsie... is this
On Tue, Jan 8, 2019 at 7:01 AM Luke Kenneth Casson Leighton
wrote:
> i'm going to see if i can get above the 4GB mark by modifying the
> Makefile to do 3,000 shared libraries instead of 3,000 static object
> files.
fail. shared libraries link extremely quickly. reverted to static,
trying
$ python evil_linker_torture.py 2000 50 100 200
ok so it's pretty basic, and arguments of "2000 50 10 100"
resulted in around a 10-15 second linker phase, which top showed to be
getting up to around the 2-3GB resident memory range. "2000 50 100
200" should start to make even a system
$ python evil_linker_torture.py 3000 100 100 50
ok so that managed to get up to 1.8GB resident memory, paused for a
bit, then doubled it to 3.6GB, and a few seconds later successfully
outputted a binary.
i'm going to see if i can get above the 4GB mark by modifying the
Makefile to do 3,000
On January 7, 2019 8:44:55 PM UTC, "namo...@gmx.net" wrote:
>Hi Debian ARM List
Hi Roman,
>I'm running debian stretch on my QNAP TS-210.
>Under QNAP firmware I was able to get the system temperature using this
>
>command:
># cat /proc/tsinfo/systemp
>
>Where (filename) can I read out the system
15 matches
Mail list logo