Date: Tue, 5 Aug 2014 17:09:55 +0200 From: Luca Pizzamiglio <luca.pizzamiglio@gmail.com> To: Raphael Kubo da Costa <rakuco@freebsd.org> Cc: freebsd-stable@freebsd.org, freebsd-ports@freebsd.org Subject: Re: [9.2-STABLE/CLANG 3.3|3.4] x11/kdelibs4 Message-ID: <CAB88xy-kC-RN3Hp6PCFKR9X1tEdB9xRL9eVdqh00NSny5fCrzQ@mail.gmail.com> In-Reply-To: <86ppkblrkw.fsf@orwell.Elisa> References: <20140418081014.2ac2536e@munin.walstatt.dyndns.org> <641C6CAA-C472-4359-9293-E65F16E84DC6@FreeBSD.org> <20140419103237.41962eff.ohartman@zedat.fu-berlin.de> <A9688D03-8CC4-4C60-9BBD-A364BB598D46@FreeBSD.org> <20140419193019.0ee792e6.ohartman@zedat.fu-berlin.de> <CBBECAB9-B48F-416C-BE39-64D6D5738B9C@FreeBSD.org> <20140420174725.199ec7af.ohartman@zedat.fu-berlin.de> <C340C8EC-9AE2-495F-9141-76B4571E0DBE@FreeBSD.org> <86ppkblrkw.fsf@orwell.Elisa>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi list, I've updated my system to FreeBSD 9.3, with clang 3.4. My make.conf set clang as default compiler. kdelibs4 seems having a problem, or better, clang 3.4 seems having a problem to compile one specific kdelibs4's file. clang++ compiles the file parser.cpp (khtml/css module) for ever and ever... Looking into it, it seems generated by bison 2.5.1, but the currently installed bison is 2.7.1. It's not the same problem with Kate, (Kate build process needs 5GB RAM, more or less), because I verified the RAM usage: SIZE is ~90-100MB, RSS 70-80MB, swap used 0KB. The current workaround is using gcc. Is it a known issue? Moreover, is it a clang problem? A kdelibs problem? A bison problem? Best regards, pizzamig On Sun, Apr 20, 2014 at 9:38 PM, Raphael Kubo da Costa <rakuco@freebsd.org> wrote: > Dimitry Andric <dim@FreeBSD.org> writes: > >>> The box in question is a Dell Latitude E6510 notebook with only 4 GB of RAM, could this >>> be the issue? The system very often starts swapping. Even my oldstyle E8400 workstation >>> with only 8 GB (most recent 11.0-CURRENT) starts swapping very often and recently, I saw >>> musterious compiler erros and stopping compiling processes never seen bevor. Restarting >>> the failed portbuild most often finish successfully. >> >> There were some postings recently, about newer versions of FreeBSD being >> supposedly more "swappy", see e.g.: >> >> http://lists.freebsd.org/pipermail/freebsd-stable/2014-April/thread.html#78361 >> >> I have no idea if this is really substantiated with evidence, or just a >> feeling, though. :) >> >> In any case, when you are experiencing mysterious compiler errors, and >> your system is heavily exercising RAM and swap, it is always a good idea >> to do a full hardware diagnostics test. >> >> For your RAM, you can use memtest86+, and since you have a Dell, you can >> use their diagnostics program to test other parts of the machine. > > For what it's worth, ports/187150 might be related to this as well (I've > never experienced those problems myself, but I'm on HEAD). > > _______________________________________________ > freebsd-ports@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAB88xy-kC-RN3Hp6PCFKR9X1tEdB9xRL9eVdqh00NSny5fCrzQ>