Bug#439701: marked as done (linux86: FTBFS: elks.c:18:22: error: sys/vm86.h: No such file or directory)
Your message dated Sun, 26 Aug 2007 19:29:54 +0200 with message-id [EMAIL PROTECTED] and subject line Bug#439701: Acknowledgement (linux86: FTBFS: elks.c:18:22: error: sys/vm86.h: No such file or directory) has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) ---BeginMessage--- Package: linux86 Version: 0.16.17-1 Severity: serious Hi, Your package is failing to build on amd64 with the following error: cc -O -c -o elks.o elks.c elks.c:18:22: error: sys/vm86.h: No such file or directory elks.c: In function 'elks_init': elks.c:37: error: invalid use of undefined type 'struct vm86_struct' elks.c:38: error: invalid use of undefined type 'struct vm86_struct' elks.c:38: error: 'CPU_286' undeclared (first use in this function) [...] The amd64 kernel does not support the vm86() system call. Previous versions didn't build elksemu on amd64. Kurt ---End Message--- ---BeginMessage--- Version: 0.16.17-2 Looks like this was already fixed. Kurt ---End Message---
Bug#439701: marked as done (linux86: FTBFS: elks.c:18:22: error: sys/vm86.h: No such file or directory)
On 8/26/07, Debian Bug Tracking System [EMAIL PROTECTED] wrote: Your package is failing to build on amd64 with the following error: cc -O -c -o elks.o elks.c elks.c:18:22: error: sys/vm86.h: No such file or directory I know, I know. Sorry for that. Version 0.16.17-2 was uploaded shortly after that, when I realized it, and this issue has already been fixed. Thanks for your support, Juan Cespedes -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
