Bug#223460: [dannf@debian.org: reopening]
Is this bug alive? Moreover, is this really linux-kernel-headers bug?
The latest modutils on ia64 is existed, so it can be closed, I think.
At Sat, 3 Jan 2004 13:36:47 -0500,
Daniel Jacobowitz wrote:
> On Tue, Dec 09, 2003 at 09:09:51AM -0700, dann frazier wrote:
> > Package: linux-kernel-headers
> > Version: 2.5.999-test7-bk-9
> > Severity: important
> >
> > oops - tried to reopen an archived bug.
> > opening a new one instead. see #218645 for the original report.
> >
> > ----- Forwarded message from dann frazier <dannf@debian.org> -----
> >
> > From: dann frazier <dannf@debian.org>
> > To: 218645@bugs.debian.org
> > Subject: reopening
> >
> > this bug exists in unstable - dunno if its a regression or if it wasn't
> > fixed the first time.
> >
> > ...
> > gcc -O2 -Wall -I../../../util/../include -D_GNU_SOURCE -DCONFIG_ROOT_CHECK_OFF=0 -DELF_MACHINE_H='"elf_ia64.h"' -DARCH_ia64 -c -o arch64.o ../../../util/arch64.c
> > In file included from ../../../util/arch64.c:24:
> > ../../../include/util.h:42: warning: built-in function `log' declared as non-function
> > gcc -O2 -Wall -I../../../util/../include -D_GNU_SOURCE -DCONFIG_ROOT_CHECK_OFF=0 -DELF_MACHINE_H='"elf_ia64.h"' -DARCH_ia64 -c -o gzfiles.o ../../../util/gzfiles.c
> > gcc -O2 -Wall -I../../../util/../include -D_GNU_SOURCE -DCONFIG_ROOT_CHECK_OFF=0 -DELF_MACHINE_H='"elf_ia64.h"' -DARCH_ia64 -c -o sys_nim.o ../../../util/sys_nim.c
> > gcc -O2 -Wall -I../../../util/../include -D_GNU_SOURCE -DCONFIG_ROOT_CHECK_OFF=0 -DELF_MACHINE_H='"elf_ia64.h"' -DARCH_ia64 -c -o sys_oim.o ../../../util/sys_oim.c
> > ../../../util/sys_oim.c:36: error: parse error before "old_sys_init_module"
> > make[2]: *** [sys_oim.o] Error 1
> > make[2]: Leaving directory `/tmp/modutils-2.4.25/debian/build/util'
> > make[1]: *** [all] Error 2
> > make[1]: Leaving directory `/tmp/modutils-2.4.25/debian/build'
> > make: *** [stamp-build] Error 2
>
> This isn't the same bug. Why is COMPAT_2_0 getting set? IA64 headers
> have never supported using _syscall5, so I'm guessing this is a bug in
> modutils.
Regards,
-- gotom
Reply to: