Patches item #311742, was opened at 2009-06-09 14:59 by Barry deFreese You can respond by visiting: https://alioth.debian.org/tracker/?func=detail&atid=410472&aid=311742&group_id=30628
Status: Open Priority: 3 Submitted By: Barry deFreese (bdefreese) Assigned to: Nobody (None) Summary: FTBFS scheme2c 1993.3.15.2-4 Category: linuxism Group: unreviewed Resolution: None Initial Comment: By using the following change to debian/rules I can get it to build further: arch := $(shell dpkg-architecture -qDEB_BUILD_ARCH) ifeq ($(arch),amd64) S2C_ARCH = AMD64 else ifeq ($(arch),i386) S2C_ARCH = LINUX +else ifeq ($(arch),hurd-i386) + S2C_ARCH = LINUX else $(warning Warning: unsupported architecture $(arch)) S2C_ARCH = UNSUPPORTED endif However, it fails with the following: gcc -c -m32 -O2 -march=i386 -I. cio.c cio.c:87:2: error: #error "Stack overflow is enabled for this architecture but you are either missing libsigsegv or do not have stack overflow and sigsegv recovery built in" cio.c: In function 'sc_segv__handlers': cio.c:842: error: 'stackoverflow_handler' undeclared (first use in this function) cio.c:842: error: (Each undeclared identifier is reported only once cio.c:842: error: for each function it appears in.) cio.c:843: error: 'overflow_stack' undeclared (first use in this function) cio.c:846: error: 'sigsegv_handler' undeclared (first use in this function) make[3]: *** [cio.o] Error 1 make[3]: Leaving directory `/devel/bdefreese/scheme2c/scheme2c-1993.3.15.2/LINUX/scrt' make[2]: *** [port] Error 2 make[2]: Leaving directory `/devel/bdefreese/scheme2c/scheme2c-1993.3.15.2/LINUX/scrt' make[1]: *** [port] Error 2 make[1]: Leaving directory `/devel/bdefreese/scheme2c/scheme2c-1993.3.15.2/LINUX' make: *** [build-arch-stamp] Error 2 dpkg-buildpackage: error: debian/rules build gave error exit status 2 Barry ---------------------------------------------------------------------- You can respond by visiting: https://alioth.debian.org/tracker/?func=detail&atid=410472&aid=311742&group_id=30628 -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
