From afreitas@imes.com.br Sat May 1 18:33:09 1999 Received: from imes.com.br ([200.245.82.129]) by seagull.cdrom.com (8.8.8/8.6.6) with ESMTP id SAA09318 for ; Sat, 1 May 1999 18:33:04 -0700 (PDT) Received: from l (pppremoto16 [200.245.82.112]) by imes.com.br (8.7.1/8.7.1) with ESMTP id WAA05271; Sat, 1 May 1999 22:35:22 -0300 (EST) Message-ID: <372BB91A.77927BD2@imes.com.br> Date: Sat, 01 May 1999 23:31:54 -0300 From: Aparecido Valdemir de Freitas Reply-To: afreitas@imes.com.br X-Mailer: Mozilla 4.01 [en] (Win95; I) MIME-Version: 1.0 To: clisp-list@clisp.cons.org CC: "afreitas@imes.com.br" Subject: Error CLISP Installation X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hello, I am a student of Science Computer and I intend to study Clisp. I dowloaded Clisp software from gnu.org to execute at Windows 95 environment. When I run the interpreter, the message below is displayed: Cannot reserve address range 0x1A1C0000-0x6686FFFF . GetLastError() = 0x8 (ERROR_NOT_ENOUGH_MEMORY): Not enough storage is available to process this command. C:\CLISP\CLISP-~1\LISP.EXE: Not enough memory for Lisp. Could anybody help me? Thank you. From rmz@dunk.follo.net Fri May 7 08:06:02 1999 Received: from ns1.yes.no (ns1.yes.no [195.204.136.10]) by seagull.cdrom.com (8.8.8/8.6.6) with ESMTP id IAA26979 for ; Fri, 7 May 1999 08:05:58 -0700 (PDT) Received: from dunk.follo.net (dunk.follo.net [195.204.143.225]) by ns1.yes.no (8.9.1a/8.9.1) with ESMTP id RAA28112; Fri, 7 May 1999 17:07:11 +0200 (CEST) Received: (from rmz@localhost) by dunk.follo.net (8.8.8/8.8.6) id RAA29274; Fri, 7 May 1999 17:07:11 +0200 (CEST) Date: Fri, 7 May 1999 17:07:10 +0200 From: Bjorn Remseth To: clisp-list@clisp.cons.org Cc: bjorn@yes.no Subject: Probles while building clisp-1999-01-08.tar.gz under FreeBSD 4.0 Message-ID: <19990507170710.B27266@dunk.follo.net> Reply-To: clisp-list@clisp.cons.org Mime-Version: 1.0 Content-Type: multipart/mixed; boundary=sm4nu43k4a2Rpi4c X-Mailer: Mutt 0.95.3i Organization: Yes Interactive AS --sm4nu43k4a2Rpi4c Content-Type: text/plain; charset=iso-8859-1 The command ./configure --prefix=/tmp/tmplocal crashes giving the error message ./tests > tests.out uniq -u < tests.out > tests.output.i386-unknown-freebsd4.0 test '!' -s tests.output.i386-unknown-freebsd4.0 *** Error code 1 (the full build - log is attached to this message). The FreeBSD version is FreeBSD 4.0-19990504-CURRENT (not quite bleeding edge, but pretty close ;) Does anyone have a clue about what is going on? (Rmz) --sm4nu43k4a2Rpi4c Content-Type: text/plain Content-Disposition: attachment; filename="clispmakelog.txt" executing src/configure ... creating cache ./config.cache checking for gcc... gcc checking whether the C compiler (gcc ) works... yes checking whether the C compiler (gcc ) is a cross-compiler... no checking whether we are using GNU C... yes checking how to run the C preprocessor... gcc -O -E -w checking for AIX... no checking for POSIXized ISC... no checking for minix/config.h... no checking whether using GNU C... yes checking whether using C++... no checking whether using ANSI C... yes checking whether CPP likes indented directives... yes checking whether CPP likes empty macro arguments... yes checking for underscore in external names... no checking for ranlib... ranlib checking for a BSD compatible install... cp checking how to copy files... cp -p checking whether ln -s works... yes checking how to make hard links... ln checking for getpwnam... yes checking for DYNIX/ptx libseq or libsocket... no checking whether gethostent requires -lnsl... no checking whether setsockopt requires -lsocket... no checking whether CC works at all... yes checking for broken HP/UX, A/UX, OSF/1 and NeXTstep shell... no checking host system type... i386-unknown-freebsd4.0 checking for working const... yes checking for inline... inline checking for working void... yes checking for working "return void"... yes checking for long long type... yes checking for ANSI C header files... yes checking for stdlib.h... yes checking for stddef.h... yes checking for offsetof in stddef.h... yes checking for locale.h... yes checking for unistd.h... yes checking for sys/file.h... yes checking for R_OK in unistd.h... yes checking for sys/file.h... (cached) yes checking for O_RDWR in fcntl.h... yes checking for dirent.h that defines DIR... yes checking for opendir in -ldir... no checking for sys/utsname.h and struct utsname... yes checking for netdb.h... yes checking for sys/shm.h... yes checking for sys/ipc.h... yes checking for termios.h... yes checking for termio.h... no checking for sys/termio.h... no checking for sgtty.h... yes checking for tcgetattr... yes checking for tcsetattr declaration... extern int tcsetattr (int, int, const struct termios *); checking for TCSAFLUSH in termios.h... yes checking for struct winsize... yes checking for X11 checking for xmkmf... no checking for X11 header files... checking for X11 library... checking for ANSI C header files... yes checking for size_t... yes checking for pid_t... yes checking for uid_t in sys/types.h... yes checking for off_t... yes checking for caddr_t in sys/types.h... yes checking for clock_t in sys/types.h etc.... yes checking for d_namlen in struct dirent... yes checking for struct tm in sys/time.h... yes checking for strlen declaration... extern size_t strlen (const char*); checking for memset... yes checking for memset declaration... extern char* memset (char*, int, int); checking for broken HP/UX malloc... no checking for malloc declaration... extern void* malloc (unsigned int); checking for free declaration... extern void free (void*); checking for working alloca.h... no checking for alloca... yes checking for _setjmp... yes checking for _longjmp... yes checking return type of signal handlers... void checking whether the signal handler function type needs dots... no checking for sighold... no checking for sigprocmask... yes checking for sigblock... yes checking for signal blocking interfaces... POSIX BSD checking for sigprocmask declaration... extern int sigprocmask (int, const sigset_t*, sigset_t*); checking whether signal handlers need to be reinstalled... no checking whether signals are blocked when signal handlers are entered... yes checking whether other signals are blocked when signal handlers are entered... no checking for sigaction... yes checking whether sigaction handlers need to be reinstalled... no checking whether signals are blocked when sigaction handlers are entered... yes checking for siginterrupt... yes checking for for fpu_control_t... no checking for for __setfpucw... no checking for abort declaration... extern void abort (void); checking for perror declaration... yes checking for sys_errlist declaration... extern const char* const sys_errlist[]; checking for getenv declaration... extern char* getenv (const char*); checking for putenv... yes checking for putenv declaration... extern int putenv (const char*); checking for setlocale declaration... extern char* setlocale (int, const char*); checking for setrlimit... yes checking for getrlimit declaration... extern int getrlimit (int, struct rlimit *); checking for setrlimit declaration... extern int setrlimit (int, const struct rlimit *); checking for vfork.h... no checking for working vfork... yes checking for vfork declaration... extern pid_t vfork (void); checking for setsid... yes checking for setpgid... yes checking for execv declaration... extern int execv (const char*, char* const[]); checking for execl declaration... extern int execl (const char*, const char*, ...); checking for waitpid... yes checking for waitpid declaration... extern pid_t waitpid (pid_t, int*, int); checking for sys/resource.h... yes checking for sys/times.h... yes checking for getrusage... yes checking for getrusage declaration... extern int getrusage (int, struct rusage *); checking for getcwd... yes checking for getcwd declaration... extern char* getcwd (char*, size_t); checking for chdir declaration... extern int chdir (const char*); checking for mkdir declaration... extern int mkdir (const char*, mode_t); checking for rmdir declaration... extern int rmdir (const char*); checking whether stat file-mode macros are broken... no checking for fstat declaration... extern int fstat (int, struct stat *); checking for stat declaration... extern int stat (const char*, struct stat *); checking for lstat... yes checking for lstat declaration... extern int lstat (const char*, struct stat *); checking for readlink... yes checking for readlink declaration... extern int readlink (const char*, char*, int); checking for ELOOP... yes checking for opendir declaration... extern DIR* opendir (const char*); checking for closedir declaration... extern int closedir (DIR*); checking for usable closedir return value... yes checking for open declaration... extern int open (const char*, int, ...); checking for read declaration... extern int read (int, void*, size_t); checking for write declaration... extern int write (int, const void*, size_t); checking for rename... yes checking for rename declaration... extern int rename (const char*, const char*); checking for unlink declaration... extern int unlink (const char*); checking for fsync... yes checking for ioctl declaration... extern int ioctl (int, unsigned long, ...); checking for FIONREAD... no checking for FIONREAD in sys/filio.h... yes checking for reliable FIONREAD... yes checking for fcntl declaration... extern int fcntl (int, int, ...); checking for select... yes checking for sys/select.h... yes checking for select declaration... extern int select (int, fd_set *, fd_set *, fd_set *, struct timeval *); checking for ualarm... yes checking for setitimer... yes checking for setitimer declaration... extern int setitimer (int, const struct itimerval *, struct itimerval *); checking for usleep... yes checking for localtime declaration... extern struct tm * localtime (const time_t*); checking for gettimeofday... yes checking for gettimeofday declaration... extern int gettimeofday (struct timeval *, struct timezone *); checking for ftime... no checking for getpwnam declaration... extern struct passwd * getpwnam (const char*); checking for getpwuid declaration... extern struct passwd * getpwuid (uid_t); checking for gethostname... yes checking for gethostname declaration... extern int gethostname (char*, int); checking for gethostbyname declaration... extern struct hostent * gethostbyname (const char*); checking for connect declaration... extern int connect (int, const struct sockaddr *, int); checking for sys/un.h... yes checking for sun_len in struct sockaddr_un... yes checking for netinet/in.h... yes checking for arpa/inet.h... yes checking for inet_addr declaration... extern unsigned long inet_addr (const char*); checking for netinet/tcp.h... yes checking for setsockopt declaration... extern int setsockopt (int, int, int, const void*, int); checking for the code address range... 0x08000000 checking for the malloc address range... 0x08000000 checking for the shared library address range... 0x28000000 checking for getpagesize... yes checking for getpagesize declaration... extern int getpagesize (void); checking for vadvise... yes checking for vm_allocate... no checking for sys/mman.h... yes checking for mmap... yes checking for mmap declaration... extern void* mmap (void*, size_t, int, int, int, off_t); checking for working mmap... yes checking for munmap... yes checking for msync... yes checking for mprotect... yes checking for mprotect declaration... extern int mprotect (const void*, size_t, int); checking for working mprotect... yes checking for shmget declaration... extern int shmget (key_t, int, int); checking for shmat declaration... extern void* shmat (int, void*, int); checking for shmdt declaration... extern int shmdt (void*); checking for shmctl declaration... extern int shmctl (int, int, struct shmid_ds *); checking for working shared memory... no checking for dlopen... yes checking for dlsym declaration... extern void* dlsym (void* handle, const char* symbol); checking for dlerror declaration... extern const char * dlerror (); checking for tgetent... no checking for tgetent in -ltermcap... yes checking for the valid characters in filenames... 8-bit checking for inline __builtin_strlen... yes checking for inline __builtin_strcmp... no checking whether characters are unsigned... no checking for integer types and behaviour creating intparam.h updating cache ./config.cache creating ./config.status creating makemake creating unixconf.h executing src/readline/configure ... loading cache ../config.cache checking for gcc... (cached) gcc -O checking whether the C compiler (gcc -O ) works... yes checking whether the C compiler (gcc -O ) is a cross-compiler... no checking whether we are using GNU C... (cached) yes checking how to run the C preprocessor... (cached) gcc -O -E -w checking whether -traditional is needed for gcc -O on this system... no checking for ranlib... (cached) ranlib checking for a BSD compatible install... (cached) cp checking for AIX... (cached) no checking for POSIXized ISC... (cached) no checking for minix/config.h... (cached) no checking for working const... (cached) yes checking for inline... (cached) inline checking for working void... yes checking for ANSI C header files... (cached) yes checking for unistd.h... (cached) yes checking for sys/file.h... (cached) yes checking for O_RDWR in fcntl.h... (cached) yes checking for dirent.h that defines DIR... (cached) yes checking for opendir in -ldir... (cached) no checking for stdarg.h... yes checking for varargs.h... yes checking for termios.h... (cached) yes checking for termio.h... (cached) no checking for sys/termio.h... (cached) no checking for sgtty.h... (cached) yes checking for tcgetattr... yes checking for tcflow... yes checking for sys/stream.h... no checking for sys/ptem.h... no checking for FIONREAD... no checking for FIONREAD in sys/filio.h... yes checking for select... (cached) yes checking for sys/select.h... (cached) yes checking for working alloca.h... no checking for alloca... yes checking for strchr... yes checking for strrchr... yes checking for strpbrk... yes checking return type of signal handlers... void checking for sighold... (cached) no checking for sigprocmask... (cached) yes checking for sigblock... (cached) yes checking for signal blocking interfaces... (cached) POSIX BSD checking whether signal handlers need to be reinstalled... (cached) no checking whether signals are blocked when signal handlers are entered... (cached) yes checking for sigaction... (cached) yes checking for uid_t in sys/types.h... (cached) yes checking for getpwuid declaration... (cached) extern struct passwd * getpwuid (uid_t); updating cache ../config.cache creating ./config.status creating Makefile creating config.h executing src/newreadline/configure ... loading cache ../config.cache checking for gcc... (cached) gcc -O checking whether the C compiler (gcc -O -g ) works... yes checking whether the C compiler (gcc -O -g ) is a cross-compiler... no checking whether we are using GNU C... (cached) yes checking how to run the C preprocessor... (cached) gcc -O -E -w checking whether -traditional is needed for gcc -O on this system... (cached) no checking for a BSD compatible install... (cached) cp checking for ranlib... (cached) ranlib checking for working void... (cached) yes checking for strcasecmp... yes checking for select... (cached) yes checking for strpbrk... (cached) yes checking for unistd.h... (cached) yes checking for stdlib.h... (cached) yes checking for varargs.h... (cached) yes checking for string.h... yes checking for alloca.h... (cached) no checking for dirent.h... yes checking for sys/ptem.h... (cached) no checking for sys/pte.h... no checking for sys/stream.h... (cached) no checking for termcap.h... yes checking for sys/select.h... yes checking for sys/file.h... (cached) yes checking for O_RDWR in fcntl.h... (cached) yes checking for dirent.h that defines DIR... (cached) yes checking for opendir in -ldir... (cached) no checking for termios.h... (cached) yes checking for termio.h... (cached) no checking for sys/termio.h... (cached) no checking for sgtty.h... (cached) yes checking for tcgetattr... (cached) yes checking for tcflow... (cached) yes checking for sys/stream.h... (cached) no checking for sys/ptem.h... (cached) no checking for FIONREAD... (cached) no checking for FIONREAD in sys/filio.h... (cached) yes checking for TIOCGWINSZ in sys/ioctl.h... yes checking for programs able to redeclare getpw functions... yes checking for working alloca.h... (cached) no checking for alloca... (cached) yes checking for sighold... (cached) no checking for sigprocmask... (cached) yes checking for sigblock... (cached) yes checking for signal blocking interfaces... (cached) POSIX BSD updating cache ../config.cache creating ./config.status creating Makefile creating config.h executing src/newnewreadline/configure ... creating cache ./config.cache checking host system type... i386-pc-freebsd4.0 checking for gcc... gcc checking whether the C compiler (gcc -g ) works... yes checking whether the C compiler (gcc -g ) is a cross-compiler... no checking whether we are using GNU C... yes checking whether gcc accepts -g... yes checking how to run the C preprocessor... gcc -E checking for minix/config.h... no checking whether gcc needs -traditional... no checking for a BSD compatible install... /usr/bin/install -c checking for ranlib... ranlib checking return type of signal handlers... void checking whether stat file-mode macros are broken... no checking for dirent.h that defines DIR... yes checking for opendir in -ldir... no checking for strcasecmp... yes checking for select... yes checking for setenv... yes checking for putenv... yes checking for tcgetattr... yes checking for setlocale... yes checking for lstat... yes checking for working strcoll... yes checking for unistd.h... yes checking for stdlib.h... yes checking for varargs.h... yes checking for stdarg.h... yes checking for string.h... yes checking for sys/ptem.h... no checking for sys/pte.h... no checking for sys/stream.h... no checking for sys/select.h... yes checking for termcap.h... yes checking for termios.h... yes checking for termio.h... no checking for sys/file.h... yes checking for locale.h... yes checking for type of signal functions... posix checking if signal handlers must be reinstalled when invoked... no checking for presence of POSIX-style sigsetjmp/siglongjmp... present checking for lstat... yes checking whether programs are able to redeclare getpw functions... yes checking whether or not strcoll and strcmp differ... no checking whether signal handlers are of type void... yes checking for TIOCGWINSZ in sys/ioctl.h... yes checking for TIOCSTAT in sys/ioctl.h... yes checking for FIONREAD in sys/ioctl.h... yes checking for speed_t in sys/types.h... no checking for struct winsize in sys/ioctl.h and termios.h... sys/ioctl.h checking if struct dirent has a d_ino member... yes checking if struct dirent has a d_fileno member... yes checking for tgetent in -ltermcap... yes checking which library has the termcap functions... using libtermcap updating cache ./config.cache creating ./config.status creating Makefile creating doc/Makefile creating examples/Makefile creating config.h executing src/gettext/configure ... loading cache ../config.cache checking whether build environment is sane... yes checking whether make sets $(MAKE)... yes checking for gcc... (cached) gcc -O checking whether the C compiler (gcc -O ) works... yes checking whether the C compiler (gcc -O ) is a cross-compiler... no checking whether we are using GNU C... (cached) yes checking how to run the C preprocessor... (cached) gcc -O -E -w checking for ranlib... (cached) ranlib checking for a BSD compatible install... (cached) cp checking for POSIXized ISC... (cached) no checking for ANSI C header files... (cached) yes checking for working const... (cached) yes checking for inline... (cached) inline checking for off_t... (cached) yes checking for size_t... (cached) yes checking for working alloca.h... (cached) no checking for alloca... (cached) yes checking for unistd.h... (cached) yes checking for getpagesize... yes checking for working mmap... yes checking for argz.h... no checking for limits.h... yes checking for locale.h... (cached) yes checking for nl_types.h... yes checking for malloc.h... yes checking for string.h... (cached) yes checking for unistd.h... (cached) yes checking for sys/param.h... yes checking for getcwd... yes checking for munmap... (cached) yes checking for putenv... (cached) yes checking for setenv... yes checking for setlocale... yes checking for strchr... (cached) yes checking for strcasecmp... (cached) yes checking for strdup... yes checking for __argz_count... no checking for __argz_stringify... no checking for __argz_next... no checking for stpcpy... no checking for LC_MESSAGES... yes checking whether NLS is requested... yes checking whether included gettext is requested... yes checking for msgfmt... msgfmt checking for gmsgfmt... msgfmt checking for xgettext... : checking for catalogs to be installed... en de fr es updating cache ../config.cache creating ./config.status creating intl/Makefile creating intl/intlh.inst creating po/Makefile creating config.h linking ./intl/libgettext.h to intl/libintl.h executing src/avcall/configure ... loading cache ../config.cache checking for gcc... (cached) gcc -O checking whether the C compiler (gcc -O ) works... yes checking whether the C compiler (gcc -O ) is a cross-compiler... no checking whether we are using GNU C... (cached) yes checking how to run the C preprocessor... (cached) gcc -O -E -w checking whether -traditional is needed for gcc -O on this system... (cached) no checking for underscore in external names... (cached) no checking for ranlib... (cached) ranlib checking whether make sets $(MAKE)... (cached) yes checking for a BSD compatible install... (cached) cp checking host system type... (cached) i386-unknown-freebsd4.0 checking for pcc non-reentrant struct return convention... no checking whether small structs are returned in registers... yes checking for long long type... (cached) yes updating cache ../config.cache creating ./config.status creating Makefile creating avcall.h executing src/callback/configure ... loading cache ../config.cache checking for gcc... (cached) gcc -O checking whether the C compiler (gcc -O ) works... yes checking whether the C compiler (gcc -O ) is a cross-compiler... no checking whether we are using GNU C... (cached) yes checking how to run the C preprocessor... (cached) gcc -O -E -w checking whether -traditional is needed for gcc -O on this system... (cached) no checking for ranlib... (cached) ranlib checking whether make sets $(MAKE)... (cached) yes checking for a BSD compatible install... (cached) cp checking whether ln -s works... (cached) yes checking host system type... (cached) i386-unknown-freebsd4.0 updating cache ../config.cache creating ./config.status creating Makefile configuring in vacall_r running /bin/sh ../../../ffcall/callback/vacall_r/configure --prefix=/tmp/tmplocal --cache-file=../../config.cache --srcdir=../../../ffcall/callback/vacall_r loading cache ../../config.cache checking for gcc... (cached) gcc -O checking whether the C compiler (gcc -O ) works... yes checking whether the C compiler (gcc -O ) is a cross-compiler... no checking whether we are using GNU C... (cached) yes checking how to run the C preprocessor... (cached) gcc -O -E -w checking whether -traditional is needed for gcc -O on this system... (cached) no checking for underscore in external names... (cached) no checking for ranlib... (cached) ranlib checking whether make sets $(MAKE)... (cached) yes checking for a BSD compatible install... (cached) cp checking for stdlib.h... (cached) yes checking for abort declaration... (cached) extern void abort (void); checking host system type... (cached) i386-unknown-freebsd4.0 checking for pcc non-reentrant struct return convention... (cached) no checking whether small structs are returned in registers... (cached) yes checking for long long type... (cached) yes checking whether characters are unsigned... (cached) no updating cache ../../config.cache creating ./config.status creating Makefile creating vacall_r.h creating config.h configuring in trampoline_r running /bin/sh ../../../ffcall/callback/trampoline_r/configure --prefix=/tmp/tmplocal --cache-file=../../config.cache --srcdir=../../../ffcall/callback/trampoline_r loading cache ../../config.cache checking for gcc... (cached) gcc -O checking whether the C compiler (gcc -O ) works... yes checking whether the C compiler (gcc -O ) is a cross-compiler... no checking whether we are using GNU C... (cached) yes checking how to run the C preprocessor... (cached) gcc -O -E -w checking whether -traditional is needed for gcc -O on this system... (cached) no checking for underscore in external names... (cached) no checking for ranlib... (cached) ranlib checking whether make sets $(MAKE)... (cached) yes checking for a BSD compatible install... (cached) cp checking whether ln -s works... (cached) yes checking for working void... (cached) yes checking for working "return void"... (cached) yes checking for ANSI C header files... (cached) yes checking for stdlib.h... (cached) yes checking for unistd.h... (cached) yes checking for ANSI C header files... (cached) yes checking for size_t... (cached) yes checking for off_t... (cached) yes checking for malloc declaration... (cached) extern void* malloc (unsigned int); checking for free declaration... (cached) extern void free (void*); checking for abort declaration... (cached) extern void abort (void); checking for mkdir declaration... (cached) extern int mkdir (const char*, mode_t); checking for open declaration... (cached) extern int open (const char*, int, ...); checking for getpagesize... (cached) yes checking for getpagesize declaration... (cached) extern int getpagesize (void); checking for vm_allocate... (cached) no checking for sys/file.h... (cached) yes checking for O_RDWR in fcntl.h... (cached) yes checking for sys/mman.h... (cached) yes checking for mmap... (cached) yes checking for mmap declaration... (cached) extern void* mmap (void*, size_t, int, int, int, off_t); checking for working mmap... (cached) yes checking for mprotect... (cached) yes checking for mprotect declaration... (cached) extern int mprotect (const void*, size_t, int); checking for working mprotect... (cached) yes checking for sys/shm.h... (cached) yes checking for sys/ipc.h... (cached) yes checking for shmget declaration... (cached) extern int shmget (key_t, int, int); checking for shmat declaration... (cached) extern void* shmat (int, void*, int); checking for shmdt declaration... (cached) extern int shmdt (void*); checking for shmctl declaration... (cached) extern int shmctl (int, int, struct shmid_ds *); checking for working shared memory... (cached) no checking host system type... (cached) i386-unknown-freebsd4.0 checking whether code in malloc'ed memory is executable... yes updating cache ../../config.cache creating ./config.status creating Makefile creating config.h executing src/sigsegv/configure ... loading cache ../config.cache checking for gcc... (cached) gcc -O checking whether the C compiler (gcc -O ) works... yes checking whether the C compiler (gcc -O ) is a cross-compiler... no checking whether we are using GNU C... (cached) yes checking how to run the C preprocessor... (cached) gcc -O -E -w checking for AIX... (cached) no checking for POSIXized ISC... (cached) no checking for minix/config.h... (cached) no checking whether CC works at all... (cached) yes checking for ranlib... (cached) ranlib checking for a BSD compatible install... (cached) cp checking for sys/file.h... (cached) yes checking for O_RDWR in fcntl.h... (cached) yes checking for memset... (cached) yes checking for memset declaration... (cached) extern char* memset (char*, int, int); checking for malloc declaration... (cached) extern void* malloc (unsigned int); checking return type of signal handlers... (cached) void checking whether the signal handler function type needs dots... (cached) no checking for sighold... (cached) no checking for sigprocmask... (cached) yes checking for sigblock... (cached) yes checking for signal blocking interfaces... (cached) POSIX BSD checking whether signal handlers need to be reinstalled... (cached) no checking whether signals are blocked when signal handlers are entered... (cached) yes checking whether other signals are blocked when signal handlers are entered... (cached) no checking for sigaction... (cached) yes checking whether sigaction handlers need to be reinstalled... (cached) no checking whether signals are blocked when sigaction handlers are entered... (cached) yes checking for siginterrupt... (cached) yes checking for getpagesize... (cached) yes checking for getpagesize declaration... (cached) extern int getpagesize (void); checking for vadvise... (cached) yes checking for vm_allocate... (cached) no checking for ANSI C header files... (cached) yes checking for size_t... (cached) yes checking for off_t... (cached) yes checking for sys/mman.h... (cached) yes checking for mmap... (cached) yes checking for mmap declaration... (cached) extern void* mmap (void*, size_t, int, int, int, off_t); checking for working mmap... (cached) yes checking for mprotect... (cached) yes checking for mprotect declaration... (cached) extern int mprotect (const void*, size_t, int); checking for working mprotect... (cached) yes updating cache ../config.cache creating ./config.status creating Makefile creating config.h gcc -O -E -w `if test false = true; then echo '-DASM_UNDERSCORE'; fi` ../../ffcall/avcall/avcall-i386.S | grep -v '^ *#line' | grep -v '^#ident' | grep -v '^#' | sed -e 's,% ,%,g' > avcall-i386.s gcc -O -c avcall-i386.s rm -f avcall.o ln avcall-i386.o avcall.o gcc -O -c ../../ffcall/avcall/structcpy.c rm -f libavcall.a ar rc libavcall.a avcall.o structcpy.o ranlib libavcall.a cd vacall_r; make all gcc -O -E -w `if test false = true; then echo '-DASM_UNDERSCORE'; fi` ../../../ffcall/callback/vacall_r/vacall-i386.S | grep -v '^ *#line' | grep -v '^#ident' | grep -v '^#' | sed -e 's,% ,%,g' > vacall-i386.s gcc -O -c vacall-i386.s rm -f vacall.o ln vacall-i386.o vacall.o gcc -O -I. -I../../../ffcall/callback/vacall_r -c ../../../ffcall/callback/vacall_r/misc.c gcc -O -c ../../../ffcall/callback/vacall_r/structcpy.c rm -f libvacall.a ar rc libvacall.a vacall.o misc.o structcpy.o ranlib libvacall.a cd trampoline_r; make all ln -s ../../../ffcall/callback/trampoline_r/trampoline_r.h.in trampoline_r.h gcc -O -I. -I../../../ffcall/callback/trampoline_r -c ../../../ffcall/callback/trampoline_r/trampoline.c rm -f libtrampoline.a ar rc libtrampoline.a trampoline.o ranlib libtrampoline.a ln -s ../../ffcall/callback/callback.h.in callback.h ln -s vacall_r/vacall_r.h vacall_r.h ln -s trampoline_r/trampoline_r.h trampoline_r.h rm -f libcallback.a mkdir libtmpdir cd libtmpdir; ar x ../vacall_r/libvacall.a && rm -f ________64ELEL_ cd libtmpdir; ar x ../trampoline_r/libtrampoline.a && rm -f ________64ELEL_ cd libtmpdir; ar rc ../libcallback.a *.o rm -f -r libtmpdir ranlib libcallback.a gcc -O -I. -I../../ffcall/avcall -c ../../ffcall/avcall/tests.c gcc -O tests.o avcall.o structcpy.o -o tests ./tests > tests.out uniq -u < tests.out > tests.output.i386-unknown-freebsd4.0 test '!' -s tests.output.i386-unknown-freebsd4.0 *** Error code 1 Stop. --sm4nu43k4a2Rpi4c-- From haible@ilog.fr Fri May 7 10:42:48 1999 Received: from sceaux.ilog.fr (sceaux.ilog.fr [193.55.64.10]) by seagull.cdrom.com (8.8.8/8.6.6) with ESMTP id KAA29214 for ; Fri, 7 May 1999 10:42:47 -0700 (PDT) Received: from laposte.ilog.fr (laposte [172.17.1.6]) by sceaux.ilog.fr (8.9.1/8.9.1) with ESMTP id TAA09098 for ; Fri, 7 May 1999 19:43:49 +0200 (MET DST) Received: from jaures.ilog.fr ([172.17.4.95]) by laposte.ilog.fr (8.9.3/8.9.3) with ESMTP id TAA11696; Fri, 7 May 1999 19:43:49 +0200 (MET DST) From: Bruno Haible Received: (from haible@localhost) by jaures.ilog.fr (8.9.3/8.9.3) id TAA08749; Fri, 7 May 1999 19:43:31 +0200 (MET DST) Date: Fri, 7 May 1999 19:43:31 +0200 (MET DST) Message-Id: <199905071743.TAA08749@jaures.ilog.fr> To: clisp-list@seagull.cons.org Subject: Re: Probles while building clisp-1999-01-08.tar.gz under FreeBSD 4.0 In-Reply-To: <19990507170710.B27266@dunk.follo.net> References: <19990507170710.B27266@dunk.follo.net> Bjorn Remseth writes: > The command > > ./configure --prefix=/tmp/tmplocal > > crashes giving the error message > > ./tests > tests.out > uniq -u < tests.out > tests.output.i386-unknown-freebsd4.0 > test '!' -s tests.output.i386-unknown-freebsd4.0 > *** Error code 1 This is an error in a subordinate "make", executed in a subshell, and means only that the FFI will not be included. (ffcall needs to be updated for FreeBSD-gcc's calling convention.) Normally, `configure' would print the following lines: To continue building CLISP, the following commands are recommended (cf. unix/INSTALL step 4): cd /tmp/tmplocal ./makemake --with-readline --with-gettext > Makefile make make check If `configure' does not print that, it's because of a /bin/sh bug. If you execute CONFIG_SHELL=/bin/bash export CONFIG_SHELL $CONFIG_SHELL configure --prefix=/tmp/tmplocal you will not have this problem. (At least that's the experience I made on MacOS X Server.) It would be good if someone tracked this down and submitted a bug report to the FreeBSD /bin/sh maintainer. Bruno From amoroso@mclink.it Mon May 10 09:25:59 1999 Received: from mail1.mclink.it (net128-007.mclink.it [195.110.128.7]) by seagull.cdrom.com (8.8.8/8.6.6) with ESMTP id JAA09372 for ; Mon, 10 May 1999 09:25:58 -0700 (PDT) Received: from net145-124.mclink.it (net145-124.mclink.it [195.110.145.124]) by mail1.mclink.it (8.9.1/8.9.0) with SMTP id SAA17658 for ; Mon, 10 May 1999 18:27:31 +0200 (CEST) From: amoroso@mclink.it (Paolo Amoroso) To: clisp-list@clisp.cons.org Subject: Garnet questions and problems Date: Mon, 10 May 1999 16:30:01 GMT Organization: Paolo Amoroso - Milan, ITALY Message-ID: <373707c8.30406@mail.mclink.it> X-Mailer: Forte Agent 1.5/32.451 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit I use CLISP 1999.01.08, built from source with the included NCLX module, under Red Hat Linux 5.2. I have installed the Garnet 3.0 distribution for CLISP available at CONS.ORG. I have followed the directions provided in the Garnet documentation, including the ones specific to CLISP. Of course I didn't need to rename the source files. I have also set *WARN-ON-FLOATING-POINT-CONTAGION* to NIL before compilation to avoid being flooded by warnings when later running the demos. I have found that in garnet-loader.lsp there is no CLISP specific value for *DEFAULT-GARNET-PROCLAIM*. I guess this reflected the state of CLISP when Garnet 3.0 was released several years ago. Are there optimization settings worth considering with recent versions of CLISP such as the one I'm using? As suggested by the documentation, I have dumped a Garnet image that I start with an appropriate script. Do I still need to run the garnet-after-compile script? Can I delete the Lisp sources and binaries when they are non longer needed? When I start the Garnet image, I get the following error: [paolo@localhost paolo]$ garnet i i i i i i i ooooo o ooooooo ooooo ooooo I I I I I I I 8 8 8 8 8 o 8 8 I I I I I I I 8 8 8 8 8 8 I I I I I I I 8 8 8 ooooo 8oooo I \ `+' / I 8 8 8 8 8 \ `-+-' / 8 o 8 8 o 8 8 `-__|__-' ooooo 8oooooo ooo8ooo ooooo 8 | ------+------ Copyright (c) Bruno Haible, Michael Stoll 1992, 1993 Copyright (c) Bruno Haible, Marcus Daniels 1994-1997 Copyright (c) Pierpaolo Bernardi, Sam Steingold 1998 *** Restarting Garnet 3.0 image created with opal:make-image *** *** Image creation date: May 10, 1999, 3:17 PM *** *** - FUNCALL: the function #:|(SETF XLIB:DISPLAY-REPORT-ASYNCHRONOUS-ERRORS)| is undefined As far as I can tell, that function is present in the XLIB package: 1. Break [7]> (apropos "DISPLAY-REPORT-ASYNCHRONOUS-ERRORS") XLIB:DISPLAY-REPORT-ASYNCHRONOUS-ERRORS function XLIB::DISPLAY-REPORT-ASYNCHRONOUS-ERRORS-SETTER function It seems that the only reference to XLIB:DISPLAY-REPORT-ASYNCHRONOUS-ERRORS is in src/opal/x.lsp: [...] ;;; RETURNS: ;;; normally NIL; returns T if: ;;; - the property is :WIDTH or :HEIGHT and a new buffer is required because ;;; the old one was too small; or ;;; - the property is :VISIBLE and the window needs to be mapped. ;;; (defun x-set-window-property (window property value) (case property (:BACKGROUND-COLOR ...) ;; ... (:REPORT-ASYNCHRONOUS-ERRORS (setf (xlib:display-report-asynchronous-errors opal::*default-x-display*) value)) ;; ... (T (format t "Unknown property ~S in gem:x-set-window-property.~%" property)))) [...] After the above mentioned error, however, I am able to use Garnet anyway--e.g. for loading the demos--by switching to the USER package and evaluating the appropriate forms: 1. Break [7]> abort [8]> *package* # [9]> (garnet-load "demos:demos-controller") *** - EVAL: the function GARNET-LOAD is undefined 1. Break [10]> abort [11]> (in-package :user) # USER[12]> (garnet-load "demos:demos-controller") Loading #P"/usr/local/lib/clisp/garnet/src/demos/demos-controller" [...] A few demos--e.g. angle, scrollbar and unidraw--still do not work, but this is a minor problem. Do you have any suggestions for solving the problem with the Garnet image and DISPLAY-REPORT-ASYNCHRONOUS-ERRORS? Paolo -- Paolo Amoroso From jcgroult@etu.info.unicaen.fr Thu May 13 15:10:44 1999 Received: from asterix.etu.info.unicaen.fr (asterix.etu.info.unicaen.fr [193.55.130.51]) by seagull.cdrom.com (8.8.8/8.6.6) with ESMTP id PAA19366 for ; Thu, 13 May 1999 15:10:43 -0700 (PDT) Received: from obelix.etu.info.unicaen.fr (obelix [193.55.130.26]) by asterix.etu.info.unicaen.fr (8.9.0.Beta5/8.9.0.Beta5) with ESMTP id AAA16349 for ; Fri, 14 May 1999 00:10:55 +0200 (MET DST) Received: from localhost (jcgroult@localhost) by obelix.etu.info.unicaen.fr (8.8.8+Sun/8.8.8) with SMTP id AAA29594 for ; Fri, 14 May 1999 00:10:49 +0200 (MET DST) Date: Fri, 14 May 1999 00:10:49 +0200 (MET DST) From: Jean-Christophe Groult To: clisp-list Subject: creating metaclass Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Transfer-Encoding: QUOTED-PRINTABLE Hello, I am student and I work on a projet written in CLOS. I need some class which should have some slots which are themselves instances of class. The trouble is to make instances of slots *automatically*.=20 I believe metaclass could solve this. What I want to do, is something like below : (defclass my-metaclass (standard-class) ( ... maybe some slots here ...) ) =2E.. some method here. Probably initialize-instance :around (or :after) (defclass slots-classA (...) (...) ) =2E.. some method ... (defclass slots-classB (...) (...) ) =2E.. some method ... (defclass first-class (some-superclass) ((slotA :type slots-classA) (slotC :initarg :C)) (:metaclass my-metaclass)) =2E.. some method ... (defclass second-class (some-superclass) ((slotA :type slots-classA) (slotB :type slots-classB) (other-slotB :type slot-classB)) (:metaclass my-metaclass) ) =2E.. some method ... ;and then (setf foo (make-instance 'first-class)) =3D> automatic call of (setf slotA (make-instance 'slots-classA)) nothing for slotC (setf bar (make-instance 'second-class)) =3D> automatic call of (setf slotA (make-instance 'slots-classA)) =3D> automatic call of (setf slotB (make-instance 'slots-classB)) =3D> automatic call of (setf other-slotB (make-instance 'slots-classB)) So, I have few questions now ;-) How to create a metaclass ! ? I have some examples in a (bit old) book. But they don't work, even this simple one : [1]> (defclass foo (standard-class) () ) *** - DEFCLASS FOO: superclass # should belong to class STANDARD-CLASS 1. Break [2]>=20 standard-class is not the goog one, so which one should I use ? And how can I get the value associated whith the :type keyword ? Can I have some trouble using an already defined keyword ? Is it better to use a new one ? If someone have experience with metaclass, or some working examples: please, help ! :-) thanks for having read all, JC Jean-Christophe GROULT mail : jcgroult@etu.info.unicaen.fr DEA informatique Universite de CAEN =C9viter le d=E9shonneur est un fait ind=E9pendant de la victoire ou de la = d=E9faite From haible@ilog.fr Fri May 14 05:33:31 1999 Received: from sceaux.ilog.fr (sceaux.ilog.fr [193.55.64.10]) by seagull.cdrom.com (8.8.8/8.6.6) with ESMTP id FAA02923 for ; Fri, 14 May 1999 05:33:30 -0700 (PDT) Received: from laposte.ilog.fr (laposte [172.17.1.6]) by sceaux.ilog.fr (8.9.1/8.9.1) with ESMTP id OAA15625 for ; Fri, 14 May 1999 14:33:44 +0200 (MET DST) Received: from jaures.ilog.fr ([172.17.4.45]) by laposte.ilog.fr (8.9.3/8.9.3) with ESMTP id OAA04668; Fri, 14 May 1999 14:33:44 +0200 (MET DST) From: Bruno Haible Received: (from haible@localhost) by jaures.ilog.fr (8.9.3/8.9.3) id OAA22931; Fri, 14 May 1999 14:33:23 +0200 (MET DST) Date: Fri, 14 May 1999 14:33:23 +0200 (MET DST) Message-Id: <199905141233.OAA22931@jaures.ilog.fr> To: clisp-list@seagull.cons.org Subject: Re: creating metaclass In-Reply-To: References: Jean-Christophe Groult writes: > [1]> (defclass foo (standard-class) () ) > > *** - DEFCLASS FOO: superclass # should > belong to class STANDARD-CLASS > 1. Break [2]>=20 > > standard-class is not the goog one, so which one should I use ? In clisp, since the superclass `standard-class' is of metaclass structure-class, you also need to make `foo' of metaclass structure-class: (defclass foo (standard-class) () #+clisp (:metaclass structure-class)) > If someone have experience with metaclass, or some working examples: > please, help ! :-) The following sample is contained in clisp's testsuite (and was taken from closette's testsuite): (defclass rectangle2 () ((x :initform 0.0 :initarg x) (y :initform 0.0 :initarg y))) (defclass counted2-class (standard-class) ((counter :initform 0)) #+CLISP (:metaclass structure-class)) (defclass counted2-rectangle (rectangle2) () (:metaclass counted2-class)) (defmethod make-instance :after ((c counted2-class) &rest args) (incf (slot-value c 'counter))) (slot-value (find-class 'counted2-rectangle) 'counter) (make-instance 'counted2-rectangle) (slot-value (find-class 'counted2-rectangle) 'counter) Bruno From abecerra@iie.ufro.cl Sat May 15 08:34:12 1999 Received: from lautaro.enlaces.ufro.cl (lautaro.enlaces.ufro.cl [200.13.0.1]) by seagull.cdrom.com (8.8.8/8.6.6) with ESMTP id IAA22747 for ; Sat, 15 May 1999 08:34:08 -0700 (PDT) Received: from doc92.dis.ufro.cl ([200.10.21.91]) by lautaro.enlaces.ufro.cl (8.8.8/8.8.8) with SMTP id MAA00553 for ; Sat, 15 May 1999 12:32:53 -0400 (SAT) Message-ID: <002101be9ee0$3c0e8500$5b150ac8@doc92.dis.ufro.cl> From: "Anita Lilian Becerra Lagos" To: Subject: FTP site Common Lisp for MS-DOS Date: Sat, 15 May 1999 11:35:52 -0300 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_001E_01BE9EC7.165C97C0" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.2106.4 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 This is a multi-part message in MIME format. ------=_NextPart_000_001E_01BE9EC7.165C97C0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi =20 I =B4m interesting in Common Lisp for MS-DOS I have=20 CLISP 1 "15 June 1995" but I have a problem=20 this re-booting the computer=20 and too , I have=20 clisp-win32.zip =20 but this say: Cannot reserve address range 0x1A1C0000-0x6686FFFF . GetLastError() =3D = 0x8 (ERROR_NOT_ENOUGH_MEMORY): Not enough storage is available to = process this command. C:\CLISP\CLISP-~1\LISP.EXE: Not enough memory for Lisp. somebody knows Compiler for Common Lisp in Ms-DOS of FTP site for I download Thanks Anita. ------=_NextPart_000_001E_01BE9EC7.165C97C0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Hi
 
