unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: rvclayton@acm.org (r. clayton)
To: bug-guile@gnu.org
Subject: Failure while building Guile-SDL 0.3.6.
Date: 01 Apr 2007 16:37:38 -0400	[thread overview]
Message-ID: <87abxrhlv1.fsf@UlanBator.myhome.westell.com> (raw)

I was trying to build http://www.gnuvola.org/software/guile-sdl/ under
guile-1.8 on a debian testing system (updated weekly) and ran into a problem:

  $ make
  make  all-recursive
  make[1]: Entering directory `/usr/local/src/guile-sdl-0.3.6'
  Making all in src
  make[2]: Entering directory `/usr/local/src/guile-sdl-0.3.6/src'
  make  all-am
  make[3]: Entering directory `/usr/local/src/guile-sdl-0.3.6/src'
  if /bin/sh ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H
  -I. -I. -I.. -I. -I../include   -g -O2 -Wall -pedantic -Wno-long-long -pipe
  -I/usr/local/packages/sdl-1.2.11/include/SDL -D_GNU_SOURCE=1 -D_REENTRANT -MT
  initf.lo -MD -MP -MF ".deps/initf.Tpo" -c -o initf.lo initf.c; \ then mv -f
  ".deps/initf.Tpo" ".deps/initf.Plo"; else rm -f ".deps/initf.Tpo"; exit 1; fi

  In file included from /usr/include/libguile/tags.h:31,
                   from ../include/gperfsup.h:4,
                   from initf.c:33:
  /usr/include/libguile/__scm.h:523: error: expected '=', ',', ';', 'asm' or
                   '__attribute__' before 'scm_call_generic_0' 
  /usr/include/libguile/__scm.h:532: error: expected '=', ',', ';', 'asm' or
                   '__attribute__' before 'scm_call_generic_1' 
  /usr/include/libguile/__scm.h:541: error: expected '=', ',', ';', 'asm' or
                   '__attribute__' before 'scm_call_generic_2' 
  /usr/include/libguile/__scm.h:552: error: expected '=', ',', ';', 'asm' or
                   '__attribute__' before 'scm_apply_generic' 
  make[3]: *** [initf.lo] Error 1
  make[3]: Leaving directory `/usr/local/src/guile-sdl-0.3.6/src'
  make[2]: *** [all] Error 2
  make[2]: Leaving directory `/usr/local/src/guile-sdl-0.3.6/src'
  make[1]: *** [all-recursive] Error 1
  make[1]: Leaving directory `/usr/local/src/guile-sdl-0.3.6'
  make: *** [all] Error 2

  $

Doing the gcc -E thing shows the likely problem:

  $ gcc -E -DHAVE_CONFIG_H -I. -I. -I.. -I. -I../include -g -O2 -Wall -pedantic
  -Wno-long-long -pipe -I/usr/local/packages/sdl-1.2.11/include/SDL
  -D_GNU_SOURCE=1 -D_REENTRANT -MT initf.lo -MD -MP -MF .deps/initf.Tpo -c
  initf.c  -fPIC -DPIC | grep _generic
  extern SCM scm_call_generic_0 (SCM gf);
  extern SCM scm_call_generic_1 (SCM gf, SCM a1);
  extern SCM scm_call_generic_2 (SCM gf, SCM a1, SCM a2);
  extern SCM scm_apply_generic (SCM gf, SCM args);

  $ 

At this point I've reached the end of my tricks.  What more needs to be done to
fix this?



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


             reply	other threads:[~2007-04-01 20:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-01 20:37 r. clayton [this message]
2007-04-02  8:02 ` Failure while building Guile-SDL 0.3.6 Ludovic Courtès
2007-04-02  9:51   ` Thien-Thi Nguyen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87abxrhlv1.fsf@UlanBator.myhome.westell.com \
    --to=rvclayton@acm.org \
    --cc=bug-guile@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).