unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
* Guile 1.4.1 w/ guile-oops 1.0.2
@ 2002-09-06  8:21 Michael Carmack
  2002-09-06 17:08 ` Thien-Thi Nguyen
  0 siblings, 1 reply; 2+ messages in thread
From: Michael Carmack @ 2002-09-06  8:21 UTC (permalink / raw)



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.




_______________________________________________
Bug-guile mailing list
Bug-guile@gnu.org
http://mail.gnu.org/mailman/listinfo/bug-guile


^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2002-09-06 17:08 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2002-09-06  8:21 Guile 1.4.1 w/ guile-oops 1.0.2 Michael Carmack
2002-09-06 17:08 ` Thien-Thi Nguyen

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).