Make commands...

Lowell Gilbert freebsd-ports-local at be-well.ilk.org
Wed Nov 20 15:15:28 UTC 2013


Boris Samorodov <bsam at passap.ru> writes:

> 20.11.2013 05:34, Joe Nosay пишет:
>> On Tue, Nov 19, 2013 at 9:35 AM, Lowell Gilbert <
>> freebsd-ports-local at be-well.ilk.org> wrote:
>> 
>>> Joe Nosay <superbisquit at 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.

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. 


More information about the freebsd-ports mailing list