Following the removal of eglibc support, this commit replaces all
occurences of "(e)glibc" by just "glibc". Most of the occurences are in
package Config.in comments.
In addition, when the form "an (e)glibc ..." was used, it is replaced by
"a glibc ...".
[Peter: add new efi* packages, s/uclibc/uClibc as suggested by Romain,
systemd / liquid-dsp tweaks as suggested by Yann]
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Reviewed-by: Romain Naour <romain.naour@gmail.com>
Acked-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
As pointed out by Arnout, racehound does not require kernel headers
3.14-or-later. So, drop this depenency.
It stills require a kernel >= 3.14 to build and run, but we really
have no way to express that dependency as Kconfig options.
Besides, racehound does not build with kernel 4.5 because the struct
modules has been updated. Bump racehound to fix that build failure.
Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
Cc: Arnout Vandecappelle <arnout@mind.be>
Cc: Peter Korsgaard <peter@korsgaard.com>
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
racehound requires a kernel >= 3.14 to be built and to run.
However, the current conditions on the corresponding comments are wrong:
- the comment about the kernel has a dependency on the requested
headers
- the comment on the toolchain features does not have this condition.
Thus, the comments are not shown/hidden under the appropriate
conditions, like in this situation:
- toolchain with headers < 3.14 (e.g. Sourcery CodeBench x86/x86_64
2012.09 with headers 3.5)
- kernel 4.5 enabled
this comment is shown:
racehound needs an Linux kernel >= 3.14 to be built
So, this is incorrect, because:
1- a kernel >= 3.14 is indeed to be built
2- the headers version mismatch is not reported
Fix that by moving the dependency on the kernel headers to the
appropriate comment and enhance it.
Since there is no way we can know the kernel version to be built, we can
not add such a condition; still, we leave the kernel message as-is.
Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
And reorder 'select' after 'depends'
Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
As Thomas puts it:
The comment can only be visible when a toolchain that is *not*
uclibc and *not* glibc is used. I.e, the comment is now only visible
when musl is used. Which is not what we want.
Indeed, I completely borked the conditions. When a glibc or uClibc
toolchain is selected, the comment is entirely hidden, and we don;t get
the extra requirements (wchar, !static).
Fix that with the solution proposed by Thomas.
Reported-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
- check for linux kernel >= 3.14
- add cross compile enviornment for linux kernel compile
- add additional kernel config hint (CONFIG_KALLSYMS_ALL)
- fix kernel module install path
[Thomas:
- fix Config.in dependency logic for the comment on the kernel
version, as noticed by Baruch.
- minor improvements in the .mk file.]
Signed-off-by: Peter Seiderer <ps.report@gmx.net>
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
[Thomas:
- indicate in the Config.in help text that CONFIG_KPROBES
- add missing final double quote in one of the Config.in comment
- normalize the Config.in comment dependencies
- bump to the latest Git version.]
Signed-off-by: Peter Seiderer <ps.report@gmx.net>
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
