Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 20 Nov 2013 12:05:52 +0400
From:      Boris Samorodov <bsam@passap.ru>
To:        Joe Nosay <superbisquit@gmail.com>
Cc:        ports <ports@freebsd.org>
Subject:   Re: Make commands...
Message-ID:  <528C6D60.2030409@passap.ru>
In-Reply-To: <CA%2BWntOte7DdNSTTPZBeYyzv1ijZx8S27Tnzis6tNcw3YmoFHNA@mail.gmail.com>
References:  <CA%2BWntOt0B6Gdmjp6WwA0_ZnqJRr-1VkbXYrbVOML43OhtvLVAA@mail.gmail.com> <448uwkihmw.fsf@lowell-desk.lan> <CA%2BWntOte7DdNSTTPZBeYyzv1ijZx8S27Tnzis6tNcw3YmoFHNA@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
20.11.2013 05:34, Joe Nosay пишет:
> 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==m MAKE.MODE==v" 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.

-- 
WBR, Boris Samorodov (bsam)
FreeBSD Committer, http://www.FreeBSD.org The Power To Serve



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?528C6D60.2030409>