unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Daniel Kraft <d@domob.eu>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guile-devel@gnu.org
Subject: Re: Patch: Some work towards making --disable-deprecated compile
Date: Tue, 07 Apr 2009 17:56:13 +0200	[thread overview]
Message-ID: <49DB779D.7010802@domob.eu> (raw)
In-Reply-To: <87zlevkll3.fsf@gnu.org>

Ludovic Courtès wrote:
>> here's my patch from last december to fix some internal
>> inconsistencies that prevented guile from compiling with
>> --disable-deprecated at that time.  I've now my copyright assignment
>> in place, so when it is ok you could commit it at any time.  The patch
>> is updated to the current revision.
> 
> Thanks!  I've committed it with minor formatting changes:
> 
>   http://git.savannah.gnu.org/cgit/guile.git/commit/?id=6ab8238d99f477ee7ac12f1f1a3ec70aab3e68c7

Thank you very much, Ludo!

> BTW, next time, could you fix your Git user name and email configuration
> (which appears in the patch), and provide the change log as part of the
> Git log (so that the patch can be applied quickly with git-am(1))?

I will try so; unfortunatelly I'm still a little fighting with git, as 
this was/is the first time for me to use it.  And while I really like 
the apparent features with regards to local branching and the like, I'm 
just missing some experience working with it for now :)

> However, there's still another issue:
> 
>   $ ./pre-inst-guile -q --debug -c 0
>   ;;; Succeeds.
> 
>   $ ./pre-inst-guile -q --debug -c '(use-modules (ice-9 r5rs))'
> 
>   Backtrace:
>   In current input:
>      1:  0* (use-modules (ice-9 r5rs))
>      1:  1  (eval-when (eval load compile) (process-use-modules (list (list #))) ...)
>      1:  2  (begin (process-use-modules (list (list #))) *unspecified*)
>      ?:  3* [process-use-modules (((ice-9 r5rs)))]
>      ?:  4  (let* ((interfaces #)) (call-with-deferred-observers (lambda () #)))
>      ?:  5* [map #<procedure #f (mif-args)> (((ice-9 r5rs)))]
>      ?:  6* [#<procedure #f (mif-args)> ((ice-9 r5rs))]
>      ?:  7* (or (apply resolve-interface mif-args) (error "no such module" mif-args))
>      ?:  8* [apply #<procedure resolve-interface (name . args)> ((ice-9 r5rs))]
>      ?:  9  [resolve-interface (ice-9 r5rs)]
>       ...
>      ?: 10  (let* (# # # # ...) (and # #) (if # public-i #))
>      ?: 11* (and (or (not #) (not #)) (error "no code for module" name))
>      ?: 12  [error "no code for module" (ice-9 r5rs)]
>       ...
>      ?: 13  [scm-error misc-error #f "~A ~S" ("no code for module" (ice-9 r5rs)) #f]
> 
>   <unnamed port>: In procedure scm-error in expression (scm-error (quote misc-error) #f ...):
>   <unnamed port>: no code for module (ice-9 r5rs)
> 
> Looking with strace(1) shows that ice-9/r5rs.{scm,go} aren't loaded at
> all here.

Hm... No ideas yet, but I will look into that problem now; and maybe I 
can  still find the solution, even though I'm not yet really 
knowledge-able about Guile's code :D

Yours,
Daniel




      reply	other threads:[~2009-04-07 15:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-28 12:06 Patch: Some work towards making --disable-deprecated compile Daniel Kraft
2009-04-05 18:21 ` Ludovic Courtès
2009-04-07 15:56   ` Daniel Kraft [this message]

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=49DB779D.7010802@domob.eu \
    --to=d@domob.eu \
    --cc=guile-devel@gnu.org \
    --cc=ludo@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).