j'ai des petits problemes pour compiler des logiciels.
Je me rends compte que ces problemes proviennent des headers linux
/usr/include/linux -> /usr/src/linux/include/linux
Mais je lis pas mal de choses sur linux-libc-headers, mais qui n'a plus
l'air d'être maintenu.
Questions:
faut il garder le lien symbolique /usr/include/linux (et le lien
/usr/include/asm) ?
quelle est cette histoire de header 'fixes' ?
Comment retrouver un moyen de compiler tout ca (qemu-0.8.2 en
l'occurence) ?
La version du noyau peut elle jouer?
je suis en 2.6.13 ou 2.6.16 et mes headers sont ceux du 2.6.16
Merci pour toute explication
--
Pour contacter l'équipe de modération : moderateurs-fcolm@efrei.fr
ATTENTION: Postez DIRECTEMENT vos articles dans le groupe, PAS dans
la liste de distribution des modérateurs.
Cette action est irreversible, confirmez la suppression du commentaire ?
Signaler le commentaire
Veuillez sélectionner un problème
Nudité
Violence
Harcèlement
Fraude
Vente illégale
Discours haineux
Terrorisme
Autre
Alain
Bonjour,
Peut être un début de réponse sur le site : www.linuxfromscratch.org
8<-------- Some kernel documentation recommends creating a symlink from /usr/src/linux pointing to the kernel source directory. This is specific to kernels prior to the 2.6 series and must not be created on an LFS system as it can cause problems for packages you may wish to build once your base LFS system is complete. Also, the headers in the system's include directory should always be the ones against which Glibc was compiled, that is, the ones from the Linux-Libc-Headers package, and therefore, should never be replaced by the kernel headers. 8<-------
Et pour finir, un petit commentaire de Linus Torvalds :
8<---- I would suggest that people who compile new kernels should:
- not have a single symbolic link in sight (except the one that the kernel build itself sets up, namely the ?linux/include/asm? symlink that is only used for the internal kernel compile itself)
And yes, this is what I do. My /usr/src/linux still has the old 2.2.13 header files, even though I haven't run a 2.2.13 kernel in a _loong_ time. But those headers were what Glibc was compiled against, so those headers are what matches the library object files.
And this is actually what has been the suggested environment for at least the last five years. I don't know why the symlink business keeps on living on, like a bad zombie. Pretty much every distribution still has that broken symlink, and people still remember that the linux sources should go into ?/usr/src/linux? even though that hasn't been true in a _loong_ time. 8<----
En clair, il faut garder les headers qui ont servis à compiler la glibc du système. C'est ce que je fais toujours, je n'ai jamais eu de pb.
Alain
-- Pour contacter l'équipe de modération : ATTENTION: Postez DIRECTEMENT vos articles dans le groupe, PAS dans la liste de distribution des modérateurs.
Bonjour,
Peut être un début de réponse sur le site :
www.linuxfromscratch.org
8<--------
Some kernel documentation recommends creating a symlink from /usr/src/linux
pointing to the kernel source directory. This is specific to kernels prior
to the 2.6 series and must not be created on an LFS system as it can cause
problems for packages you may wish to build once your base LFS system is
complete.
Also, the headers in the system's include directory should always be the
ones against which Glibc was compiled, that is, the ones from the
Linux-Libc-Headers package, and therefore, should never be replaced by the
kernel headers.
8<-------
Et pour finir, un petit commentaire de Linus Torvalds :
8<----
I would suggest that people who compile new kernels should:
- not have a single symbolic link in sight (except the one that the
kernel build itself sets up, namely the ?linux/include/asm?
symlink that is only used for the internal kernel compile itself)
And yes, this is what I do. My /usr/src/linux still has the old 2.2.13
header files, even though I haven't run a 2.2.13 kernel in a _loong_
time. But those headers were what Glibc was compiled against, so those
headers are what matches the library object files.
And this is actually what has been the suggested environment for at
least the last five years. I don't know why the symlink business keeps
on living on, like a bad zombie. Pretty much every distribution still
has that broken symlink, and people still remember that the linux
sources should go into ?/usr/src/linux? even though that hasn't
been true in a _loong_ time.
8<----
En clair, il faut garder les headers qui ont servis à compiler la glibc du
système. C'est ce que je fais toujours, je n'ai jamais eu de pb.
Alain
--
Pour contacter l'équipe de modération : moderateurs-fcolm@efrei.fr
ATTENTION: Postez DIRECTEMENT vos articles dans le groupe, PAS dans
la liste de distribution des modérateurs.
Peut être un début de réponse sur le site : www.linuxfromscratch.org
8<-------- Some kernel documentation recommends creating a symlink from /usr/src/linux pointing to the kernel source directory. This is specific to kernels prior to the 2.6 series and must not be created on an LFS system as it can cause problems for packages you may wish to build once your base LFS system is complete. Also, the headers in the system's include directory should always be the ones against which Glibc was compiled, that is, the ones from the Linux-Libc-Headers package, and therefore, should never be replaced by the kernel headers. 8<-------
Et pour finir, un petit commentaire de Linus Torvalds :
8<---- I would suggest that people who compile new kernels should:
- not have a single symbolic link in sight (except the one that the kernel build itself sets up, namely the ?linux/include/asm? symlink that is only used for the internal kernel compile itself)
And yes, this is what I do. My /usr/src/linux still has the old 2.2.13 header files, even though I haven't run a 2.2.13 kernel in a _loong_ time. But those headers were what Glibc was compiled against, so those headers are what matches the library object files.
And this is actually what has been the suggested environment for at least the last five years. I don't know why the symlink business keeps on living on, like a bad zombie. Pretty much every distribution still has that broken symlink, and people still remember that the linux sources should go into ?/usr/src/linux? even though that hasn't been true in a _loong_ time. 8<----
En clair, il faut garder les headers qui ont servis à compiler la glibc du système. C'est ce que je fais toujours, je n'ai jamais eu de pb.
Alain
-- Pour contacter l'équipe de modération : ATTENTION: Postez DIRECTEMENT vos articles dans le groupe, PAS dans la liste de distribution des modérateurs.
