Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.os.linux.misc > #11188 > unrolled thread
| Started by | Baho Utot <baho-utot@invalid.com> |
|---|---|
| First post | 2014-06-05 16:47 -0400 |
| Last post | 2014-06-07 09:39 +0100 |
| Articles | 9 — 4 participants |
Back to article view | Back to comp.os.linux.misc
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
| From | Baho Utot <baho-utot@invalid.com> |
|---|---|
| Date | 2014-06-05 16:47 -0400 |
| Subject | GCC verbose compilation |
| Message-ID | <ak176b-1lo.ln1@raspberrypi.bildanet.com> |
I would like to have gcc output like the following (excerpt from bzip2 compile) gcc -fpic -fPIC -Wall -Winline -march=x86-64 -mtune=generic -O2 -pipe - fno-strict-aliasing -g -D_FILE_OFFSET_BITS=64 -c blocksort.c gcc -fpic -fPIC -Wall -Winline -march=x86-64 -mtune=generic -O2 -pipe - fno-strict-aliasing -g -D_FILE_OFFSET_BITS=64 -c huffman.c gcc -fpic -fPIC -Wall -Winline -march=x86-64 -mtune=generic -O2 -pipe - fno-strict-aliasing -g -D_FILE_OFFSET_BITS=64 -c crctable.c gcc -fpic -fPIC -Wall -Winline -march=x86-64 -mtune=generic -O2 -pipe - fno-strict-aliasing -g -D_FILE_OFFSET_BITS=64 -c randtable.c gcc -fpic -fPIC -Wall -Winline -march=x86-64 -mtune=generic -O2 -pipe - fno-strict-aliasing -g -D_FILE_OFFSET_BITS=64 -c compress.c gcc -fpic -fPIC -Wall -Winline -march=x86-64 -mtune=generic -O2 -pipe - fno-strict-aliasing -g -D_FILE_OFFSET_BITS=64 -c decompress.c gcc -fpic -fPIC -Wall -Winline -march=x86-64 -mtune=generic -O2 -pipe - fno-strict-aliasing -g -D_FILE_OFFSET_BITS=64 -c bzlib.c 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 Why does some packages not obey the VERBOSE flag? Can I change the make line to get the results I am looking for? Thanks
[toc] | [next] | [standalone]
| From | Tauno Voipio <tauno.voipio@notused.fi.invalid> |
|---|---|
| Date | 2014-06-06 08:47 +0300 |
| Message-ID | <lmrkkv$ujr$1@dont-email.me> |
| In reply to | #11188 |
On 5.6.14 23:47, Baho Utot wrote: > I would like to have gcc output like the following > (excerpt from bzip2 compile) > > gcc -fpic -fPIC -Wall -Winline -march=x86-64 -mtune=generic -O2 -pipe - > fno-strict-aliasing -g -D_FILE_OFFSET_BITS=64 -c blocksort.c > gcc -fpic -fPIC -Wall -Winline -march=x86-64 -mtune=generic -O2 -pipe - > fno-strict-aliasing -g -D_FILE_OFFSET_BITS=64 -c huffman.c > gcc -fpic -fPIC -Wall -Winline -march=x86-64 -mtune=generic -O2 -pipe - > fno-strict-aliasing -g -D_FILE_OFFSET_BITS=64 -c crctable.c > gcc -fpic -fPIC -Wall -Winline -march=x86-64 -mtune=generic -O2 -pipe - > fno-strict-aliasing -g -D_FILE_OFFSET_BITS=64 -c randtable.c > gcc -fpic -fPIC -Wall -Winline -march=x86-64 -mtune=generic -O2 -pipe - > fno-strict-aliasing -g -D_FILE_OFFSET_BITS=64 -c compress.c > gcc -fpic -fPIC -Wall -Winline -march=x86-64 -mtune=generic -O2 -pipe - > fno-strict-aliasing -g -D_FILE_OFFSET_BITS=64 -c decompress.c > gcc -fpic -fPIC -Wall -Winline -march=x86-64 -mtune=generic -O2 -pipe - > fno-strict-aliasing -g -D_FILE_OFFSET_BITS=64 -c bzlib.c > > 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 > > Why does some packages not obey the VERBOSE flag? > > Can I change the make line to get the results I am looking for? > > Thanks > Did you read the Makefile? The solution is in the Makefile, refer to the Make manual. -- Tauno Voipio
[toc] | [prev] | [next] | [standalone]
| From | Baho Utot <baho-utot@invalid.com> |
|---|---|
| Date | 2014-06-06 07:03 -0400 |
| Message-ID | <3oj86b-otp.ln1@raspberrypi.bildanet.com> |
| In reply to | #11192 |
Tauno Voipio wrote: > On 5.6.14 23:47, Baho Utot wrote: >> I would like to have gcc output like the following >> (excerpt from bzip2 compile) >> >> gcc -fpic -fPIC -Wall -Winline -march=x86-64 -mtune=generic -O2 -pipe >> - fno-strict-aliasing -g -D_FILE_OFFSET_BITS=64 -c blocksort.c >> gcc -fpic -fPIC -Wall -Winline -march=x86-64 -mtune=generic -O2 -pipe >> - fno-strict-aliasing -g -D_FILE_OFFSET_BITS=64 -c huffman.c >> gcc -fpic -fPIC -Wall -Winline -march=x86-64 -mtune=generic -O2 -pipe >> - fno-strict-aliasing -g -D_FILE_OFFSET_BITS=64 -c crctable.c >> gcc -fpic -fPIC -Wall -Winline -march=x86-64 -mtune=generic -O2 -pipe >> - fno-strict-aliasing -g -D_FILE_OFFSET_BITS=64 -c randtable.c >> gcc -fpic -fPIC -Wall -Winline -march=x86-64 -mtune=generic -O2 -pipe >> - fno-strict-aliasing -g -D_FILE_OFFSET_BITS=64 -c compress.c >> gcc -fpic -fPIC -Wall -Winline -march=x86-64 -mtune=generic -O2 -pipe >> - fno-strict-aliasing -g -D_FILE_OFFSET_BITS=64 -c decompress.c >> gcc -fpic -fPIC -Wall -Winline -march=x86-64 -mtune=generic -O2 -pipe >> - fno-strict-aliasing -g -D_FILE_OFFSET_BITS=64 -c bzlib.c >> >> 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 >> >> Why does some packages not obey the VERBOSE flag? >> >> Can I change the make line to get the results I am looking for? >> >> Thanks >> > > 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.
[toc] | [prev] | [next] | [standalone]
| From | Robert Heller <heller@deepsoft.com> |
|---|---|
| Date | 2014-06-06 08:25 -0500 |
| Message-ID | <a7idndvpBcvNXAzOnZ2dnUVZ_vadnZ2d@giganews.com> |
| In reply to | #11193 |
At Fri, 06 Jun 2014 07:03:03 -0400 Baho Utot <baho-utot@invalid.com> wrote:
>
> Tauno Voipio wrote:
>
> > On 5.6.14 23:47, Baho Utot wrote:
> >> I would like to have gcc output like the following
> >> (excerpt from bzip2 compile)
> >>
> >> gcc -fpic -fPIC -Wall -Winline -march=x86-64 -mtune=generic -O2 -pipe
> >> - fno-strict-aliasing -g -D_FILE_OFFSET_BITS=64 -c blocksort.c
> >> gcc -fpic -fPIC -Wall -Winline -march=x86-64 -mtune=generic -O2 -pipe
> >> - fno-strict-aliasing -g -D_FILE_OFFSET_BITS=64 -c huffman.c
> >> gcc -fpic -fPIC -Wall -Winline -march=x86-64 -mtune=generic -O2 -pipe
> >> - fno-strict-aliasing -g -D_FILE_OFFSET_BITS=64 -c crctable.c
> >> gcc -fpic -fPIC -Wall -Winline -march=x86-64 -mtune=generic -O2 -pipe
> >> - fno-strict-aliasing -g -D_FILE_OFFSET_BITS=64 -c randtable.c
> >> gcc -fpic -fPIC -Wall -Winline -march=x86-64 -mtune=generic -O2 -pipe
> >> - fno-strict-aliasing -g -D_FILE_OFFSET_BITS=64 -c compress.c
> >> gcc -fpic -fPIC -Wall -Winline -march=x86-64 -mtune=generic -O2 -pipe
> >> - fno-strict-aliasing -g -D_FILE_OFFSET_BITS=64 -c decompress.c
> >> gcc -fpic -fPIC -Wall -Winline -march=x86-64 -mtune=generic -O2 -pipe
> >> - fno-strict-aliasing -g -D_FILE_OFFSET_BITS=64 -c bzlib.c
> >>
> >> 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
> >>
> >> Why does some packages not obey the VERBOSE flag?
> >>
> >> Can I change the make line to get the results I am looking for?
> >>
> >> Thanks
> >>
> >
> > 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.
>
>
>
--
Robert Heller -- 978-544-6933 / heller@deepsoft.com
Deepwoods Software -- http://www.deepsoft.com/
() ascii ribbon campaign -- against html e-mail
/\ www.asciiribbon.org -- against proprietary attachments
[toc] | [prev] | [next] | [standalone]
| From | Baho Utot <baho-utot@invalid.com> |
|---|---|
| Date | 2014-06-06 11:06 -0400 |
| Message-ID | <t0296b-8bq.ln1@raspberrypi.bildanet.com> |
| In reply to | #11195 |
Robert Heller wrote: > At Fri, 06 Jun 2014 07:03:03 -0400 Baho Utot <baho-utot@invalid.com> > wrote: > >> >> Tauno Voipio wrote: >> >> > On 5.6.14 23:47, Baho Utot wrote: >> >> I would like to have gcc output like the following >> >> (excerpt from bzip2 compile) >> >> >> >> gcc -fpic -fPIC -Wall -Winline -march=x86-64 -mtune=generic -O2 >> >> -pipe - fno-strict-aliasing -g -D_FILE_OFFSET_BITS=64 -c >> >> blocksort.c gcc -fpic -fPIC -Wall -Winline -march=x86-64 >> >> -mtune=generic -O2 -pipe - fno-strict-aliasing -g >> >> -D_FILE_OFFSET_BITS=64 -c huffman.c gcc -fpic -fPIC -Wall -Winline >> >> -march=x86-64 -mtune=generic -O2 -pipe - fno-strict-aliasing -g >> >> -D_FILE_OFFSET_BITS=64 -c crctable.c gcc -fpic -fPIC -Wall >> >> -Winline -march=x86-64 -mtune=generic -O2 -pipe - >> >> fno-strict-aliasing -g -D_FILE_OFFSET_BITS=64 -c randtable.c gcc >> >> -fpic -fPIC -Wall -Winline -march=x86-64 -mtune=generic -O2 -pipe >> >> - fno-strict-aliasing -g -D_FILE_OFFSET_BITS=64 -c compress.c gcc >> >> -fpic -fPIC -Wall -Winline -march=x86-64 -mtune=generic -O2 -pipe >> >> - fno-strict-aliasing -g -D_FILE_OFFSET_BITS=64 -c decompress.c >> >> gcc -fpic -fPIC -Wall -Winline -march=x86-64 -mtune=generic -O2 >> >> -pipe - fno-strict-aliasing -g -D_FILE_OFFSET_BITS=64 -c bzlib.c >> >> >> >> 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 >> >> >> >> Why does some packages not obey the VERBOSE flag? >> >> >> >> Can I change the make line to get the results I am looking for? >> >> >> >> Thanks >> >> >> > >> > 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. > >> >> >> > Not always, some are generated by hand for example sysklogd, sysvinit and bzip2
[toc] | [prev] | [next] | [standalone]
| From | Richard Kettlewell <rjk@greenend.org.uk> |
|---|---|
| Date | 2014-06-06 18:14 +0100 |
| Message-ID | <wwv4mzyot8y.fsf@l1AntVDjLrnP7Td3DQJ8ynzIq3lJMueXf87AxnpFoA.invalid> |
| In reply to | #11195 |
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. >>>> 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. -- http://www.greenend.org.uk/rjk/
[toc] | [prev] | [next] | [standalone]
| From | Baho Utot <baho-utot@invalid.com> |
|---|---|
| Date | 2014-06-06 16:16 -0400 |
| Message-ID | <g6k96b-3rq.ln1@raspberrypi.bildanet.com> |
| In reply to | #11200 |
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.
[toc] | [prev] | [next] | [standalone]
| From | Tauno Voipio <tauno.voipio@notused.fi.invalid> |
|---|---|
| Date | 2014-06-06 23:15 +0300 |
| Message-ID | <lmt7h3$i0b$1@dont-email.me> |
| In reply to | #11200 |
On 6.6.14 20:14, 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. > >>>>> 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. > The OP did not say a word about what he was compiling, or that the Makefile was generated using autotools. The only tool he mentioned was make, so I did not enter a guessing game. -- -TV
[toc] | [prev] | [next] | [standalone]
| From | Richard Kettlewell <rjk@greenend.org.uk> |
|---|---|
| Date | 2014-06-07 09:39 +0100 |
| Message-ID | <wwvy4x9nmfm.fsf@l1AntVDjLrnP7Td3DQJ8ynzIq3lJMueXf87AxnpFoA.invalid> |
| In reply to | #11209 |
Tauno Voipio <tauno.voipio@notused.fi.invalid> writes: > The OP did not say a word about what he was compiling, or that the > Makefile was generated using autotools. The only tool he mentioned > was make, so I did not enter a guessing game. They specifically mentioned Bison. -- http://www.greenend.org.uk/rjk/
[toc] | [prev] | [standalone]
Back to top | Article view | comp.os.linux.misc
csiph-web