From owner-freebsd-questions Thu Apr 24 17:26:18 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id RAA11754 for questions-outgoing; Thu, 24 Apr 1997 17:26:18 -0700 (PDT) Received: from Pkrw.tcn.net (Pkrw.tcn.net [199.166.4.58]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA11749 for ; Thu, 24 Apr 1997 17:26:15 -0700 (PDT) Received: from localhost (krw@localhost) by Pkrw.tcn.net (8.8.5/8.8.5) with SMTP id UAA00259 for ; Thu, 24 Apr 1997 20:29:50 -0400 (EDT) X-Authentication-Warning: Pkrw.tcn.net: krw owned process doing -bs Date: Thu, 24 Apr 1997 20:29:21 -0400 (EDT) From: "Kenneth R. Westerback" To: freebsd-questions@freebsd.org Subject: Allegro CL for Linux - need Linux ld to apply patches? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I got the Franz CD distribution of Allegro Common Lisp for Linux (it's FREE after all) and installed with no more than the usual fumbling about, including the interface to emacs (well, xemacs 19.15 actually). It seemed to run OK (I had already installed the Linux compatibility stuff). Then I tried to compile a simple file (one defun) and got a 'Bus error' and a core dump. A recent message on this forum revealed that 'Bus error' really means 'Attempt to modify read-only memory' (wouldn't that be a nicer message? or does 'Bus error' happen for other things too?) and gave me hope that perhaps it's just a minor bug. So I downloaded all the patches for Allegro 4.3 (the version on the CD) and attempted to run the script that rebuilds the Lisp binary image. This script blew up trying to compile a .c file, complaining about prototype mismatches in various include files having to do with networking. I found out how to manually recompile the file with some command line options that tell it to use the system routines (presumably the ones in the Linux compatibility libs) rather than roll its own. The script then bombs out trying to run ld to rebuild the library containing all the new .o files that comprise some of the patches. It complains that the first .o file it tries is neither an object file nor an archive. Whew. Is it possible to run the Linux ld to rebuild the library/archive? Or will that fail because the new .o file I cc'ed into existance is now a FreeBDS object rather than a Linux object? Is there any hope short of (shudder!) installing Linux? Has anyone got/even tried to get Allegro CL for Linux working under FreeBSD? I'm running FreeBSD 2.2-STABLE up to date through src-2.2.0248. ---- Ken