[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: libsigsegv fails to compile under OpenWRT and LibreCMC
From: |
Bruno Haible |
Subject: |
Re: libsigsegv fails to compile under OpenWRT and LibreCMC |
Date: |
Thu, 20 Feb 2020 18:05:43 +0100 |
User-agent: |
KMail/5.1.3 (Linux/4.4.0-171-generic; KDE/5.18.0; x86_64; ; ) |
Hi,
> ./configure --target=mips-openwrt-linux --host=mips-openwrt-linux
> --build=x86_64-pc-linux-gnu --program-prefix="" --program-suffix=""
> --prefix=/usr --exec-prefix=/usr --bindir=/usr/bin --sbindir=/usr/sbin
> --libexecdir=/usr/lib --sysconfdir=/etc --datadir=/usr/share
> --localstatedir=/var --mandir=/usr/man --infodir=/usr/info --disable-nls
>
> The transcript of the compilation session is attached, as well as
> config.status.
I see this in the log:
checking whether a fault handler according to POSIX works... guessing no
checking whether a fault handler according to Linux/i386 works... no
checking whether a fault handler according to old Linux/i386 works... guessing
no
checking whether a fault handler according to Linux/m68k works... no
checking whether a fault handler according to Linux/PowerPC works... no
checking whether a fault handler according to Linux/HPPA works... guessing no
checking whether a fault handler according to BSD works... guessing no
checking whether a fault handler according to IRIX works... no
checking whether a fault handler according to HP-UX HPPA works... no
checking whether a fault handler according to OSF/1 Alpha works... no
checking whether a fault handler according to NetBSD Alpha works... guessing no
checking whether a fault handler according to AIX works... no
checking whether a fault handler according to MacOSX/Darwin7 PowerPC works... no
checking whether a fault handler according to MacOSX/Darwin5 PowerPC works... no
checking whether a fault handler according to Hurd works... guessing no
...
checking whether a signal handler can be left through longjmp... guessing no
checking whether a signal handler can be left through longjmp and
sigaltstack... guessing no
checking whether a signal handler can be left through longjmp and setcontext...
guessing no
checking whether a signal handler can be left through siglongjmp... guessing no
checking whether a signal handler can be left through siglongjmp and
sigaltstack... guessing no
checking whether a signal handler can be left through siglongjmp and
setcontext... guessing no
These "guessing no" are caused by cross-compilation.
In a native compilation on Linux/mips, I get these determinations (not guesses):
checking whether a fault handler according to POSIX works... yes
checking whether a fault handler according to Linux/i386 works... no
checking whether a fault handler according to old Linux/i386 works... no
checking whether a fault handler according to Linux/m68k works... no
checking whether a fault handler according to Linux/PowerPC works... no
checking whether a fault handler according to Linux/HPPA works... no
checking whether a fault handler according to BSD works... no
checking whether a fault handler according to IRIX works... no
checking whether a fault handler according to HP-UX HPPA works... no
checking whether a fault handler according to OSF/1 Alpha works... no
checking whether a fault handler according to NetBSD Alpha works... no
checking whether a fault handler according to AIX works... no
checking whether a fault handler according to MacOSX/Darwin7 PowerPC works... no
checking whether a fault handler according to MacOSX/Darwin5 PowerPC works... no
checking whether a fault handler according to Hurd works... no
...
checking whether a signal handler can be left through longjmp... yes
checking whether a signal handler can be left through longjmp and
sigaltstack... yes
checking whether a signal handler can be left through longjmp and setcontext...
yes
checking whether a signal handler can be left through siglongjmp... yes
checking whether a signal handler can be left through siglongjmp and
sigaltstack... yes
checking whether a signal handler can be left through siglongjmp and
setcontext... yes
Therefore either
* use a native compilation instead of a cross-compilation, or
* set the following variables (as environment variables) before the run:
sv_cv_fault_posix=yes
sv_cv_leave_handler_longjmp=yes
sv_cv_leave_handler_longjmp_sigaltstack=yes
sv_cv_leave_handler_longjmp_setcontext=yes
sv_cv_leave_handler_siglongjmp=yes
sv_cv_leave_handler_siglongjmp_sigaltstack=yes
sv_cv_leave_handler_siglongjmp_setcontext=yes
That should do it.
Bruno