From: Rob Browning <rlb@defaultvalue.org>
Subject: update on 1.6 failure to bootstrap from pssyntax.ss (need help)
Date: Thu, 28 Aug 2003 10:32:07 -0500 [thread overview]
Message-ID: <87bru9dci0.fsf@raven.i.defaultvalue.org> (raw)
I forgot you need to edit syncase.scm if you're monkeying with
pssyntax.scm. Did I forget anything else?
>From a clean checkout of 1.6, build:
- uncomment this in syncase.scm:
;;; The following lines are necessary only if we start making changes
;; (use-syntax sc-expand)
;; (load-from-path "ice-9/psyntax.ss")
- $ touch psyntax.ss
- $ make
/home/rlb/src/guile/1.6/pre-inst-guile -s ./compile-psyntax.scm \
./psyntax.ss ./psyntax.pp
<unnamed port>: In expression (eval (list syntmp-noexpand-84 syntmp-x-1033) (interaction-environment)):
<unnamed port>: Wrong type to apply: #f
make: *** [psyntax.pp] Error 2
You can also also add
(debug-enable 'debug)
(debug-enable 'backtrace)
(read-enable 'positions)
just above the load-from path in syncase.scm and you'll get the result
below. Anyone have any suggestions for the fastest way to track this
down. I'd like to fix it, but I don't have a lot of time to spend on
it this week, and so I haven't yet dived in deeply. I was hoping
someone who already knows this area better might have suggestions.
$ make
/home/rlb/src/guile/1.6/pre-inst-guile -s ./compile-psyntax.scm \
./psyntax.ss ./psyntax.pp
Backtrace:
In unknown file:
?: 0* [primitive-load-path "ice-9/psyntax.ss"]
?: 1* [#<procedure #f (syntmp-x-1370)> (let () # #)]
?: 2* (if (and # #) (cadr syntmp-x-1370) ...)
?: 3 [syntmp-chi-top-150 (let () (define-syntax define-structure #) ...) () ...]
...
?: 4 (let (#) (if # #) syntmp-x-785)
?: 5* [syntmp-chi-expr-152 core #<procedure #f #> # ...]
?: 6 (let (#) (if # syntmp-value-701 #))
...
?: 7 [syntmp-build-let-97 #f () () ...
?: 8* [syntmp-chi-body-155 (# #) #(syntax-object # #) () ...]
?: 9 (let ((syntmp-r-627 #)) (let (#) (let # #)))
...
?: 10 (begin (if # #) (letrec # #) (set-cdr! syntmp-r-627 #) ...)
?: 11* (letrec ((syntmp-loop-665 #)) (syntmp-loop-665 syntmp-bindings-636 #f #f))
?: 12 [syntmp-loop-665 ((macro (#) . #(syntax-object # #))) #f #f]
...
?: 13 (let (#) (set-cdr! syntmp-b-669 #) ...)
?: 14* [set-cdr! (macro (#) . #(syntax-object # #)) ...
?: 15* [syntmp-eval-local-transformer-158 (lambda (syntmp-x-0) (letrec # #))]
?: 16 (let ((syntmp-p-572 #)) (if (procedure? syntmp-p-572) syntmp-p-572 ...))
?: 17* [syntmp-local-eval-hook-91 (lambda (syntmp-x-0) (letrec # #))]
?: 18 (eval (list syntmp-noexpand-84 syntmp-x-1033) (interaction-environment))
<unnamed port>: In expression (eval (list syntmp-noexpand-84 syntmp-x-1033) (interaction-environment)):
<unnamed port>: Wrong type to apply: #f
make: *** [psyntax.pp] Error 2
--
Rob Browning
rlb @defaultvalue.org and @debian.org; previously @cs.utexas.edu
GPG starting 2002-11-03 = 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
reply other threads:[~2003-08-28 15:32 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=87bru9dci0.fsf@raven.i.defaultvalue.org \
--to=rlb@defaultvalue.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).