I ´m interesting in Common Lisp  for=20 MS-DOS
I have

CLISP 1 "15 June 1995"

but I have a problem
this
re-booting the computer
 
 
and too , I have
clisp-win32.zip  
but this say:
Cannot reserve address range 0x1A1C0000-0x6686FFFF . GetLastError() = =3D 0x8=20 (ERROR_NOT_ENOUGH_MEMORY): Not enough storage is available to process = this=20 command.
C:\CLISP\CLISP-~1\LISP.EXE: Not enough memory for = Lisp.
 
somebody knows Compiler for Common Lisp in Ms-DOS of FTP site
for I download
 
Thanks
 
Anita.
------=_NextPart_000_001E_01BE9EC7.165C97C0-- From abecerra@iie.ufro.cl Sat May 15 08:45:20 1999 Received: from lautaro.enlaces.ufro.cl (lautaro.enlaces.ufro.cl [200.13.0.1]) by seagull.cdrom.com (8.8.8/8.6.6) with ESMTP id IAA23162 for ; Sat, 15 May 1999 08:45:16 -0700 (PDT) Received: from doc92.dis.ufro.cl ([200.10.21.91]) by lautaro.enlaces.ufro.cl (8.8.8/8.8.8) with SMTP id MAA00655 for ; Sat, 15 May 1999 12:43:40 -0400 (SAT) Message-Id: <3.0.6.32.19990515114639.0081ec80@iie.ufro.cl> X-Sender: abecerra@iie.ufro.cl X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.6 (32) Date: Sat, 15 May 1999 11:46:39 -0300 To: clisp-list@clisp.cons.org From: Anita Lilian Becerra Lagos Subject: Common Lisp for Ms-DOS Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi =20 I =B4m interesting in Common Lisp for MS-DOS I have=20 CLISP 1 "15 June 1995" but I have a problem=20 this re-booting the computer=20 =20 =20 and too , I have=20 clisp-win32.zip =20 but this say: Cannot reserve address range 0x1A1C0000-0x6686FFFF . GetLastError() =3D 0x8 (ERROR_NOT_ENOUGH_MEMORY): Not enough storage is available to process this command. C:\CLISP\CLISP-~1\LISP.EXE: Not enough memory for Lisp. =20 somebody knows Compiler for Common Lisp in Ms-DOS of FTP site for I download =20 Thanks =20 Anita. From arvo@goblin.cs.caltech.edu Fri May 21 18:35:40 1999 Received: from csvax.cs.caltech.edu (csvax.cs.caltech.edu [131.215.131.131]) by seagull.cdrom.com (8.8.8/8.6.6) with ESMTP id SAA10994 for ; Fri, 21 May 1999 18:35:39 -0700 (PDT) Received: from goblin.cs.caltech.edu (goblin.cs.caltech.edu [131.215.131.116]) by csvax.cs.caltech.edu (8.9.1/8.9.1) with SMTP id SAA14937 for ; Fri, 21 May 1999 18:37:00 -0700 (PDT) Received: (from arvo@localhost) by goblin.cs.caltech.edu (950413.SGI.8.6.12/950213.SGI.AUTOCF) id SAA12923 for clisp-list@clisp.cons.org; Fri, 21 May 1999 18:58:42 -0700 From: "Jim Arvo" Message-Id: <9905211858.ZM12921@goblin.cs.caltech.edu> Date: Fri, 21 May 1999 18:58:42 -0700 X-Mailer: Z-Mail (3.2.3 08feb96 MediaMail) To: clisp-list@clisp.cons.org Subject: clisp & sockets Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii I wish to run clisp in a separate process (perhaps on another machine), and communicate with it from C++. I understand that on Unix platforms the correct way to go about this is via sockets, but I need some help getting started. I have several questions: 1) When I evaluate (socket-server 1), I get the error message *** - UNIX error 13 (EACCES): Permission denied Are there some magic port numbers I need to use? (I've tried a bunch.) Must the Lisp process be running as root? 2) Can someone point me to a VERY SIMPLE example of a C or C++ program that communicates with a Lisp environment via sockets? I'm sure this is quite easy -- I just need a trivial example to start with. 3) Are there any publicly-available Lisp packages (with corresponding C libraries) that provide a higher-level communication layer than sockets? Any advice/information would be greatly appreciated. Thanks. -- Jim Arvo From ecm@savage.iut-blagnac.fr Sun May 23 07:08:55 1999 Received: from savage.iut-blagnac.fr (savage.iut-blagnac.fr [193.54.227.231]) by seagull.cdrom.com (8.8.8/8.6.6) with ESMTP id HAA27300 for ; Sun, 23 May 1999 07:08:53 -0700 (PDT) Received: by savage.iut-blagnac.fr via sendmail from stdin id (Debian Smail3.2.0.101) for clisp-list@seagull.cons.org; Sun, 23 May 1999 16:10:20 +0200 (CEST) Date: Sun, 23 May 1999 16:10:20 +0200 From: Eric Marsden To: clisp-list@seagull.cons.org Subject: Re: clisp & sockets Message-ID: <19990523161020.A24139@savage.iut-blagnac.fr> References: <9905211858.ZM12921@goblin.cs.caltech.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i In-Reply-To: <9905211858.ZM12921@goblin.cs.caltech.edu>; from Jim Arvo on Fri, May 21, 1999 at 06:38:09PM -0700 X-Attribution: ecm X-Eric-Conspiracy: There is no conspiracy. Organization: disorganized On Fri, May 21, 1999 at 06:38:09PM -0700, Jim Arvo wrote: > 1) When I evaluate (socket-server 1), I get the error message > > *** - UNIX error 13 (EACCES): Permission denied > > Are there some magic port numbers I need to use? (I've tried a bunch.) > Must the Lisp process be running as root? Under Unix, binding to a port number under 1024 requires root priviledges (and a number of the numbers have predefined meanings; see /etc/services). As a user you can bind to anything above, but note that you can't count on being able to use a specific number (as is generally necessary, since your C program has to know in advance which port to connect to), because another program may have had that port attributed to it by the system for a client request. You may find the following sites useful: > 2) Can someone point me to a VERY SIMPLE example of a C or C++ program that > communicates with a Lisp environment via sockets? I'm sure this is > quite easy -- I just need a trivial example to start with. CMUCL includes a Motif interface which works by issuing requests via a socket to a server written in C. It's not very simple (and the Lisp side API is different from CLISP, unfortunately), but it might be useful to you. The source can be browsed at An example of using the CLISP sockets API is Bruno Haible's inspector, which make CLISP communicate with a browser; see > 3) Are there any publicly-available Lisp packages (with corresponding > C libraries) that provide a higher-level communication layer than > sockets? Not that I know of. Hope that helps, -- Eric Marsden It's elephants all the way down From sds@goems.com Tue May 25 13:11:19 1999 Received: from smtp0-alterdial.uu.net (smtp0-alterdial.UU.NET [192.48.96.28]) by seagull.cdrom.com (8.8.8/8.6.6) with ESMTP id NAA26214 for ; Tue, 25 May 1999 13:11:17 -0700 (PDT) Received: from eho.eaglets.com by smtp0-alterdial.uu.net with ESMTP (peer crosschecked as: [208.235.77.238]) id QQgqts19266 for ; Tue, 25 May 1999 20:14:39 GMT Received: (from sds@localhost) by eho.eaglets.com (8.9.3/8.9.3) id QAA30254; Tue, 25 May 1999 16:09:42 -0400 Sender: sds@goems.com To: Bruno Haible Subject: new CLISP binary RPM Return-Receipt-To: sds@goems.com Reply-To: sds@goems.com X-Attribution: Sam X-Disclaimer: You should not expect anyone to agree with me. Mail-Copies-To: never From: Sam Steingold Date: 25 May 1999 16:09:42 -0400 Message-ID: Lines: 13 Hi, If you are running RedHat GNU/Linux with glibc 2.1, I would appreciate if you tested the new CLISP binary RPM, available at ftp://cellar.goems.com/pub/clisp/. Thanks. -- Sam Steingold (http://www.goems.com/~sds) running RedHat6.0 GNU/Linux Micros**t is not the answer. Micros**t is a question, and the answer is Linux, (http://www.linux.org) the choice of the GNU (http://www.gnu.org) generation. A computer scientist is someone who fixes things that aren't broken. From abecerra@iie.ufro.cl Fri May 28 09:11:56 1999 Received: from lautaro.enlaces.ufro.cl (lautaro.enlaces.ufro.cl [200.13.0.1]) by seagull.cdrom.com (8.8.8/8.6.6) with ESMTP id JAA28574 for ; Fri, 28 May 1999 09:11:52 -0700 (PDT) Received: from doc92.dis.ufro.cl ([200.10.21.91]) by lautaro.enlaces.ufro.cl (8.8.8/8.8.8) with SMTP id NAA26841 for ; Fri, 28 May 1999 13:11:18 -0400 (SAT) Message-ID: <010501bea91c$b6df0480$5b150ac8@doc92.dis.ufro.cl> From: "Lilian" To: Subject: help ... in Lisp Date: Fri, 28 May 1999 12:13:55 -0300 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.2106.4 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 hi I need a compiler for DOS of Lisp o Common Lisp I find Clisp but this re-boot my PC you knows a compiler ... and not a Interprete please Thanks Anita. From sds@goems.com Fri May 28 10:58:51 1999 Received: from smtp0-alterdial.uu.net (smtp0-alterdial.UU.NET [192.48.96.28]) by seagull.cdrom.com (8.8.8/8.6.6) with ESMTP id KAA29609 for ; Fri, 28 May 1999 10:58:49 -0700 (PDT) Received: from eho.eaglets.com by smtp0-alterdial.uu.net with ESMTP (peer crosschecked as: [208.235.77.238]) id QQgrem11663 for ; Fri, 28 May 1999 18:03:11 GMT Received: (from sds@localhost) by eho.eaglets.com (8.9.3/8.9.3) id OAA04897; Fri, 28 May 1999 14:00:30 -0400 Sender: sds@goems.com To: clisp-list@seagull.cons.org Subject: Re: help ... in Lisp References: <010501bea91c$b6df0480$5b150ac8@doc92.dis.ufro.cl> Return-Receipt-To: sds@goems.com Reply-To: sds@goems.com X-Attribution: Sam X-Disclaimer: You should not expect anyone to agree with me. Mail-Copies-To: never From: Sam Steingold In-Reply-To: "Lilian"'s message of "Fri, 28 May 1999 09:13:43 -0700 (PDT)" Date: 28 May 1999 14:00:30 -0400 Message-ID: Lines: 19 X-Mailer: Gnus v5.7/Emacs 20.3 >>>> In message <010501bea91c$b6df0480$5b150ac8@doc92.dis.ufro.cl> >>>> On the subject of "help ... in Lisp" >>>> Sent on Fri, 28 May 1999 09:13:43 -0700 (PDT) >>>> Honorable "Lilian" writes: >> >> I find Clisp but this re-boot my PC did you compile your binary yourself? >> I need a compiler for DOS of Lisp o Common Lisp >> you knows a compiler ... and not a Interprete http://burks.bton.ac.uk/burks/language/lisp/index.htm -- Sam Steingold (http://www.goems.com/~sds) running RedHat6.0 GNU/Linux Micros**t is not the answer. Micros**t is a question, and the answer is Linux, (http://www.linux.org) the choice of the GNU (http://www.gnu.org) generation. Yeah, yeah, I love cats too... wanna trade recipes? From atze@wicx50.informatik.uni-wuerzburg.de Fri May 28 17:52:46 1999 Received: from wrzx07.rz.uni-wuerzburg.de (wrzx07.rz.uni-wuerzburg.de [132.187.1.7]) by seagull.cdrom.com (8.8.8/8.6.6) with ESMTP id RAA03595 for ; Fri, 28 May 1999 17:52:44 -0700 (PDT) Received: from Io (ma@wex210.extern.uni-wuerzburg.de [132.187.248.210]) by wrzx07.rz.uni-wuerzburg.de (8.8.8/8.8.8) with SMTP id CAA05660 for ; Sat, 29 May 1999 02:54:54 +0200 (MET DST) From: Martin Atzmueller Reply-To: atze@wicx50.informatik.uni-wuerzburg.de To: clisp-list@clisp.cons.org Subject: FFI Date: Sat, 29 May 1999 03:40:21 +0200 X-Mailer: KMail [version 1.0.17] Content-Type: text/plain MIME-Version: 1.0 Message-Id: <99052903532100.20905@Io> Content-Transfer-Encoding: 8bit Hi I want to call a foreign c-function from Clisp by def-call-out. The function's argument is a 2-dimensional array of double-floats. So the c-function is defined as "void bar (double * x) ...". But with the FFI it seems to be the case, that I can't call it without specifying the precise dimensions of the array. I tried to define the parameter of the FFI-conversion-function as "c-pointer" but this didn't help, because Clisp couldn't convert the 2-dim array appropriately. Is there a way to solve this, e.g. can I call the function with the FFI using arrays of different dimensions as arguments? Thanks Martin From 3moeller@rzdspc1.informatik.uni-hamburg.de Sat May 29 07:19:49 1999 Received: from rzdspc1.informatik.uni-hamburg.de (root@rzdspc1.informatik.uni-hamburg.de [134.100.9.61]) by seagull.cdrom.com (8.8.8/8.6.6) with ESMTP id HAA12243 for ; Sat, 29 May 1999 07:19:48 -0700 (PDT) Received: from rzdspc3.informatik.uni-hamburg.de (3moeller@rzdspc3.informatik.uni-hamburg.de [134.100.8.63]) by rzdspc1.informatik.uni-hamburg.de (8.9.3/8.9.3) with ESMTP id QAA21344 for ; Sat, 29 May 1999 16:21:57 +0200 (MET DST) Received: (from 3moeller@localhost) by rzdspc3.informatik.uni-hamburg.de (8.9.3/8.9.3) id QAA24508 for clisp-list@seagull.cons.org; Sat, 29 May 1999 16:21:55 +0200 (MET DST) Date: Sat, 29 May 1999 16:21:55 +0200 From: Bodo Moeller <3moeller@informatik.uni-hamburg.de> To: clisp-list@seagull.cons.org Subject: Re: FFI Message-ID: <19990529162153.A24504@informatik.uni-hamburg.de> References: <99052903532100.20905@Io> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.5i In-Reply-To: <99052903532100.20905@Io>; from Martin Atzmueller on Fri, May 28, 1999 at 05:53:06PM -0700 On Fri, May 28, 1999 at 05:53:06PM -0700, Martin Atzmueller wrote: > I want to call a foreign c-function from Clisp by def-call-out. > The function's argument is a 2-dimensional array of double-floats. > So the c-function is defined as "void bar (double * x) ...". That's not a two-dimensional array; it's just a pointer to double, which means (with the implicit type conversion rules of C -- an array type value is always converted into a pointer to the first element, except when used with the & or sizeof operator) that it can be used for *one*-dimensional arrays. > But with the FFI it seems to be the case, that I can't call it without > specifying the precise dimensions of the array. It's exactly like that in C; e.g. void bar (double (*x)[10]); (x is a pointer to an array with 10 elements of type "double"). You cannot write void bar (double (*x)[]); From dobes@mindless.com Sat May 29 15:33:36 1999 Received: from mail.rdc1.bc.home.com (imail@ha1.rdc1.bc.wave.home.com [24.2.10.66]) by seagull.cdrom.com (8.8.8/8.6.6) with ESMTP id PAA15834 for ; Sat, 29 May 1999 15:33:33 -0700 (PDT) Received: from cr594972-a.surrey1.bc.wave.home.com ([24.112.126.47]) by mail.rdc1.bc.home.com (InterMail v4.01.01.00 201-229-111) with SMTP id <19990529223548.YFNY18720.mail.rdc1.bc.home.com@cr594972-a.surrey1.bc.wave.home.com> for ; Sat, 29 May 1999 15:35:48 -0700 Received: (qmail 15302 invoked from network); 29 May 1999 22:35:48 -0000 Received: from sludge.localdomain (HELO mindless.com) (192.168.0.2) by nexus.localdomain with SMTP; 29 May 1999 22:35:48 -0000 Message-ID: <37506BC3.D3960365@mindless.com> Date: Sat, 29 May 1999 15:35:47 -0700 From: Dobes Vandermeer Organization: None whatsoever X-Mailer: Mozilla 4.6 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: clisp-list@seagull.cons.org Subject: Re: FFI References: <19990529162153.A24504@informatik.uni-hamburg.de> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Bodo Moeller wrote: > > It's exactly like that in C; e.g. > > void bar (double (*x)[10]); > > (x is a pointer to an array with 10 elements of type "double"). You > cannot write > > void bar (double (*x)[]); What about void bar(double **x), which is functionally equivalent? Did you actually try that, BTW? It looks to me like "double *x[]" would work just fine as well, but thats just a guess. CU Dobes From 3moeller@rzdspc1.informatik.uni-hamburg.de Sat May 29 16:41:55 1999 Received: from rzdspc1.informatik.uni-hamburg.de (root@rzdspc1.informatik.uni-hamburg.de [134.100.9.61]) by seagull.cdrom.com (8.8.8/8.6.6) with ESMTP id QAA16674 for ; Sat, 29 May 1999 16:41:50 -0700 (PDT) Received: from rzdspc3.informatik.uni-hamburg.de (3moeller@rzdspc3.informatik.uni-hamburg.de [134.100.8.63]) by rzdspc1.informatik.uni-hamburg.de (8.9.3/8.9.3) with ESMTP id BAA27575 for ; Sun, 30 May 1999 01:44:00 +0200 (MET DST) Received: (from 3moeller@localhost) by rzdspc3.informatik.uni-hamburg.de (8.9.3/8.9.3) id BAA26143 for clisp-list@seagull.cons.org; Sun, 30 May 1999 01:43:58 +0200 (MET DST) Date: Sun, 30 May 1999 01:43:58 +0200 From: Bodo Moeller <3moeller@informatik.uni-hamburg.de> To: clisp-list@seagull.cons.org Subject: Re: FFI Message-ID: <19990530014356.A26093@informatik.uni-hamburg.de> References: <37506BC3.D3960365@mindless.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.5i In-Reply-To: <37506BC3.D3960365@mindless.com>; from Dobes Vandermeer on Sat, May 29, 1999 at 03:33:47PM -0700 On Sat, May 29, 1999 at 03:33:47PM -0700, Dobes Vandermeer wrote: > Bodo Moeller wrote: >> It's exactly like that in C; e.g. >> >> void bar (double (*x)[10]); >> >> (x is a pointer to an array with 10 elements of type "double"). You >> cannot write >> >> void bar (double (*x)[]); > What about void bar(double **x), which is functionally equivalent? It's not. "double **x" means that x is a pointer to a pointer which points to a double. This can mean that x actually points to the first element of an array (of pointers to double), but in any case *x is a pointer, not an array. > Did you actually try that, BTW? It looks to me like "double *x[]" would > work just fine as well, but thats just a guess. "double *x[]" in the function prototype works just as well as "double **x", but these are entirely different from "double (*x)[]". (Note that the [] has higher precedence than *.) In a variable declaration, double *x[] and double **x would be different things: void some_function(double arg1, double arg2, double arg3) { double *x[] = {&arg1, &arg2, &arg3}; /* x is an array of pointers * to double. */ double **y = &(x[0]); /* y is a pointer to a pointer to double. */ /* ... */ } Instead of &(x[0]) (which, according to the C precedence rules, could just as well be written as "&x[0]") it is more customary to write just x, but one should always keep in mind that pointers and arrays are *not* equivalent. E.g., in some_function, sizeof x will be three times the size of a single pointer to double (3*4, say), while sizeof y will be the size of a single pointer (e.g. 4). When you write "y = x;" with declarations as above, you invoke one of the magic C rules for automatic conversion. A related rule applies to function prototypes -- in prototypes (but not in ordinary variable declarations), some_type x[] or even some_type x[42] is automatically interpreted as some_type *x. (You cannot assign whole arrays [unless they are wrapped into a struct or union], so a function parameter of array type can never exist.) The idea is that you can make visible in the function declaration that the function argument is not just the pointer to an isolated value, but to the first element of an array -- i.e. that x + 1, x + 2, ... are meaningful pointers to other elements of the same array (if the array is that large). But this conversion rule does not apply to array types "deeper" in the type declaration (it just wouldn't make sense), so "some_type x[][]" and "some_type *(x[])" are *not* the same. I suggest that you read the explanations on these issues in K&R (in the "C reference manual" appendix) if this is not clear to you. From atze@wicx50.informatik.uni-wuerzburg.de Sun May 30 15:10:10 1999 Received: from wrzx07.rz.uni-wuerzburg.de (wrzx07.rz.uni-wuerzburg.de [132.187.1.7]) by seagull.cdrom.com (8.8.8/8.6.6) with ESMTP id PAA26712 for ; Sun, 30 May 1999 15:10:05 -0700 (PDT) Received: from Io (ma@wex188.extern.uni-wuerzburg.de [132.187.248.188]) by wrzx07.rz.uni-wuerzburg.de (8.8.8/8.8.8) with SMTP id AAA07265 for ; Mon, 31 May 1999 00:12:20 +0200 (MET DST) From: Martin Atzmueller Reply-To: atze@wicx50.informatik.uni-wuerzburg.de To: clisp-list@seagull.cons.org Subject: Re: FFI Date: Mon, 31 May 1999 00:51:48 +0200 X-Mailer: KMail [version 1.0.17] Content-Type: text/plain References: <19990529162153.A24504@informatik.uni-hamburg.de> MIME-Version: 1.0 Message-Id: <99053101094300.00284@Io> Content-Transfer-Encoding: 8bit On Sat, 29 May 1999, you wrote: > On Fri, May 28, 1999 at 05:53:06PM -0700, Martin Atzmueller wrote: > > > I want to call a foreign c-function from Clisp by def-call-out. > > The function's argument is a 2-dimensional array of double-floats. > > So the c-function is defined as "void bar (double * x) ...". > > That's not a two-dimensional array; it's just a pointer to double, > which means (with the implicit type conversion rules of C -- an array > type value is always converted into a pointer to the first element, > except when used with the & or sizeof operator) that it can be used > for *one*-dimensional arrays. I have to confess that I am no C expert. But the thing hinted at above is exactly what I wanted. I tried to port code that was written using the ACL-FFI and there the arguments for the foreign function: void bla (double * x, double * y, int dim-x, int dim-y), for example, were defined as :arguments ((array double-float) (array double-float) integer integer). It seems that for the ACL-FFI the number of dimensions does not matter when passing an array since it is converted to a pointer to the first element, or so I guess. My problem is that I want to have a foreign function that accepts arrays of different dimensions, since I do not know the exact dimensions of the array that gets passed to the function. But so far I did not find a solution with the Clisp-FFI. The imp-notes for Clisp say that one has to write (c-ptr (c-array ({dims}*) ) when passing an array to a c-function, but just writing (c-ptr (c-array () ) does not help in this case. From haible@ilog.fr Mon May 31 02:15:22 1999 Received: from sceaux.ilog.fr (sceaux.ilog.fr [193.55.64.10]) by seagull.cdrom.com (8.8.8/8.6.6) with ESMTP id CAA02884 for ; Mon, 31 May 1999 02:15:21 -0700 (PDT) Received: from laposte.ilog.fr (laposte [172.17.1.6]) by sceaux.ilog.fr (8.9.1/8.9.1) with ESMTP id LAA28280 for ; Mon, 31 May 1999 11:17:47 +0200 (MET DST) Received: from jaures.ilog.fr ([172.17.4.75]) by laposte.ilog.fr (8.9.3/8.9.3) with ESMTP id LAA25311; Mon, 31 May 1999 11:17:46 +0200 (MET DST) From: Bruno Haible Received: (from haible@localhost) by jaures.ilog.fr (8.9.3/8.9.3) id LAA23379; Mon, 31 May 1999 11:17:17 +0200 (MET DST) Date: Mon, 31 May 1999 11:17:17 +0200 (MET DST) Message-Id: <199905310917.LAA23379@jaures.ilog.fr> To: clisp-list@seagull.cons.org Subject: Re: FFI In-Reply-To: <99052903532100.20905@Io> References: <99052903532100.20905@Io> Martin Atzmueller writes: > I want to call a foreign c-function from Clisp by def-call-out. > The function's argument is a 2-dimensional array of double-floats. > So the c-function is defined as "void bar (double * x) ...". > But with the FFI it seems to be the case, that I can't call it without > specifying the precise dimensions of the array. You can do it in two steps: 1. Passing a linear array of `double', whose length is the product of your matrix' dimensions. This can be done using the trick in example 5 in impnotes.html (or foreign.txt): You cast the function type (cast your_function `(c-function (:arguments (v (c-ptr (c-array double-float ,n)))) (:return-type (c-ptr (c-array double-float ,n)) :malloc-free ) ) ) 2. Use MAKE-ARRAY with :DISPLACED-TO argument to "convert" your 1-dimensional Lisp array into a 2-dimensional Lisp array. Bruno From hoehle@tzd.telekom.de Mon May 31 09:23:57 1999 Received: from fw1b.telekom.de (gw1.telekom.de [194.25.15.11]) by seagull.cdrom.com (8.8.8/8.6.6) with SMTP id JAA06758 for ; Mon, 31 May 1999 09:23:56 -0700 (PDT) Received: by fw1b.telekom.de; (5.65v4.0/1.3/10May95) id AA03591; Mon, 31 May 1999 18:26:21 +0200 Received: from Q8P65.blf01.telekom.de by U8PW4.blf01.telekom.de with ESMTP for clisp-list@clisp.cons.org; Mon, 31 May 1999 18:26:46 +0200 Received: from q9f09.dmst02.telekom.de by q8p65.blf01.telekom.de with ESMTP for clisp-list@clisp.cons.org; Mon, 31 May 1999 18:26:17 +0200 Received: from w9f00992.dmst02.telekom.de (W9F00992.dmst02.telekom.de [164.27.121.145]) by q9f09.dmst02.telekom.de (8.8.5/8.8.5) with SMTP id SAA13386 for ; Mon, 31 May 1999 18:13:24 +0200 Received: from w9f01006.dmst02.telekom.de by w9f00992.dmst02.telekom.de (SMI-8.6/SMI-SVR4) id SAA24450; Mon, 31 May 1999 18:26:16 +0200 Received: (from hoehle@localhost) by w9f01006.dmst02.telekom.de (8.8.8+Sun/8.8.8) id SAA07042; Mon, 31 May 1999 18:26:15 +0200 (MET DST) Sender: hoehle@tzd.telekom.de To: clisp-list@clisp.cons.org Subject: CLOS streams ? (Was: Streams as pipes?) References: <4nyaidhxyy.fsf@rtp.ericsson.se> <3136674790837348@naggum.no> From: Joerg-Cyril Hoehle Date: 31 May 1999 20:26:14 +0200 In-Reply-To: Erik Naggum's message of 26 May 1999 02:33:10 +0000 Message-Id: Lines: 15 X-Mailer: Gnus v5.2.25/XEmacs 19.14 Hi, Erik Naggum wrote in c.l.lisp: > if you use a Common Lisp implementation that supports the Gray Proposal > for CLOSified streams, this is a trivial exercise. if you don't, you're > basically out of luck. since the Gray Proposal is not quite standard, > you'll need to use the manual with the Common Lisp implementation. How do CLISP's controller streams compare to that proposal? Is that proposal known to the larger Lisp community? Regards, J"org H"ohle hoehle tzd telekom de --/ Funktionssicherheit/Reliability Forschungszentrum Telekom AG/Telekom Research Center