severity 679592 normal
thanks
On Sun, Jul 29, 2012 at 09:56:04PM +0200, Mathieu Malaterre wrote:
> I am marking this as grave, since this looks like a regression. I do
> not understand what happen exactly, but clearly pike support
> disappear.
Actually, pike support hasn't disappeared:
$ dpkg -l swig2.0
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-==============-============-============-=================================
ii swig2.0 2.0.7-3 amd64 Generate scripting interfaces to
$ echo '%module test' > test.i
$ swig2.0 -pike test.i
$ ls -l test_wrap.c
-rw-r--r-- 1 olly olly 32089 Sep 6 12:07 test_wrap.c
> ...
> checking for /usr/bin/pike7.6-config... no
> checking for pike-config... no
> checking for pike7.6-config... no
> checking for pike7.4-config... no
> checking for pike7.2-config... no
> ...
This just means that running "make check" in the build tree won't run any
tests for pike bindings. SWIG will still have pike support.
It would be better to install the required dependencies so that the
SWIG testsuite gets run for pike (and other languages), but this isn't
a regression in pike support, so it's not an RC issue.
Cheers,
Olly
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
