| Re: [proaudio] [929] Fixed external kernel modules build with rt-sources-2.6.23-r1 |
[ Thread Index |
Date Index
| More lists.tuxfamily.org/proaudio Archives
]
- To: proaudio@xxxxxxxxxxxxxxxxxxx
- Subject: Re: [proaudio] [929] Fixed external kernel modules build with rt-sources-2.6.23-r1
- From: Dominique Michel <dominique.michel@xxxxxxxxxxxx>
- Date: Thu, 18 Oct 2007 20:40:44 +0200
- Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAJFBMVEXy8ubtkoXo7+b1+fbN cGKCeWDtamweFA8eMkmKPkPtvcWRoqyV0Pn7AAACbElEQVQ4jXXTMWvbQBQA4MOlizsdXEXp KAi09mKcLZ0EJxONDRJVkikg9AtqTm63gtHDmVJs1GsnC0JiaTMJGN2f67uzznJb+gZj9PFO 7717IqdtvCAmem4bxMLp/2BEyEBF1+U/0H8uhI6rv+BVLNrY/gH9T0L8yAxk2yMY3YuZxDCn TY/gpBByyTGktIcZOIvFjPNJmqYJDwrx3cIoBrE0zzG4FF8tfBAwM+DonKCYWjgROZ6Upjcm 5Qje58JAmlKKGfIAjzaDUuogZBY2Bjg14eDbywMIqZvwqgqFBcVFB0seYONLb00ZZlh4p0F6 FHNoUMyKAzxowJSQTyj+XloYs3MN3GeMpzyYSTMshLM00ODpWlPp4SDbqs4cViDcGAgmlK/a PsaOg7DvIQ3wzANMqB/iQW/XTkoTLO6XhSeHUoQKe+NLjyY/Ldx7CW2D4WTYhZ3V0GP64RpP Q/E66IUWMLj3+nDn4w2ejMACyXFeHZy6ETcZehc49bv1GQ/0bazNuzm97mDkhnoie9i30WYM w/YCnYT7Fx308s98n0IT//Jod1+aOzdzYXLVbftol+PC+REG3u+0AxdEtuSMB6G+DLGwMH4E vXGmJn8VCLM9LhmrOAMQYt5Wi/DFgIC52iFkUzMpDVmjAaDZRGC+JGwDqzJ/G5fUUcWZAaE7 YfvPLYtIU1Wb4A2IeS7uDMgcIFutiCr766qGfKHyuxvTIERKXVNSN27lDgCuBuojlpxIyJV6 ritS1uWWuHF2Ww7qcIKbqEFVNbmtmm3vGSCHbVXjikrY3SpVxwQWw2aIjwG+ueXTJDmHeK6a HfwGyU5ZSlGeSRQAAAAASUVORK5CYII=
Le Wed, 17 Oct 2007 22:57:59 +0200,
Thomas Kuther <gimpel@xxxxxxxxxxxxxxxx> a écrit :
> On Mi, 17.10.07 13:49 "Mark Knecht" <markknecht@xxxxxxxxx> wrote:
>
> > After reflecting on this I suspect that the reason it worked for me is
> > that I currently don't build any external modules anymore. I dropped
> > the ATI drivers and everything else I use is part of the kernel these
> > days.
> >
> > Or possibly because I'm AMD64 and somehow that's different.
>
> It isn't. The issue is also on amd64
>
> > Is there any reason for me to try the fixes you did or can I just
> > take it easy?
> >
> > - Mark
> >
>
This will affect any kernel external modules (alsa, nvidia, wmware, fuse,....).
If you are sure that you don't want to build such external modules, you can just
ignore this issue.
FEATURES="-sandbox -usersandbox" emerge <ebuild>
is another workaround (usersandbox is also affected) when merging external
modules. But it is better to fix that in the kernel build system like this
patch is doing or with the ~arch sandbox (the real fix).
All this has to do with a new feature of gcc that make possible to write into
existent files. In this case in the kernel tree. Read the bug report for the
details. http://bugs.gentoo.org/show_bug.cgi?id=135745
> You can ignore it then I guess. It's more like hacking the kernel to
> work around bugs elsewhere (sandbox in this case)
>
> But dominique is right, making the kernel depend on a ~arch masked
> sandbox version is also not the right way..
>