Re: m4 FTBFS

2013-12-16 Thread Santiago Vila
On Sun, 15 Dec 2013, Julien Cristau wrote:

 On Mon, Dec  2, 2013 at 11:31:58 +0100, Santiago Vila wrote:
 
  Hello.
  
  m4 FTBFS on sparc. I need help to diagnose this.
  
  https://buildd.debian.org/status/fetch.php?pkg=m4arch=sparcver=1.4.17-2stamp=1385908483
  
 Looks like an issue between the kernel and libsigsegv.  As far as I can
 tell from looking a this on smetana, sigsegv_handler gets called with
 this siginfo_t structure:
 [...]
 I'm not sure the NULL value for si_addr is expected.  In any case the
 is this near the top of the stack check fails, and the overflow
 handler is never called.

Thanks. So what should I do, in your opinion?

Submit a serious bug against libsigsegv?
Change Build-Depends to libsigsegv-dev [!sparc]?
Disable checks on sparc?


-- 
To UNSUBSCRIBE, email to debian-sparc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/alpine.deb.2.02.1312161018110.24...@cantor.unex.es



Re: m4 FTBFS

2013-12-15 Thread Julien Cristau
On Mon, Dec  2, 2013 at 11:31:58 +0100, Santiago Vila wrote:

 Hello.
 
 m4 FTBFS on sparc. I need help to diagnose this.
 
 https://buildd.debian.org/status/fetch.php?pkg=m4arch=sparcver=1.4.17-2stamp=1385908483
 
Looks like an issue between the kernel and libsigsegv.  As far as I can
tell from looking a this on smetana, sigsegv_handler gets called with
this siginfo_t structure:

(gdb) p *sip
$1 = {si_signo = 11, si_errno = 0, si_code = 1, _sifields = {_pad = {
  0 repeats 29 times}, _kill = {si_pid = 0, si_uid = 0}, _timer = {
  si_tid = 0, si_overrun = 0, si_sigval = {sival_int = 0, 
sival_ptr = 0x0}}, _rt = {si_pid = 0, si_uid = 0, si_sigval = {
sival_int = 0, sival_ptr = 0x0}}, _sigchld = {si_pid = 0, si_uid = 0, 
  si_status = 0, si_utime = 0, si_stime = 0}, _sigfault = {si_addr = 0x0, 
  si_trapno = 0}, _sigpoll = {si_band = 0, si_fd = 0}, _sigsys = {
  _call_addr = 0x0, _syscall = 0, _arch = 0}}}

I'm not sure the NULL value for si_addr is expected.  In any case the
is this near the top of the stack check fails, and the overflow
handler is never called.

Cheers,
Julien


signature.asc
Description: Digital signature


m4 FTBFS

2013-12-02 Thread Santiago Vila
Hello.

m4 FTBFS on sparc. I need help to diagnose this.

https://buildd.debian.org/status/fetch.php?pkg=m4arch=sparcver=1.4.17-2stamp=1385908483

Thanks.


-- 
To UNSUBSCRIBE, email to debian-sparc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/alpine.deb.2.02.1312021129330.27...@cantor.unex.es