On 05/24/13 04:17, Raphael Kubo da Costa wrote:
> Lawrence Stewart writes:
>
>> On 05/20/13 23:22, Raphael Kubo da Costa wrote:
>>> SVN commit 9242 by rakuco:
>>>
>>> kdenetwork4: Add my upstream commit to fix the build with
On 05/20/13 23:22, Raphael Kubo da Costa wrote:
> SVN commit 9242 by rakuco:
>
> kdenetwork4: Add my upstream commit to fix the build with clang.
>
>
> AMpatch-kget__core__transferhistorystore.cpp
Any chance you can push this to ports svn? I'm hitting the kdenetwork4
clang build
On 12/22/11 22:54, Lawrence Stewart wrote:
On 12/22/11 20:15, Alberto Villa wrote:
On Thursday 22 December 2011 08:32:05 Lawrence Stewart wrote:
Since updating to KDE 4.7.3 on my FreeBSD 8-STABLE amd64 work
desktop,
plasma-desktop is suffering from a consistent a fairly bad memory leak.
Is
On 12/22/11 20:15, Alberto Villa wrote:
On Thursday 22 December 2011 08:32:05 Lawrence Stewart wrote:
Since updating to KDE 4.7.3 on my FreeBSD 8-STABLE amd64 work
desktop,
plasma-desktop is suffering from a consistent a fairly bad memory leak.
Is this a known issue that I missed seeing
Hi All,
Since updating to KDE 4.7.3 on my FreeBSD 8-STABLE amd64 work desktop,
plasma-desktop is suffering from a consistent a fairly bad memory leak.
After running for about 3 days, plasma-desktop grew to ~900MB of
resident memory:
lstewart@lstewart> ps -l 26994
UID PID PPID CPU PRI
On 11/29/11 16:27, David Naylor wrote:
On Monday, 28 November 2011 02:32:00 Lawrence Stewart wrote:
On 11/26/11 10:19, ajtiM wrote:
Is it a bug on automoc or gcc still "alive", please?,
It happened three times on my new installed FreeBSD 9.0 RC-2 during
building KDE 4. Two times st
On 11/26/11 10:19, ajtiM wrote:
Is it a bug on automoc or gcc still "alive", please?,
It happened three times on my new installed FreeBSD 9.0 RC-2 during building
KDE 4. Two times stopped when I built kde4-workspace and once in kdelibs4.
https://bugs.kde.org/show_bug.cgi?id=276461
I'm still
On 10/23/11 13:02, Raphael Kubo da Costa wrote:
Lawrence Stewart writes:
So yes, I've already done this and it does work. The question is why
doesn't it build successfully with MAKE_JOBS_SAFE? Obviously it has
been working for Alberto or he wouldn't have enabled it. I have a 6
On 10/23/11 13:02, Raphael Kubo da Costa wrote:
Lawrence Stewart writes:
So yes, I've already done this and it does work. The question is why
doesn't it build successfully with MAKE_JOBS_SAFE? Obviously it has
been working for Alberto or he wouldn't have enabled it. I have a 6
Hi Max,
On 10/22/11 03:25, Max Brazhnikov wrote:
On Sat, 22 Oct 2011 03:11:30 +1100, Lawrence Stewart wrote:
On 09/07/11 02:06, Alberto Villa wrote:
SVN commit 7609 by avilla:
- Mark MAKE_JOBS_SAFE.
I just finished upgrading to KDE 4.7.2 but astro/marble kept failing to
build during the
On 09/07/11 02:06, Alberto Villa wrote:
SVN commit 7609 by avilla:
- Mark MAKE_JOBS_SAFE.
I just finished upgrading to KDE 4.7.2 but astro/marble kept failing to
build during the portmaster update. I found that by disabling
MAKE_JOBS_SAFE, the marble build would successfully continue to comp
11 matches
Mail list logo
