unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: guile-devel@gnu.org
Subject: build failure just trying to build guile-1.8.7 natively
Date: Wed, 18 Nov 2009 12:11:51 -0500 (EST)	[thread overview]
Message-ID: <alpine.LFD.2.00.0911181210100.9125@localhost> (raw)


  as a followup to my earlier plea for help, i downloaded the
guile-1.8.7 tarball and tried to build it on my (effectively) fedora
12 system, and ran into exactly the same error:

cat alist.doc arbiters.doc async.doc backtrace.doc boolean.doc
chars.doc continuations.doc debug.doc deprecation.doc deprecated.doc
discouraged.doc dynl.doc dynwind.doc environments.doc eq.doc error.doc
eval.doc evalext.doc extensions.doc feature.doc fluids.doc fports.doc
futures.doc gc.doc goops.doc gsubr.doc gc-mark.doc gc-segment.doc
gc-malloc.doc gc-card.doc guardians.doc hash.doc hashtab.doc hooks.doc
i18n.doc init.doc ioext.doc keywords.doc lang.doc list.doc load.doc
macros.doc mallocs.doc modules.doc numbers.doc objects.doc objprop.doc
options.doc pairs.doc ports.doc print.doc procprop.doc procs.doc
properties.doc random.doc rdelim.doc read.doc root.doc rw.doc
scmsigs.doc script.doc simpos.doc smob.doc sort.doc srcprop.doc
stackchk.doc stacks.doc stime.doc strings.doc srfi-4.doc srfi-13.doc
srfi-14.doc strorder.doc strports.doc struct.doc symbols.doc
threads.doc throw.doc values.doc variable.doc vectors.doc version.doc
vports.doc weaks.doc ramap.doc unif.doc dynl.doc filesys.doc posix.doc
net_db.doc socket.doc regex-posix.doc |
GUILE="/home/rpjday/guile-1.8.7/pre-inst-guile"
../scripts/snarf-check-and-output-texi          >
guile-procedures.texi || { rm guile-procedures.texi; false; }
ERROR: unknown doc attribute: (location (string . alist.c) (int . 40)
(hash . hash))
make[3]: *** [guile-procedures.texi] Error 1
make[3]: Leaving directory `/home/rpjday/guile-1.8.7/libguile'
make[2]: *** [all] Error 2
make[2]: Leaving directory `/home/rpjday/guile-1.8.7/libguile'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/rpjday/guile-1.8.7'
make: *** [all] Error 2

  so this is no longer an openembedded issue, it's a straight build
issue.  can anyone help?  i simply ran:

  $ ./configure
  $ make

rday
--


========================================================================
Robert P. J. Day                               Waterloo, Ontario, CANADA

            Linux Consulting, Training and Kernel Pedantry.

Web page:                                          http://crashcourse.ca
Twitter:                                       http://twitter.com/rpjday
========================================================================




             reply	other threads:[~2009-11-18 17:11 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-18 17:11 Robert P. J. Day [this message]
2009-11-19 17:24 ` build failure just trying to build guile-1.8.7 natively Miroslav Lichvar
2009-11-19 18:01   ` Robert P. J. Day
2009-11-19 18:58   ` Robert P. J. Day
2009-11-27 17:56   ` Ludovic Courtès
2009-11-27 18:22     ` Miroslav Lichvar
2009-11-27 20:29       ` Ludovic Courtès
2009-11-27 20:52         ` Miroslav Lichvar
2009-11-27 21:07           ` Robert P. J. Day
2009-11-27 22:00             ` Ludovic Courtès

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=alpine.LFD.2.00.0911181210100.9125@localhost \
    --to=rpjday@crashcourse.ca \
    --cc=guile-devel@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).