unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: Fu-Gangqiang <lispor@163.com>
To: "Guile bug" <bug-guile@gnu.org>
Subject: guile make error
Date: Wed, 16 Feb 2011 10:41:05 +0800 (CST)	[thread overview]
Message-ID: <3cc71019.ee26.12e2c57a6c0.Coremail.lispor@163.com> (raw)

Hi,all,
Today, I built guile from Git repository,
but have some warnings and 2 errors.

warnings and errors :
----->cut here:start<-----
gc.c: In function 'scm_gc_dump':
gc.c:333: warning: implicit declaration of function 'GC_dump'
memoize.c:478:***Mismatching FUNC_NAME.  Should be: `#define FUNC_NAME s_"@prompt"'
pairs.c:147:***Missing or erroneous `#define FUNC_NAME s_scm_cdr'
pairs.c:150:***pairs.c:155:***Missing or erroneous `#define FUNC_NAME s_scm_cddr'
pairs.c:158:***pairs.c:163:***Missing or erroneous `#define FUNC_NAME s_scm_cadr'
pairs.c:166:***pairs.c:171:***Missing or erroneous `#define FUNC_NAME s_scm_cdddr'
pairs.c:174:***pairs.c:179:***Missing or erroneous `#define FUNC_NAME s_scm_cdadr'
pairs.c:182:***pairs.c:187:***Missing or erroneous `#define FUNC_NAME s_scm_caddr'
pairs.c:190:***pairs.c:195:***Missing or erroneous `#define FUNC_NAME s_scm_caadr'
pairs.c:198:***pairs.c:203:***Missing or erroneous `#define FUNC_NAME s_scm_cddddr'
pairs.c:206:***pairs.c:211:***Missing or erroneous `#define FUNC_NAME s_scm_cddadr'
pairs.c:214:***pairs.c:219:***Missing or erroneous `#define FUNC_NAME s_scm_cdaddr'
pairs.c:222:***pairs.c:227:***Missing or erroneous `#define FUNC_NAME s_scm_cdaadr'
pairs.c:230:***pairs.c:235:***Missing or erroneous `#define FUNC_NAME s_scm_cadddr'
pairs.c:238:***pairs.c:243:***Missing or erroneous `#define FUNC_NAME s_scm_cadadr'
pairs.c:246:***pairs.c:251:***Missing or erroneous `#define FUNC_NAME s_scm_caaddr'
pairs.c:254:***pairs.c:259:***Missing or erroneous `#define FUNC_NAME s_scm_caaadr'
pairs.c:262:***module/language/glil/decompile-assembly.scm:174:21: warning: possibly unbound variable `make-glil-local'
module/language/glil/decompile-assembly.scm:170:21: warning: possibly unbound variable `make-glil-local'
module/ice-9/mapping.scm:97:48: warning: possibly wrong number of arguments to `hashx-get-handle'
module/ice-9/mapping.scm:94:48: warning: possibly unbound variable `hashx-create-handle'
module/scripts/autofrisk.scm:182:2: warning: non-literal format string
module/language/ecmascript/base.scm:179:31: warning: wrong number of arguments to `object->number'
module/language/ecmascript/base.scm:95:6: warning: possibly unbound variable `v'
module/language/ecmascript/base.scm:181:14: warning: possibly unbound variable `o'
module/language/ecmascript/base.scm:226:22: warning: possibly unbound variable `Boolean'
module/language/ecmascript/base.scm:227:21: warning: possibly unbound variable `String'
module/language/ecmascript/base.scm:228:21: warning: possibly unbound variable `Number'
module/language/ecmascript/function.scm:40:9: warning: possibly unbound variable `<js-array-object>'
module/language/ecmascript/function.scm:44:43: warning: possibly unbound variable `js-array-vector'
guile-readline/ice-9/readline.scm:216:10: warning: possibly unbound variable `*readline-completion-function*'
guile-readline/ice-9/readline.scm:213:10: warning: possibly unbound variable `*readline-completion-function*'
guile-readline/ice-9/readline.scm:210:2: warning: possibly unbound variable `*readline-completion-function*'
guile-readline/ice-9/readline.scm:156:4: warning: possibly unbound variable `%readline'
guile-readline/ice-9/readline.scm:63:0: warning: possibly unbound variable `readline-options-interface'
guile-readline/ice-9/readline.scm:63:0: warning: possibly unbound variable `readline-options-interface'
guile-readline/ice-9/readline.scm:63:0: warning: possibly unbound variable `readline-options-interface'
guile-readline/ice-9/readline.scm:63:0: warning: possibly unbound variable `readline-options-interface'
guile-readline/ice-9/readline.scm:63:0: warning: possibly unbound variable `readline-options-interface'
guile-readline/ice-9/readline.scm:63:0: warning: possibly unbound variable `readline-options-interface'
guile-readline/ice-9/readline.scm:63:0: warning: possibly unbound variable `readline-options-interface'
guile-readline/ice-9/readline.scm:63:0: warning: possibly unbound variable `readline-options-interface'
guile-readline/ice-9/readline.scm:63:0: warning: possibly unbound variable `readline-options-interface'
guile-readline/ice-9/readline.scm:63:0: warning: possibly unbound variable `readline-options-interface'
guile-readline/ice-9/readline.scm:97:49: warning: possibly unbound variable `%readline'
guile-readline/ice-9/readline.scm:125:38: warning: possibly unbound variable `readline-options-interface'
guile-readline/ice-9/readline.scm:206:4: warning: possibly unbound variable `*readline-completion-function*'
~/Git/guile/doc/ref//standard-library.texi:974: Node `deffn-filter' previously defined at line 937.
makeinfo: Removing output file `guile.info' due to errors; use --force to preserve.
make[4]: *** [guile.info] Error 1
make[3]: *** [all] Error 2
make[2]: *** [all-recursive] Error 1
make[1]: *** [all-recursive] Error 1
make: *** [all] Error 2
----->cut here:end<-----




                 reply	other threads:[~2011-02-16  2:41 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=3cc71019.ee26.12e2c57a6c0.Coremail.lispor@163.com \
    --to=lispor@163.com \
    --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).