Bug#549569: libguytools1: Support for more arches.
Michael Prokop m...@debian.org (29/01/2010): I just uploaded libguytools1 (1.1.1-1) which additionally includes powerpc in the list of supported architectures. Why don't you just put Arch: any and let both buildds and interested users test it for you? Mraw, KiBi. signature.asc Description: Digital signature
Bug#549569: libguytools1: Support for more arches.
* Michael Prokop m...@debian.org [20100129 04:29]: * vogu00 vog...@gmail.com [20091006 08:38]: Michael Prokop wrote: arches in the future, and how hard it would be to add it? Guy: any information from your side? Stack backtracking: Have a look at function ToolSignalBacktraceHandler in toolsignal.cpp. I already made it architecture independant but I never tried it on architectures like sparc, for instance. However, I have an old PowerBook G4 at my disposal where succesfully build libguytools and guymager powerpc packages. Just add powerpc to the list of architectures in debian/control. Thanks - adjusted in git: http://git.debian.org/?p=forensics/libguytools.git;a=commit;h=a9262ba8e75bcc583480227026c9a048ad1ccf23 I just uploaded libguytools1 (1.1.1-1) which additionally includes powerpc in the list of supported architectures. I'll try to reach people with access to different platforms (thanks for the hint, Kurt) so we can check out which archs could be supported as well. regards, -mika- signature.asc Description: Digital signature
Bug#549569: libguytools1: Support for more arches.
Michael Prokop wrote: [Cc-ing Guy who's upstream of libguytools/guymager] * Kurt Roeckx [20091004 15:25]: Package: libguytools1 Version: 1.0.4-1 It seems the current pacakge only allows building on i386 and amd64. Is there a reason why hurd and kfreebsd couldn't work? libguytools is mostly straight-forward C code, except for some lines in backtrace handler (see below). I'm not sure if you could encounter little problems with header files (surely nothing serious), I don't have experience with hurd and kfreebsd. Looking at the description, it seems to support stack backtracking which is arch dependent, and I assume it currently only supports amd64 and i386. Do you know if there are plans to support more arches in the future, and how hard it would be to add it? Guy: any information from your side? Stack backtracking: Have a look at function ToolSignalBacktraceHandler in toolsignal.cpp. I already made it architecture independant but I never tried it on architectures like sparc, for instance. However, I have an old PowerBook G4 at my disposal where succesfully build libguytools and guymager powerpc packages. Just add powerpc to the list of architectures in debian/control. Adding other architectures: The function ToolSignalBacktraceHandler should normally be the only one that needs to be adapted. Guy -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#549569: libguytools1: Support for more arches.
* vogu00 vog...@gmail.com [20091006 08:38]: Michael Prokop wrote: * Kurt Roeckx [20091004 15:25]: Looking at the description, it seems to support stack backtracking which is arch dependent, and I assume it currently only supports amd64 and i386. Do you know if there are plans to support more arches in the future, and how hard it would be to add it? Guy: any information from your side? Stack backtracking: Have a look at function ToolSignalBacktraceHandler in toolsignal.cpp. I already made it architecture independant but I never tried it on architectures like sparc, for instance. However, I have an old PowerBook G4 at my disposal where succesfully build libguytools and guymager powerpc packages. Just add powerpc to the list of architectures in debian/control. Thanks - adjusted in git: http://git.debian.org/?p=forensics/libguytools.git;a=commit;h=a9262ba8e75bcc583480227026c9a048ad1ccf23 Adding other architectures: The function ToolSignalBacktraceHandler should normally be the only one that needs to be adapted. Please let me know if should change anything further, thanks. regards, -mika- signature.asc Description: Digital signature
Bug#549569: libguytools1: Support for more arches.
On Tue, Oct 06, 2009 at 09:15:24AM +0200, Michael Prokop wrote: Adding other architectures: The function ToolSignalBacktraceHandler should normally be the only one that needs to be adapted. Please let me know if should change anything further, thanks. You probably want to contact the porter lists if you want someone to port (or test) it for you. Kurt -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#549569: libguytools1: Support for more arches.
[Cc-ing Guy who's upstream of libguytools/guymager] * Kurt Roeckx [20091004 15:25]: Package: libguytools1 Version: 1.0.4-1 It seems the current pacakge only allows building on i386 and amd64. Is there a reason why hurd and kfreebsd couldn't work? Looking at the description, it seems to support stack backtracking which is arch dependent, and I assume it currently only supports amd64 and i386. Do you know if there are plans to support more arches in the future, and how hard it would be to add it? Guy: any information from your side? thx regards, -mika- signature.asc Description: Digital signature
Bug#549569: libguytools1: Support for more arches.
Package: libguytools1 Version: 1.0.4-1 Hi, It seems the current pacakge only allows building on i386 and amd64. Is there a reason why hurd and kfreebsd couldn't work? Looking at the description, it seems to support stack backtracking which is arch dependent, and I assume it currently only supports amd64 and i386. Do you know if there are plans to support more arches in the future, and how hard it would be to add it? Kurt -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
