[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Guile 1.4.1 w/ guile-oops 1.0.2
From: |
Michael Carmack |
Subject: |
Guile 1.4.1 w/ guile-oops 1.0.2 |
Date: |
Fri, 6 Sep 2002 08:21:18 +0000 |
User-agent: |
Mutt/1.3.24i |
Guile-oops/1.0.2 doesn't seem to build against guile/1.4.1, apparently
because the order of the CPP arguments has changed for bin/guile-snarf.
(Guile-oops/1.0.2 did build successfully against guile/1.4 for me.)
In 1.4.1, 'guile-snarf --help' reports:
Usage: guile-snarf [-d | -D] [-o OUTFILE] INFILE [CPP-OPTIONS ...]
So, apparently the CPP options must follow the file in guile/1.4.1. But
when building guile-oops/1.0.2, the first thing that gets called is:
guile-snarf -DHAVE_SCM_SIMPLE_FORMAT=1 -DHAVE_SCM_SHARED_ARRAY_ROOT=1
-DSCM_MUTEX_INIT_TWO_ARGS=1 -I. -I. -g -O2
-I/pkg/guile/1.4.1/.i686-pc-linux-gnu/include -Wall -Wpointer-arith
-Wmissing-prototypes goops.c > goops.x \
|| { rm goops.x; false; }
make[1]: *** [goops.x] Error 1
So, having the file (goops.c) follow all the cpp options immediately breaks
guile-oops/1.0.2 build.
Guile/1.4 must not have cared where the cpp options were specified,
because guile-oops/1.0.2 builds fine when compiling against guile/1.4.
Is guile-oops/1.0.2 not intended to be used with guile/1.4.1?
m.
- Guile 1.4.1 w/ guile-oops 1.0.2,
Michael Carmack <=