Re: NEW: devel/libsigsegv

2007-06-04 Thread steven mestdagh
Scott Vokes [2007-06-04, 12:24:40]:
> Actually, here's a quick update.
> 
> Please test and commit.
> 
> Scott
> 
> On 6/4/07, Scott Vokes <[EMAIL PROTECTED]> wrote:
> >Porting this seems to be the first step to updating lang/clisp.
> >
> >   From the DESCR:
> >"This is a library for handling page faults in user mode. A page fault
> >occurs when a program tries to access to a region of memory that is
> >currently not available. Catching and handling a page fault is a useful
> >technique for implementing:
> >* pageable virtual memory,
> >* memory-mapped access to persistent databases,
> >* generational garbage collectors,
> >* stack overflow handlers,
> >* distributed shared memory,
> >* ..."
> >
> >Tested on i386, the regression tests passed. Please test and commit.

Can you make it work on other architectures?
Below is the build output on amd64.

+++ Mon Jun  4 21:39:12 CEST 2007
===>  Checking files for libsigsegv-2.4
`/a/distfiles/libsigsegv-2.4.tar.gz' is up to date.
>> (SHA256) libsigsegv-2.4.tar.gz: OK
===>  Extracting for libsigsegv-2.4
===>  Patching for libsigsegv-2.4
===>  Configuring for libsigsegv-2.4
configure: loading site script /usr/ports/infrastructure/db/config.site

Build Tools:
checking for a BSD-compatible install... /usr/bin/install -c -o root -g bin
checking whether build environment is sane... yes
checking for gawk... (cached) nawk
checking whether make sets $(MAKE)... (cached) yes
checking for gcc... cc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables... 
checking for suffix of object files... (cached) o
checking whether we are using the GNU C compiler... (cached) yes
checking whether cc accepts -g... (cached) yes
checking for cc option to accept ANSI C... none needed
checking for style of include used by make... GNU
checking dependency style of cc... none
checking how to run the C preprocessor... cc -E
checking build system type... x86_64-unknown-openbsd4.1
checking host system type... x86_64-unknown-openbsd4.1
checking host platform... x86_64-unknown-openbsd4.1
checking for a BSD-compatible install... /usr/bin/install -c -o root -g bin
checking for a sed that does not truncate output... /usr/bin/sed
checking for egrep... (cached) grep -E
checking for ld used by cc... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for /usr/bin/ld option to reload object files... -r
checking for BSD-compatible nm... /usr/bin/nm -B
checking whether ln -s works... yes
checking how to recognise dependent libraries... match_pattern 
/lib[^/]+(\.so\.[0-9]+\.[0-9]+|\.so|_pic\.a)$
checking for ANSI C header files... (cached) yes
checking for sys/types.h... (cached) yes
checking for sys/stat.h... (cached) yes
checking for stdlib.h... (cached) yes
checking for string.h... (cached) yes
checking for memory.h... (cached) yes
checking for strings.h... (cached) yes
checking for inttypes.h... (cached) yes
checking for stdint.h... (cached) yes
checking for unistd.h... (cached) yes
checking for dlfcn.h... (cached) yes
checking whether we are using the GNU C++ compiler... (cached) yes
checking whether c++ accepts -g... (cached) yes
checking dependency style of c++... none
checking how to run the C++ preprocessor... c++ -E
checking for g77... g77
checking whether we are using the GNU Fortran 77 compiler... (cached) yes
checking whether g77 accepts -g... (cached) yes
checking the maximum length of command line arguments... (cached) 131072
checking command to parse /usr/bin/nm -B output from cc object... ok
checking for objdir... .libs
checking for ar... (cached) ar
checking for ranlib... (cached) ranlib
checking for strip... (cached) strip
checking if cc supports -fno-rtti -fno-exceptions... no
checking for cc option to produce PIC... -fPIC
checking if cc PIC flag -fPIC works... yes
checking if cc static flag -static works... yes
checking if cc supports -c -o file.o... yes
checking whether the cc linker (/usr/bin/ld) supports shared libraries... yes
checking whether -lc should be explicitly linked in... yes
checking dynamic linker characteristics... openbsd4.1 ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... yes
configure: creating libtool
appending configuration tag "CXX" to libtool
checking for ld used by c++... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking whether the c++ linker (/usr/bin/ld) supports shared libraries... yes
checking for c++ option to produce PIC... -fPIC
checking if c++ PIC flag -fPIC works... yes
checking if c++ static flag -static works... yes
checking if c++ supports -c -o file.o... yes
checking whether the c++ linker (/usr/bin/ld) supports shared libraries..

Re: NEW: devel/libsigsegv

2007-06-04 Thread Scott Vokes

Actually, here's a quick update.

Please test and commit.

Scott

On 6/4/07, Scott Vokes <[EMAIL PROTECTED]> wrote:

Porting this seems to be the first step to updating lang/clisp.

   From the DESCR:
"This is a library for handling page faults in user mode. A page fault
occurs when a program tries to access to a region of memory that is
currently not available. Catching and handling a page fault is a useful
technique for implementing:
* pageable virtual memory,
* memory-mapped access to persistent databases,
* generational garbage collectors,
* stack overflow handlers,
* distributed shared memory,
* ..."

Tested on i386, the regression tests passed. Please test and commit.

Thanks,
Scott
--
"I am not exactly the person you need
 to tell you about how Google works." -Ray Smuckles


libsigsegv.tgz
Description: GNU Zip compressed data


NEW: devel/libsigsegv

2007-06-03 Thread Scott Vokes

Porting this seems to be the first step to updating lang/clisp.

  From the DESCR:
"This is a library for handling page faults in user mode. A page fault
occurs when a program tries to access to a region of memory that is
currently not available. Catching and handling a page fault is a useful
technique for implementing:
   * pageable virtual memory,
   * memory-mapped access to persistent databases,
   * generational garbage collectors,
   * stack overflow handlers,
   * distributed shared memory,
   * ..."

Tested on i386, the regression tests passed. Please test and commit.

Thanks,
Scott
--
"I am not exactly the person you need
to tell you about how Google works." -Ray Smuckles


libsigsegv.tgz
Description: GNU Zip compressed data