libffi onOpenBSD 3.9

Here are testresults for libffi 3.0.2 (from cvs) on an
OpenBSD 3.9 system.
I realize that this is old, but it is the only openbsd
vmware image I have currently
laying around.

Hope this is useful.

Thomas

$ make check | tee libffi.check.log
Making check in include
Making check in testsuite
make  check-DEJAGNU
srcdir=`CDPATH="${ZSH_VERSION+.}:" && cd .
&& pwd`; export srcdir;  EXPECT=`if [ -f
../../expect/expect ] ; then  echo ../../expect/expect ; 
else echo expect ; fi`; export EXPECT;  runtest=`if [ -f
../../dejagnu/runtest ] ; then  echo ../../dejagnu/runtest ;
 else echo runtest; fi`;  if /bin/sh -c "$runtest
--version" > /dev/null 2>&1; then 
exit_status=0; l='libffi'; for tool in $l; do  if $runtest 
--tool $tool --srcdir $srcdir ;  then :; else exit_status=1;
fi;  done;  else echo "WARNING: could not find
`runtest'" 1>&2; :; fi;  exit $exit_status
WARNING: Couldn't find the global config file.
WARNING: Couldn't find tool init file
Test Run By theller on Fri Feb 22 20:17:50 2008
Native configuration is i386-unknown-openbsd3.9

                === libffi tests ===

Schedule of variations:
    unix

Running target unix
Using /usr/local/share/dejagnu/baseboards/unix.exp as board
description file for target.
Using /usr/local/share/dejagnu/config/unix.exp as generic
interface file for target.
Using /home/theller/libffi/testsuite/config/default.exp as
tool-and-target-specific interface file.
Running /home/theller/libffi/testsuite/libffi.call/call.exp
...
FAIL: libffi.call/cls_1_1byte.c execution test
FAIL: libffi.call/cls_2byte.c execution test
FAIL: libffi.call/cls_3byte1.c execution test
FAIL: libffi.call/cls_3byte2.c execution test
FAIL: libffi.call/cls_4_1byte.c execution test
FAIL: libffi.call/cls_4byte.c execution test
FAIL: libffi.call/cls_7byte.c execution test
FAIL: libffi.call/cls_8byte.c execution test
FAIL: libffi.call/float2.c (test for excess errors)
FAIL: libffi.call/return_uc.c (test for excess errors)
FAIL: libffi.call/struct3.c execution test
FAIL: libffi.call/struct5.c execution test
FAIL: libffi.call/struct9.c execution test
FAIL: libffi.call/cls_1_1byte.c execution test
FAIL: libffi.call/cls_2byte.c output pattern test, is 170 72
12 127: 182 199
res: 0 0
1 13 236 7: 237 20
res: 13 0
? should match 12 127 1 13: 13 140
?es: 13 140
?2 127 1 13: 13 140
res: 13 140
FAIL: libffi.call/cls_3byte1.c execution test
FAIL: libffi.call/cls_3byte2.c execution test
FAIL: libffi.call/cls_4_1byte.c execution test
FAIL: libffi.call/cls_4byte.c execution test
FAIL: libffi.call/cls_7byte.c execution test
FAIL: libffi.call/cls_8byte.c execution test
FAIL: libffi.call/struct3.c execution test
FAIL: libffi.call/struct5.c execution test
FAIL: libffi.call/struct9.c execution test
FAIL: libffi.call/cls_1_1byte.c execution test
FAIL: libffi.call/cls_2byte.c execution test
FAIL: libffi.call/cls_3byte1.c execution test
FAIL: libffi.call/cls_3byte2.c execution test
FAIL: libffi.call/cls_4_1byte.c execution test
FAIL: libffi.call/cls_4byte.c execution test
FAIL: libffi.call/cls_7byte.c execution test
FAIL: libffi.call/cls_8byte.c execution test
FAIL: libffi.call/struct3.c execution test
FAIL: libffi.call/struct5.c execution test
FAIL: libffi.call/struct9.c execution test
FAIL: libffi.call/cls_1_1byte.c execution test
FAIL: libffi.call/cls_2byte.c execution test
FAIL: libffi.call/cls_3byte1.c execution test
FAIL: libffi.call/cls_3byte2.c execution test
FAIL: libffi.call/cls_4_1byte.c execution test
FAIL: libffi.call/cls_4byte.c execution test
FAIL: libffi.call/cls_7byte.c execution test
FAIL: libffi.call/cls_8byte.c execution test
FAIL: libffi.call/struct3.c execution test
FAIL: libffi.call/struct5.c execution test
FAIL: libffi.call/struct9.c execution test
FAIL: libffi.call/cls_1_1byte.c execution test
FAIL: libffi.call/cls_2byte.c execution test
FAIL: libffi.call/cls_3byte1.c execution test
FAIL: libffi.call/cls_3byte2.c execution test
FAIL: libffi.call/cls_4_1byte.c execution test
FAIL: libffi.call/cls_4byte.c execution test
FAIL: libffi.call/cls_7byte.c execution test
FAIL: libffi.call/cls_8byte.c execution test
FAIL: libffi.call/struct3.c execution test
FAIL: libffi.call/struct5.c execution test
FAIL: libffi.call/struct9.c execution test
Running
/home/theller/libffi/testsuite/libffi.special/special.exp
...
FAIL: libffi.special/unwindtest.cc (test for excess errors)
WARNING: libffi.special/unwindtest.cc compilation failed to
produce executable
FAIL: libffi.special/unwindtest_ffi_call.cc (test for excess
errors)
WARNING: libffi.special/unwindtest_ffi_call.cc compilation
failed to produce executable
FAIL: libffi.special/unwindtest.cc (test for excess errors)
WARNING: libffi.special/unwindtest.cc compilation failed to
produce executable
FAIL: libffi.special/unwindtest_ffi_call.cc (test for excess
errors)
WARNING: libffi.special/unwindtest_ffi_call.cc compilation
failed to produce executable
FAIL: libffi.special/unwindtest.cc (test for excess errors)
WARNING: libffi.special/unwindtest.cc compilation failed to
produce executable
FAIL: libffi.special/unwindtest_ffi_call.cc (test for excess
errors)
WARNING: libffi.special/unwindtest_ffi_call.cc compilation
failed to produce executable
FAIL: libffi.special/unwindtest.cc (test for excess errors)
WARNING: libffi.special/unwindtest.cc compilation failed to
produce executable
FAIL: libffi.special/unwindtest_ffi_call.cc (test for excess
errors)
WARNING: libffi.special/unwindtest_ffi_call.cc compilation
failed to produce executable

                === libffi Summary ===

# of expected passes            1269
# of unexpected failures        65
# of unsupported tests          15
*** Error code 1

Stop in /home/theller/libffi/testsuite (line 294 of
Makefile).
*** Error code 1

Stop in /home/theller/libffi/testsuite (line 348 of
Makefile).
*** Error code 1

Stop in /home/theller/libffi (line 1160 of Makefile).
$ gcc --version
gcc (GCC) 3.3.5 (propolice)
Copyright (C) 2003 Free Software Foundation, Inc.
This is free software; see the source for copying
conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A
PARTICULAR PURPOSE.

$ uname -a
OpenBSD openbsd39.localdomain 3.9 GENERIC#617 i386
$

> Here are testresults for libffi 3.0.2 (from cvs) on an
OpenBSD 3.9 system.
> I realize that this is old, but it is the only openbsd
vmware image I have
> currently
> laying around.
>
> [... many failures ...]

I suggest to let OpenBSD use the FreeBSD bits. Replace
'i386-*-freebsd*'
with 'i386-*-openbsd*' in configure.ac, run autoconf and try
again. I
suppose that the patch I submitted recently can be applied
to all BSD
variants. If this works then all occurrences of X86_FREEBSD
should be
replaced with X86_BSD, freebsd.S renamed to bsd.S and so on,
to be more
liberally. 

Björn

Björn König schrieb:
>> Here are testresults for libffi 3.0.2 (from cvs) on
an OpenBSD 3.9 system.
>> I realize that this is old, but it is the only
openbsd vmware image I have
>> currently
>> laying around.
>>
>> [... many failures ...]
> 
> I suggest to let OpenBSD use the FreeBSD bits. Replace
'i386-*-freebsd*'
> with 'i386-*-openbsd*' in configure.ac, run autoconf
and try again. I
> suppose that the patch I submitted recently can be
applied to all BSD
> variants. If this works then all occurrences of
X86_FREEBSD should be
> replaced with X86_BSD, freebsd.S renamed to bsd.S and
so on, to be more
> liberally. 

With this patch to configure.ac (and a regenerated configure
script)...

thomastubu:~/devel/libffi$ cvs diff -u configure.ac
Index: configure.ac
============================================================
=======
RCS file: /cvs/libffi/libffi/configure.ac,v
retrieving revision 1.16
diff -u -r1.16 configure.ac
--- configure.ac        21 Feb 2008 13:36:18 -0000     
1.16
+++ configure.ac        22 Feb 2008 20:18:37 -0000
 -67,7
+67,7 
        TARGET=PA_HPUX; TARGETDIR=pa
        ;;

-  i386-*-freebsd*)
+  i386-*-freebsd* | i386-*-openbsd*)
        TARGET=X86_FREEBSD; TARGETDIR=x86
        ;;
   i?86-win32* | i?86-*-cygwin* | i?86-*-mingw*)
thomastubu:~/devel/libffi$

...I'm down from 65 unexpected failures to 10.

> 
> Björn
> 
> 

Thomas

Thomas Heller wrote:

> ...I'm down from 65 unexpected failures to 10.

Please tell us them.

Björn

Thomas Heller wrote:
> Björn König schrieb:
>   
>>> Here are testresults for libffi 3.0.2 (from
cvs) on an OpenBSD 3.9 system.
>>> I realize that this is old, but it is the only
openbsd vmware image I have
>>> currently
>>> laying around.
>>>
>>> [... many failures ...]
>>>       
>> I suggest to let OpenBSD use the FreeBSD bits.
Replace 'i386-*-freebsd*'
>> with 'i386-*-openbsd*' in configure.ac, run
autoconf and try again. I
>> suppose that the patch I submitted recently can be
applied to all BSD
>> variants. If this works then all occurrences of
X86_FREEBSD should be
>> replaced with X86_BSD, freebsd.S renamed to bsd.S
and so on, to be more
>> liberally. 
>>     
>
> With this patch to configure.ac (and a regenerated
configure script)...
>
> thomastubu:~/devel/libffi$ cvs diff -u configure.ac
> Index: configure.ac
>
============================================================
=======
> RCS file: /cvs/libffi/libffi/configure.ac,v
> retrieving revision 1.16
> diff -u -r1.16 configure.ac
> --- configure.ac        21 Feb 2008 13:36:18 -0000     
1.16
> +++ configure.ac        22 Feb 2008 20:18:37 -0000
>  -67,7 +67,7 
>         TARGET=PA_HPUX; TARGETDIR=pa
>         ;;
>
> -  i386-*-freebsd*)
> +  i386-*-freebsd* | i386-*-openbsd*)
>         TARGET=X86_FREEBSD; TARGETDIR=x86
>         ;;
>    i?86-win32* | i?86-*-cygwin* | i?86-*-mingw*)
> thomastubu:~/devel/libffi$
>
> ...I'm down from 65 unexpected failures to 10.
>   
Thanks Thomas.

Does it make sense to change that line to...

+  i?86-*-freebsd* | i?86-*-openbsd*)


AG

Anthony Green wrote:

> Does it make sense to change that line to...
>
> +  i?86-*-freebsd* | i?86-*-openbsd*)

No, at least for FreeBSD it definitely does not make sense
and I think
this applies for OpenBSD too.

It is meant as a synonym for the IA-32 architecture in
general. It does
not have something to do with 80386 processors. FreeBSD does
not even run
on these anymore.

Björn

Björn König schrieb:
> Thomas Heller wrote:
> 
>> ...I'm down from 65 unexpected failures to 10.
> 

$ make check
Making check in include
Making check in testsuite
make  check-DEJAGNU
srcdir=`CDPATH="${ZSH_VERSION+.}:" && cd .
&& pwd`; export srcdir;  EXPECT=`if [ -f
../../expect/expect ] ; then  echo ../../expect/expect ; 
else echo expect ; fi`; export EXPECT;  runtest=`if [ -f
../../dejagnu/runtest ] ; then  echo ../../dejagnu/runtest ;
 else echo runtest; fi`;  if /bin/sh -c "$runtest
--version" > /dev/null 2>&1; then 
exit_status=0; l='libffi'; for tool in $l; do  if $runtest 
--tool $tool --srcdir $srcdir ;  then :; else exit_status=1;
fi;  done;  else echo "WARNING: could not find
`runtest'" 1>&2; :; fi;  exit $exit_status
WARNING: Couldn't find the global config file.
WARNING: Couldn't find tool init file
Test Run By theller on Fri Feb 22 21:59:08 2008
Native configuration is i386-unknown-openbsd3.9

                === libffi tests ===

