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

Groups > linux.kernel > #1461301

feature detection versus feature selection

Show all headers | View raw

Hey guys,

	Now we have this output when building tools with the feature
detection mechanisms in tools/build/:

Auto-detecting system features:
...                         dwarf: [ on  ]
...            dwarf_getlocations: [ OFF ]
...                         glibc: [ on  ]
...                          gtk2: [ on  ]
...                      libaudit: [ on  ]
...                        libbfd: [ on  ]
...                        libelf: [ on  ]
...                       libnuma: [ on  ]
...        numa_num_possible_cpus: [ OFF ]
...                       libperl: [ on  ]
...                     libpython: [ on  ]
...                      libslang: [ on  ]
...                     libcrypto: [ on  ]
...                     libunwind: [ on  ]
...            libdw-dwarf-unwind: [ OFF ]
...                          zlib: [ on  ]
...                          lzma: [ on  ]
...                     get_cpuid: [ on  ]
...                           bpf: [ on  ]


	What I miss is a way to have another column that would state if
the user had used, say, NO_LIBELF to disable libelf...

	Jiri, is there already some file where we have the list of
manually disabled features? Or do you have something like that in mind?
.config files?

- Arnaldo

Back to linux.kernel | Previous | Next — Next in thread | Find similar | Unroll thread

Thread

feature detection versus feature selection Arnaldo Carvalho de Melo <acme@kernel.org> - 2016-08-12 18:20 +0200
  Re: feature detection versus feature selection Jiri Olsa <jolsa@redhat.com> - 2016-08-14 13:20 +0200

csiph-web