Bug#334917: klibc_1.1.1-2(m68k/unstable/vault13): FTBFS on m68k

2006-04-19 Thread maximilian attems
On Thu, 20 Oct 2005, Stephen R Marenka wrote:

> klibc fails to build from source on m68k.
> 
> Here are selected excerpts from the buildd log.

snipp from 1.2.2-1 release:
  * Add m68k-syscall.patch thanks to Kyle McMartin <[EMAIL PROTECTED]>.
Still needs setjmp/longjmp, crt0, and sysstub.ph to be usefull.

so there are still missing parts for m68k porters to jump in.
as m68k linux-2.6 uses build-in ide, i guess klibc is not a current priority.
please note that klibc is on the way to be merged in linux-2.6.18.

regards
 
-- 
maks


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Bug#334917: klibc_1.1.1-2(m68k/unstable/vault13): FTBFS on m68k

2005-10-20 Thread Stephen R Marenka
Package: klibc
Version: 1.1.1-2
Severity: important


klibc fails to build from source on m68k.

Here are selected excerpts from the buildd log.


| Automatic build of klibc_1.1.1-2 on amiga1200.jt7336.tky.hut.fi by 
sbuild/m68k 69
| Build started at 20051020-2053
| **

 [...]

| ** Using build dependencies supplied by package:
| Build-Depends: cdbs, debhelper (>= 4.0.0), linux-headers-2.6.12-1, bison, flex

 [...]

| Checking correctness of source dependencies...
| Toolchain package versions: libc6-dev_2.3.5-6 
linux-kernel-headers_2.6.13+0rc3-2 gcc-4.0_4.0.2-2 g++-4.0_4.0.2-2 
binutils_2.16.1-2 libstdc++6-4.0-dev_4.0.2-2 libstdc++6_4.0.2-2

 [...]

| gcc -Wp,-MT,siglongjmp.o,-MD,./.siglongjmp.o.d -Os -fomit-frame-pointer  
-D__KLIBC__=1 -D__KLIBC_MINOR__=1 -nostdlib -nostdinc -iwithprefix include 
-I../include/arch/m68k -I../include/bits32 -I../include -I../linux/include 
-I../linux/include2 -I../linux/include -I./zlib -I./zlib -DWITH_ERRLIST -W 
-Wall -Wpointer-arith -Wwrite-strings -Wstrict-prototypes -Winline 
-DDYNAMIC_CRC_TABLE -c -o siglongjmp.o siglongjmp.c
| In file included from siglongjmp.c:8:
| ../include/setjmp.h:13:30: error: klibc/archsetjmp.h: No such file or 
directory
| In file included from siglongjmp.c:8:
| ../include/setjmp.h:15: warning: parameter names (without types) in function 
declaration
| ../include/setjmp.h:16: error: syntax error before 'int'
| ../include/setjmp.h:16: warning: function declaration isn't a prototype
| ../include/setjmp.h:28: error: syntax error before 'jmp_buf'
| ../include/setjmp.h:28: warning: no semicolon at end of struct or union
| ../include/setjmp.h:30: error: syntax error before '}' token
| ../include/setjmp.h:32: error: array type has incomplete element type
| ../include/setjmp.h:41: warning: type defaults to 'int' in declaration of 
'type name'
| siglongjmp.c:11: warning: type defaults to 'int' in declaration of 'buf'
| siglongjmp.c: In function 'siglongjmp':
| siglongjmp.c:13: error: invalid type argument of '->'
| siglongjmp.c:14: error: invalid type argument of '->'
| make[2]: *** [siglongjmp.o] Error 1
| make[2]: Leaving directory `/build/buildd/klibc-1.1.1/klibc'
| make[1]: *** [all] Error 2
| make[1]: Leaving directory `/build/buildd/klibc-1.1.1'
| make: *** [debian/stamp-makefile-build] Error 2
| **
| Build finished at 20051020-2106
| FAILED [dpkg-buildpackage died]


A full buildd log is available at 


Other buildd logs may be available at 


--
Stephen R. Marenka If life's not fun, you're not doing it right!
<[EMAIL PROTECTED]>


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Bug#334917: klibc_1.1.1-2(m68k/unstable/vault13): FTBFS on m68k

2005-10-26 Thread maximilian attems
On Thu, 20 Oct 2005, Stephen R Marenka wrote:

> Package: klibc
> Version: 1.1.1-2
> Severity: important

next Version 1.1.1-3 will list the archs klibc currently supports.
thanks for the current moderate Severity, will leave as is.

 
> klibc fails to build from source on m68k.

this is somehow expected.
as klibc/README states m68k is not supported atm.

will need some porter work to get it building and working.

--
maks


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]