Hi Ed
Yes how do I get those logs? I will be checking dmesg from time to time (is
there a way to tail it by the way??) but then how do I enable verbose
logging while building world? I tried finding out the same by searching on
the internet and by reading the manual page for make.conf but couldn't
On 7 August 2017 at 00:32, Aijaz Baig wrote:
> That was some pretty relevant information Ed. Thanks.
Even though it's not a direct cause of the problem you encountered I
wanted to make sure a there was comprehensive reply to Dimitry's
question.
> Nonetheless, as I have indicated in my previous e
That was some pretty relevant information Ed. Thanks.
However upon bumping up my RAM, I don't hit this error anymore perhaps I
believe since the relatively large amount of RAM does not necessitate that
much of swap space.
Nonetheless, as I have indicated in my previous email, I hit an error quite
On 5 August 2017 at 16:16, Dimitry Andric wrote:
>
> I remember there being an issue with ar and/or ranlib choking when the
> .a files become too big. Ed, does that ring any bells?
Our ar (and ranlib, which is the same binary) will produce a corrupt
symbol table if the .a archive output is large
I did notice some swap related messages in dmesg earlier so this time I
bumped up my RAM to 4.25GB (did I tell you I'm running this on a VM?). In
addition I skipped parallel make jobs altogether keeping other things the
same.
So this time around it went a lot further in fact all the way to step4.3
Hello
Yes guilty as charged!!!
I turn off optimization and enable DEBUG_FLAGS using src.conf:
CFLAGS= -O0 -pipe
COPTFLAGS= -O0 -pipe
DEBUG_FLAGS=-g
This time however I run without any parallel make jobs and it fails with a
different error:
*** Signal 9
Stop.
make[6]: stopped in /usr/src/lib/c
Dimitry Andric dim at FreeBSD.org wrote on
Sat Aug 5 20:16:53 UTC 2017 :
> Hm, now I read that your obj dir is on NFS, you might be hitting some
> 4GiB filesize limit for the final .a file. Are you building world with
> a very low optimization level, and debug information on?
>
> I remember ther
On 5 Aug 2017, at 21:55, Aijaz Baig wrote:
>
> I was a bit sceptical of this as it was failing with that same port (or is
> clang a port by the way?) all the time. So as you suggested, I reduced my
> '-j' number and it still fails at the very same place with the very same
> error. Is it becaus
Hi Dmitry
I was a bit sceptical of this as it was failing with that same port (or is
clang a port by the way?) all the time. So as you suggested, I reduced my
'-j' number and it still fails at the very same place with the very same
error. Is it because the clang port doesn't allow parallel make jo
On 5 Aug 2017, at 06:00, Aijaz Baig wrote:
>
> I am trying to buildworld and it works well for quite some time until it
> tries to build the static version of the clang library where it fails. The
> error it spits is:
>
> Killed
> *** [all_subdir_lib/clang/libclang] Error code 137
>
> make[5]:
10 matches
Mail list logo
