From: Alexei S. <ale...@gm...> - 2012-08-12 17:18:27
|
This should now be fixed in TOT in the git repo. You'll need to re-run autogen.sh. -Alexei On Thu, Aug 9, 2012 at 10:14 AM, Giulio Paci <giu...@gm...> wrote: > On 09/08/2012 06:27, Alexei Svitkine wrote: >> On Wed, Aug 8, 2012 at 12:48 PM, Giulio Paci <giu...@gm...> wrote: >>> Hi to all, >>> >>> On 09/06/2012 20:44, Giulio Paci wrote: >>>> Basilisk II has been accepted into Debian unstable. >>>> Unfortunately the first upload is not compiling properly in most of the >>>> supported architectures, as it is described by this compilation report: >>>> https://buildd.debian.org/status/package.php?p=basilisk2 >>> >>> For ia64, mips, mipsel, sparc and powerpc it was my fault and I fixed that. >>> For kfreebsd Alexei Svitkine committed a fix, that is working. >>> >>> For armel the building procedure reports: >>> >>> sigsegv.cpp:1623: error: 'SIGSEGV_FAULT_HANDLER_ARGLIST' was not >>> declared in this scope >>> sigsegv.cpp:1624: error: expected ',' or ';' before '{' token >>> gmake: *** [obj/sigsegv.o] Error 1 >>> gmake: *** Waiting for unfinished jobs.... >>> *** Error code 2 >> >> Those line numbers don't look right to me. Do you have local edits to the file? > > No I have not, however this report is not about the latest version in > git (that is still failing with the same error message, about 800 lines > below): it is about the codebase I used to build the Debian package > (i.e., a CVS snapshot at the end of march). > >>> I had a quick look to this issue, but, once again, the fix is beyond my >>> knowledge and I found no useful information about it on the web (only >>> people experimenting this issue, but no solution). Unfortunately I also >>> had very few time last month, so I was not able to do anything useful >>> about this issue. >>> I have installed a Debian armel using qemu, so I have access to an armel >>> system now. If anyone wants to propose a solution for this issue I will >>> be able to try it. If anyone is interested I can also share the VM image. > >> Please share the VM image > > boot.sh: a script that can be used to start the VM (using qemu) > https://docs.google.com/open?id=0B7cMsawWW7uSUFFITVJnVzJEWkU > > boot.tar.bz2: the /boot directory containing the kernel to start the VM > https://docs.google.com/open?id=0B7cMsawWW7uSMmFPdHlMaGVsVG8 > > debian-testing-armel.qcow.bz2: the image of a current Debian testing > https://docs.google.com/open?id=0B7cMsawWW7uSTHd1LUM0VllvQW8 > > To run the VM, install qemu with arm support, untar the boot.tar.bz2, > expand debian-testing-armel.qcow.bz2 and run the script. > > There is a "root" user and a "debian" user. > The password for both is "debian". > The "debian" user already has macemu git repository in its home > (~/Source/macemu), and BasiliskII has already been configured. Running > make in ~/Source/macemu/BasiliskII/src/Unix should give you the error. > > In ~/Source/debian-packages/basilisk2 there are the sources of the > Debian package. To compile it you can run "git-buildpackage > --git-ignore-new", and compilation should fail with the error above. > >> and I'll try to take a look at it as time permits. Thanks. > > Thank you very much for your help. > > Bests, > Giulio. > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > basilisk-devel mailing list > bas...@li... > https://lists.sourceforge.net/lists/listinfo/basilisk-devel |