Your message dated Thu, 31 Aug 2006 00:09:38 +0200
with message-id <[EMAIL PROTECTED]>
and subject line ocp: FTBFS: kickload.c:203: error: 'struct sigcontext' has no
member named 'eax'
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)
--- Begin Message ---
Package: ocp
Version: 0.1.10rc6-2
Severity: serious
Justification: no longer builds from source
Hello,
There was a problem while autobuilding your package:
> Automatic build of ocp_0.1.10rc6-2 on saturne by sbuild/amd64 85
> Build started at 20060829-1009
> ******************************************************************************
[...]
> /usr/bin/make
> make[1]: Entering directory `/build/buildd/ocp-0.1.10rc6'
> /usr/bin/make -C binfile TOPDIR=.././
> make[2]: Entering directory `/build/buildd/ocp-0.1.10rc6/binfile'
> x86_64-linux-gnu-gcc -Wall -g -fPIC -O2 -fPIC -Wall -I.././ binfpak.c -c -o
> binfpak.o
> make[2]: Leaving directory `/build/buildd/ocp-0.1.10rc6/binfile'
> /usr/bin/make -C boot TOPDIR=.././
> make[2]: Entering directory `/build/buildd/ocp-0.1.10rc6/boot'
> x86_64-linux-gnu-gcc -Wall -g -fPIC -O2 -fPIC -Wall -I.././ kickload.c -o
> kickload.o -c
> kickload.c: In function 'dumpcontext':
> kickload.c:203: error: 'struct sigcontext' has no member named 'eax'
> kickload.c:203: error: 'struct sigcontext' has no member named 'ebx'
> kickload.c:203: error: 'struct sigcontext' has no member named 'ecx'
> kickload.c:203: error: 'struct sigcontext' has no member named 'edx'
> kickload.c:204: error: 'struct sigcontext' has no member named 'ds'
> kickload.c:204: error: 'struct sigcontext' has no member named 'es'
> kickload.c:204: error: 'struct sigcontext' has no member named 'ss'
> kickload.c:205: error: 'struct sigcontext' has no member named 'edi'
> kickload.c:205: error: 'struct sigcontext' has no member named 'esi'
> kickload.c:205: error: 'struct sigcontext' has no member named 'ebp'
> kickload.c:205: error: 'struct sigcontext' has no member named 'esp_at_signal'
> kickload.c:206: error: 'struct sigcontext' has no member named 'eip'
> make[2]: *** [kickload.o] Error 1
> make[2]: Leaving directory `/build/buildd/ocp-0.1.10rc6/boot'
> make[1]: *** [dirs] Error 2
> make[1]: Leaving directory `/build/buildd/ocp-0.1.10rc6'
> make: *** [build-stamp] Error 2
> ******************************************************************************
> Build finished at 20060829-1010
> FAILED [dpkg-buildpackage died]
--
Florent
pgphkc59DE1DU.pgp
Description: PGP signature
--- End Message ---
--- Begin Message ---
Hello
Please can you remove ia64 and amd64 from the following line:
%ocp: i386 ia64 amd64 hurd-i386 freebsd-i386 netbsd-i386
# i386 specific assembler in program (needs porting)
The upstream and me don't have access to intel/amd compatible 64bit
systems, thus
can't test building/working. I would have liked to see if it builds
using buildd.d.o.
Upstream is working on this actively, and it's just a matter of time.
It
already works for GNU/kFreebsd (audio and Audio CD)...
Yours,
Guerkan
--- End Message ---
