Re: (fcntl fd F_GETLK ...) from Guile

2007-09-03 Thread Kaloian Doganov
Mike Gran <[EMAIL PROTECTED]> writes:

I put together something.  I've attached the more important source
files here for reference, but, the buildable files are in
http://lonelycactus.com/getlk-0.0.tar.gz

Mike, I really appreciate your help.

For me, it does "./configure && make && make install" on Linux, but
fails on Cygwin.

I guess by "Linux" you actually mean GNU/Linux, since the make program
can not run on the bare kernel.  Unfortunately, the configure script
fails on my system (gNewSense):

Script started on  3.09.2007 (пн) 10,55,52 EEST
checking for a BSD-compatible install... /usr/bin/install -c

checking whether build environment is sane... yes

checking for gawk... gawk

checking whether make sets $(MAKE)... yes

checking for gcc... gcc

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... o

checking whether we are using the GNU C compiler... yes

checking whether gcc accepts -g... yes

checking for gcc option to accept ISO C89... none needed

checking for style of include used by make... GNU

checking dependency style of gcc... gcc3

checking build system type... i686-pc-linux-gnu

checking host system type... i686-pc-linux-gnu

checking for a sed that does not truncate output... /bin/sed

checking for grep that handles long lines and -e... /bin/grep

checking for egrep... /bin/grep -E

checking for ld used by gcc... /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 recognize dependent libraries... pass_all

checking how to run the C preprocessor... gcc -E

checking for ANSI C header files... yes

checking for sys/types.h... yes

checking for sys/stat.h... yes

checking for stdlib.h... yes

checking for string.h... yes

checking for memory.h... yes

checking for strings.h... yes

checking for inttypes.h... yes

checking for stdint.h... yes

checking for unistd.h... yes

checking dlfcn.h usability... yes

checking dlfcn.h presence... yes

checking for dlfcn.h... yes

checking for g++... g++

checking whether we are using the GNU C++ compiler... yes

checking whether g++ accepts -g... yes

checking dependency style of g++... gcc3

checking how to run the C++ preprocessor... g++ -E

checking for g77... no

checking for xlf... no

checking for f77... no

checking for frt... no

checking for pgf77... no

checking for cf77... no

checking for fort77... no

checking for fl32... no

checking for af77... no

checking for xlf90... no

checking for f90... no

checking for pgf90... no

checking for pghpf... no

checking for epcf90... no

checking for gfortran... no

checking for g95... no

checking for xlf95... no

checking for f95... no

checking for fort... no

checking for ifort... no

checking for ifc... no

checking for efc... no

checking for pgf95... no

checking for lf95... no

checking for ftn... no

checking whether we are using the GNU Fortran 77 compiler... no

checking whether  accepts -g... no

checking the maximum length of command line arguments... 98304

checking command to parse /usr/bin/nm -B output from gcc object... ok

checking for objdir... .libs

checking for ar... ar

checking for ranlib... ranlib

checking for strip... strip

checking if gcc supports -fno-rtti -fno-exceptions... no

checking for gcc option to produce PIC... -fPIC

checking if gcc PIC flag -fPIC works... yes

checking if gcc static flag -static works... yes

checking if gcc supports -c -o file.o... yes

checking whether the gcc linker (/usr/bin/ld) supports shared libraries... yes

checking whether -lc should be explicitly linked in... no

checking dynamic linker characteristics... GNU/Linux 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 g++... /usr/bin/ld

checking if the linker (/usr/bin/ld) is GNU ld... yes

checking whether the g++ linker (/usr/bin/ld) supports shared libraries... yes

checking for g++ option to produce PIC... -fPIC

checking if g++ PIC flag -fPIC works... yes

checking if g++ static flag -static works... yes

checking if g++ supports -c -o file.o... yes

checking whether the g++ linker (/usr/bin/ld) supports shared libraries... yes

checking dynamic linker characteristics... GNU/Linux ld.so

checking how to hardcode library paths into programs... immediate

appending configuration tag "F77" to libtool

checking for a BSD-compatible install... /usr/bin/install -c

checking for a thre

Re: (fcntl fd F_GETLK ...) from Guile

2007-09-03 Thread Kaloian Doganov
Kevin Ryde <[EMAIL PROTECTED]> writes:

If you don't mind breaking out a little C code it shouldn't be too
hard.

I don't mind, but I'm still clueless about C and don't have any
experience in extending Guile with C.


-- 
Protect your digital freedom and privacy, eliminate DRM, learn more at
http://www.defectivebydesign.org/what_is_drm



___
Guile-user mailing list
Guile-user@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-user


Re: (fcntl fd F_GETLK ...) from Guile

2007-09-03 Thread Mike Gran

--- Kaloian Doganov <[EMAIL PROTECTED]> wrote:

> I guess by "Linux" you actually mean GNU/Linux, since the make
> program
> can not run on the bare kernel.  

I knew I was going to get in trouble for that the moment I hit "send".

> Unfortunately, the configure script
> fails on my system (gNewSense):

Try this:   http://lonelycactus.com/getlk-0.1.tar.gz

Anyway, configure failed for you because it did not find the definition
of the type "off_t" in .  I changed the test to look for it
in , because that is where the LSB says it should be.

If it fails again, you should write me directly, as autoconf problems
(and my failings as a coder) are off-topic for the list. ;-)

-Mike Gran


___
Guile-user mailing list
Guile-user@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-user