-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 10/12/2013 07:43 PM, Anton Gladky wrote:
> Thanks all, guys, for recommendations and explanations. I will try to split
> some large cpp-files as Dmitrijs mentioned (there are a couple of them,
> which are failing reliably on weak archs), remove so
Thanks all, guys, for recommendations and explanations. I will try to
split some large cpp-files as Dmitrijs mentioned (there are a couple of
them, which are failing reliably on weak archs), remove some
optimization options as Mathieu advised and we will see, whether it helps.
I would also try to
Anton,
On Fri, Oct 11, 2013 at 9:00 PM, Anton Gladky wrote:
[...]
>> /usr/bin/c++ -Dyade_EXPORTS -g -O2 -fstack-protector
>> --param=ssp-buffer-size=4 -Wformat -Werror=format-security
>> -D_FORTIFY_SOURCE=2 -DYADE_PTR_CAST=static_pointer_cast
>> -DYADE_CAST=static_cast -fPIC -DYADE_VTK -DYA
On 11 October 2013 22:34, Ben Hutchings wrote:
> On Fri, Oct 11, 2013 at 09:55:34PM +0100, Dmitrijs Ledkovs wrote:
> [...]
>> I'm not sure, but launchpad is running 64-bit machines even when
>> compiling for the i386 architecture, and then launchpad supports PAE
>> only and thus can get >4GB of ad
On Fri, Oct 11, 2013 at 09:55:34PM +0100, Dmitrijs Ledkovs wrote:
> I'm not sure, but launchpad is running 64-bit machines even when
> compiling for the i386 architecture, and then launchpad supports PAE
> only and thus can get >4GB of address space.
A 32-bit process can still only address 32-bits
On Fri, Oct 11, 2013 at 09:55:34PM +0100, Dmitrijs Ledkovs wrote:
[...]
> I'm not sure, but launchpad is running 64-bit machines even when
> compiling for the i386 architecture, and then launchpad supports PAE
> only and thus can get >4GB of address space.
[...]
Which bit of 'Physical Address Exte
On 11 October 2013 20:32, Steve Langasek wrote:
> severity 726009 serious
> thanks
>
> This remains a serious bug. Your package, which previously built on
> multiple architectures, is now failing to build due to memory exhaustion.
> While in some circumstances it is permissible to remove the old
On Fri, Oct 11, 2013 at 12:32:27PM -0700, Steve Langasek wrote:
> severity 726009 serious
> thanks
>
> This remains a serious bug. Your package, which previously built on
> multiple architectures, is now failing to build due to memory exhaustion.
> While in some circumstances it is permissible t
severity 726009 wishlist
retitle 726009 Yade requires too much RAM for building
thanks
Hello,
thanks for bug-report. The problem is, that all build-failures are due
to insufficient RAM on build-machines [1]. I do not really know how to
"fix" that except of backlisting of some machines, as was sug
9 matches
Mail list logo
