Date: Thu, 21 Nov 2013 21:12:25 -0500 From: Joe Nosay <superbisquit@gmail.com> To: ports <ports@freebsd.org> Subject: Re: Make commands... Message-ID: <CA%2BWntOvpJAGfRDM_J0HKni%2BED=9axfK1yQbSbHOTWOQhXMpQ5A@mail.gmail.com> In-Reply-To: <CA%2BWntOtj9hFMDQSh5RQgGNDhPccpYGTu2Wk1pvHmXgw=n3SwQQ@mail.gmail.com> References: <CA%2BWntOt0B6Gdmjp6WwA0_ZnqJRr-1VkbXYrbVOML43OhtvLVAA@mail.gmail.com> <448uwkihmw.fsf@lowell-desk.lan> <CA%2BWntOte7DdNSTTPZBeYyzv1ijZx8S27Tnzis6tNcw3YmoFHNA@mail.gmail.com> <528C6D60.2030409@passap.ru> <44zjozrto0.fsf@be-well.ilk.org> <CA%2BWntOtj9hFMDQSh5RQgGNDhPccpYGTu2Wk1pvHmXgw=n3SwQQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
The flags for debugging have been chosen with -d dclV to prevent excess information. CPUFLAGS directory was changed to the jailed debian environment. On Wed, Nov 20, 2013 at 9:47 PM, Joe Nosay <superbisquit@gmail.com> wrote: > > > > > > On Wed, Nov 20, 2013 at 10:15 AM, Lowell Gilbert < > freebsd-ports-local@be-well.ilk.org> wrote: > >> Boris Samorodov <bsam@passap.ru> writes: >> >> > 20.11.2013 05:34, Joe Nosay =D0=BF=D0=B8=D1=88=D0=B5=D1=82: >> >> On Tue, Nov 19, 2013 at 9:35 AM, Lowell Gilbert < >> >> freebsd-ports-local@be-well.ilk.org> wrote: >> >> >> >>> Joe Nosay <superbisquit@gmail.com> writes: >> >>> >> >>>> Is there a flag for verbose output? >> >>> >> >>> "-v" will cause make to be verbose. >> >>> >> >>> If what you actually want is to have the things make calls >> >>> be verbose, then you need to configure make to tell those >> >>> other programs in whatever way is appropriate. Adding >> >>> "-Wall" to CFLAGS is a familiar example -- for gcc. >> >> >> >> I'm using CLang when possible. As suggested by Wolfskill in the reply >> >> before yours, would that be >> >> "#make -V MAKE.MODE=3D=3Dm MAKE.MODE=3D=3Dv" from the command line ? = It's a >> SIGSEGV >> >> fault that I am trying to trace. >> > >> > Seems that MAKE(1) (search for "debug") may help you. >> >> I'm guessing that the problem Joe is having is actually with clang, or >> maybe the executable clang produces, not with make itself. I base that >> on the reference to segment violations, but it's just a guess. He needs >> to be more specific about the symptoms he wants to fix, or else we'll >> tend to solve the wrong problem. >> >> If clang itself is seg-faulting, my advice would be to use the latest >> version of clang, and get a coredump. >> > > http://slexy.org/view/s21n8x1u6C > > > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CA%2BWntOvpJAGfRDM_J0HKni%2BED=9axfK1yQbSbHOTWOQhXMpQ5A>