Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.os.linux.misc > #11205

Re: GCC verbose compilation

Show all headers | View raw

Richard Kettlewell wrote:

> Robert Heller <heller@deepsoft.com> writes:
>> Baho Utot <baho-utot@invalid.com> wrote:
>>> Tauno Voipio wrote:
>>>> On 5.6.14 23:47, Baho Utot wrote:
> 
>>>>> This is the results from some packages like bison
>>>>>
>>>>>    GEN      lib/ref-del.sed
>>>>>    CC       src/bison-AnnotationList.o
>>>>>    CC       src/bison-InadequacyList.o
>>>>>    CC       src/bison-LR0.o
>>>>>    CC       src/bison-assoc.o
>>>>>    CC       src/bison-closure.o
>>>>>    CC       src/bison-complain.o
>>>>>    CC       src/bison-Sbitset.o
>>>>>    CC       src/bison-conflicts.o
>>>>>    CC       src/bison-derives.o
>>>>>    CC       src/bison-files.o
>>>>>    CC       src/bison-getargs.o
>>>>>    CC       src/bison-gram.o
>>>>>
>>>>> The make line used for both packages:
>>>>>
>>>>> make VERBOSE=1 -j8
> 
> make V=1
> should do it.

Not for all packages that I am building.  I "started there/ tried that" 
and it got me to within 8 packages that still didn't produce verbose 
output.  Somehow those Makefile(s) ignore V=1.

I have found that one has to add --disable-silent-rules to configure 
<whatever> as some packages will ignore V=1 or VERBOSE=1.  
--disable-silent-rules works for those hard cases.

> 
>>>>> Why does some packages not obey the VERBOSE flag?
>>>>>
>>>>> Can I change the make line to get the results I am looking for?
>>>> Did you read the Makefile?
>>>> The solution is in the Makefile, refer to the Make manual.
>>>
>>> The solution was not in the Makefile and refering to the Make manual
>>> producinges no results.  The solution is not in the Makefile(s).
>>> 
>>> Adding --disable-silent-rules to configure fixes the problem.
>>> 
>>> This was an autotools issue.
>>
>> Autotools/Automake is what *generates* the Makefile.
> 
> Telling people to read six-thousand line Automake-generated makefiles
> to find something that can actually be found in two places in the
> documentation is roughly analogous to telling someone to disassemble
> /bin/ls to find out what the option for long-form output is.
> 
> For the benefit of people who want to know the easy way to find out:
> It’s documented in the INSTALL file included in Bison, and the output
> of ./configure --help.
> 

That's why I posted this as I don't have time to read the complete 
manuals or all the Makefile(s).   I figured someone here would have run 
into this issues as well.

I could have read all those six-thousand lines and still had the issue.

Back to comp.os.linux.misc | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

GCC verbose compilation Baho Utot <baho-utot@invalid.com> - 2014-06-05 16:47 -0400
  Re: GCC verbose compilation Tauno Voipio <tauno.voipio@notused.fi.invalid> - 2014-06-06 08:47 +0300
    Re: GCC verbose compilation Baho Utot <baho-utot@invalid.com> - 2014-06-06 07:03 -0400
      Re: GCC verbose compilation Robert Heller <heller@deepsoft.com> - 2014-06-06 08:25 -0500
        Re: GCC verbose compilation Baho Utot <baho-utot@invalid.com> - 2014-06-06 11:06 -0400
        Re: GCC verbose compilation Richard Kettlewell <rjk@greenend.org.uk> - 2014-06-06 18:14 +0100
          Re: GCC verbose compilation Baho Utot <baho-utot@invalid.com> - 2014-06-06 16:16 -0400
          Re: GCC verbose compilation Tauno Voipio <tauno.voipio@notused.fi.invalid> - 2014-06-06 23:15 +0300
            Re: GCC verbose compilation Richard Kettlewell <rjk@greenend.org.uk> - 2014-06-07 09:39 +0100

csiph-web