Schedule of variations:
    unix

Running target unix
Using /usr/local/share/dejagnu/baseboards/unix.exp as board
description file for target.
Using /usr/local/share/dejagnu/config/unix.exp as generic
interface file for target.
Using /home/theller/libffi/testsuite/config/default.exp as
tool-and-target-specific interface file.
Running /home/theller/libffi/testsuite/libffi.call/call.exp
...
FAIL: libffi.call/float2.c (test for excess errors)
FAIL: libffi.call/return_uc.c (test for excess errors)
Running
/home/theller/libffi/testsuite/libffi.special/special.exp
...
FAIL: libffi.special/unwindtest.cc (test for excess errors)
WARNING: libffi.special/unwindtest.cc compilation failed to
produce executable
FAIL: libffi.special/unwindtest_ffi_call.cc (test for excess
errors)
WARNING: libffi.special/unwindtest_ffi_call.cc compilation
failed to produce executable
FAIL: libffi.special/unwindtest.cc (test for excess errors)
WARNING: libffi.special/unwindtest.cc compilation failed to
produce executable
FAIL: libffi.special/unwindtest_ffi_call.cc (test for excess
errors)
WARNING: libffi.special/unwindtest_ffi_call.cc compilation
failed to produce executable
FAIL: libffi.special/unwindtest.cc (test for excess errors)
WARNING: libffi.special/unwindtest.cc compilation failed to
produce executable
FAIL: libffi.special/unwindtest_ffi_call.cc (test for excess
errors)
WARNING: libffi.special/unwindtest_ffi_call.cc compilation
failed to produce executable
FAIL: libffi.special/unwindtest.cc (test for excess errors)
WARNING: libffi.special/unwindtest.cc compilation failed to
produce executable
FAIL: libffi.special/unwindtest_ffi_call.cc (test for excess
errors)
WARNING: libffi.special/unwindtest_ffi_call.cc compilation
failed to produce executable

                === libffi Summary ===

