Re: cmucl-19e + gcc43 better, not quite there

Rex Dieter <[email protected]>
Newsgroups gmane.lisp.cmucl.general
Message-ID <[email protected]>
Carl Shapiro wrote:

> Hi Rex,
> 
> On Fri, Mar 14, 2008 at 12:37 PM, Rex Dieter <[email protected]> wrote:
>> Tried out cmucl-19e-pre1, and this works better (than cmucl-19d) and
>> gets further, but fails in some asm in
>> ../../src/lisp/x86-assem.S
>> ../../src/lisp/x86-assem.S: Assembler messages:
>> ../../src/lisp/x86-assem.S:84: Error: suffix or operands invalid for
>> `fnstsw'
> 
> Can you change that line to "fnstsw %ax" and running the compile again?

Yes, that seemed to help.  Now I'm seeing some bits not building (but it's
better)
http://koji.fedoraproject.org/koji/getfile?taskID=517448&name=build.log
excerpt:
install: cannot stat `i386-redhat-linux-gnu-4/hemlock/hemlock-library.x86f':
No such file or directory
install: cannot stat `i386-redhat-linux-gnu-4/hemlock/spell-dictionary.bin':
No such file or directory
install: cannot stat `i386-redhat-linux-gnu-4/interface/clm-library.x86f':
No such file or directory
install: cannot stat `i386-redhat-linux-gnu-4/motif/server/motifd': No such
file or directory

I'll keep digging.

>> Further, attached is a quick-n-dirty patch I needed to make it not choke
>> on
>> #include <sys/syscalls.h>
>> ->
>> #include <asm/unistd.h>
>> which contains
>> #ifdef __i386__
>> #include "unistd_32.h"
>> #else
>> #include "unistd_64.h"
>> #endif
>> on recent kernel-headers.  In short, translating -I- to use -iquote
>> instead (and have the build respect our rpm optflags)
> 
> I committed a change to the FreeBSD and Darwin configuration files
> which switch to using -iquote when the compiler is not GCC 2 or 3.  I
> can make a change to the Linux configuration file as well.  However, I
> do not understand how this problem relates to the kernel header files.
>  Is the underlying problem that the wrong header file is being found
> when an -iquote is not used?

Else, get "unistd_32.h" not found errors.

-- Rex
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.