# of expected passes            1363
# of unexpected failures        10
# of unsupported tests          15
*** Error code 1

Stop in /home/theller/libffi/testsuite (line 294 of
Makefile).
*** Error code 1

Stop in /home/theller/libffi/testsuite (line 348 of
Makefile).
*** Error code 1

Stop in /home/theller/libffi (line 1160 of Makefile).
$

Thomas Heller wrote:
> Björn König schrieb:
>> Thomas Heller wrote:
>>
>>> ...I'm down from 65 unexpected failures to 10.
> 
> $ make check
> Making check in include
> Making check in testsuite
> make  check-DEJAGNU
> srcdir=`CDPATH="${ZSH_VERSION+.}:" &&
cd . && pwd`; export srcdir;  EXPECT=`if [ -f
../../expect/expect ] ; then  echo ../../expect/expect ; 
else echo expect ; fi`; export EXPECT;  runtest=`if [ -f
../../dejagnu/runtest ] ; then  echo ../../dejagnu/runtest ;
 else echo runtest; fi`;  if /bin/sh -c "$runtest
--version" > /dev/null 2>&1; then 
exit_status=0; l='libffi'; for tool in $l; do  if $runtest 
--tool $tool --srcdir $srcdir ;  then :; else exit_status=1;
fi;  done;  else echo "WARNING: could not find
`runtest'" 1>&2; :; fi;  exit $exit_status
> WARNING: Couldn't find the global config file.
> WARNING: Couldn't find tool init file
> Test Run By theller on Fri Feb 22 21:59:08 2008
> Native configuration is i386-unknown-openbsd3.9
> 
>                 === libffi tests ===
> 
> Schedule of variations:
>     unix
> 
> Running target unix
> Using /usr/local/share/dejagnu/baseboards/unix.exp as
board description file for target.
> Using /usr/local/share/dejagnu/config/unix.exp as
generic interface file for target.
> Using /home/theller/libffi/testsuite/config/default.exp
as tool-and-target-specific interface file.
> Running
/home/theller/libffi/testsuite/libffi.call/call.exp ...
> FAIL: libffi.call/float2.c (test for excess errors)
> FAIL: libffi.call/return_uc.c (test for excess errors)

gdb might help here?

You also might comment the CHECK function in the test cases
to see 
what's coming out.

> Running
/home/theller/libffi/testsuite/libffi.special/special.exp
...
> FAIL: libffi.special/unwindtest.cc (test for excess
errors)
> WARNING: libffi.special/unwindtest.cc compilation
failed to produce executable
> FAIL: libffi.special/unwindtest_ffi_call.cc (test for
excess errors)
> WARNING: libffi.special/unwindtest_ffi_call.cc
compilation failed to produce executable
> FAIL: libffi.special/unwindtest.cc (test for excess
errors)
> WARNING: libffi.special/unwindtest.cc compilation
failed to produce executable
> FAIL: libffi.special/unwindtest_ffi_call.cc (test for
excess errors)
> WARNING: libffi.special/unwindtest_ffi_call.cc
compilation failed to produce executable
> FAIL: libffi.special/unwindtest.cc (test for excess
errors)
> WARNING: libffi.special/unwindtest.cc compilation
failed to produce executable
> FAIL: libffi.special/unwindtest_ffi_call.cc (test for
excess errors)
> WARNING: libffi.special/unwindtest_ffi_call.cc
compilation failed to produce executable
> FAIL: libffi.special/unwindtest.cc (test for excess
errors)
> WARNING: libffi.special/unwindtest.cc compilation
failed to produce executable
> FAIL: libffi.special/unwindtest_ffi_call.cc (test for
excess errors)
> WARNING: libffi.special/unwindtest_ffi_call.cc
compilation failed to produce executable


Having a look into the testsuite/libffi.log might tell you
why it failed 
to produce an exe?

Andreas

[forgot to cc the list]

Andrew Haley schrieb:
> > Thomas Heller wrote:
> > 
> > ...
> > 
> > I think you do not have a working C++ compiler.
> > 
> > Andrew.

I installed g++, the logfile testsuite/libffi.log contains
these errors:

WARNING: libffi.special/unwindtest.cc compilation failed to
produce executable
Executing on host: gcc
/home/theller/libffi/testsuite/libffi.special/unwindtest_ffi
_call.cc   -shared-libgcc -lstdc++ -O0 -W -Wall -I/
home/theller/libffi/testsuite/../include
-I/home/theller/libffi/testsuite/../include 
-I/home/theller/libffi/testsuite/../include/.. -
L/home/theller/libffi/testsuite/../.libs  -lffi -lm   -o
./unwindtest_ffi_call.exe    (timeout = 300)
/home/theller/libffi/testsuite/libffi.special/unwindtest_ffi
_call.cc:10: error: syntax
   error before `__attribute__'
compiler exited with status 1
output is:
/home/theller/libffi/testsuite/libffi.special/unwindtest_ffi
_call.cc:10: error: syntax
   error before `__attribute__'

Any idea?

Thomas

On Sat, Feb 23, 2008 at 9:12 AM, Thomas Heller
<thellerctypes.org> wrote:
> [forgot to cc the list]
>
>  I installed g++, the logfile testsuite/libffi.log
contains these errors:
> 
/home/theller/libffi/testsuite/libffi.special/unwindtest_ffi
_call.cc:10: error: syntax
>    error before `__attribute__'
>  compiler exited with status 1
>  output is:
> 
/home/theller/libffi/testsuite/libffi.special/unwindtest_ffi
_call.cc:10: error: syntax
>    error before `__attribute__'
>
>  Any idea?

What version of g++?  This is most likely due to parser
changes in
3.4.0 which changed where __attribute__ is allowed.

-- Pinski