unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: bornlibra23 <awarikoo@nse.co.in>
To: Guile-user@gnu.org
Subject: Re: Guile Build Errors
Date: Tue, 1 Sep 2009 01:30:20 -0700 (PDT)	[thread overview]
Message-ID: <25236356.post@talk.nabble.com> (raw)
In-Reply-To: <87ljl040px.fsf@gnu.org>


Hello Ludo'
I am new to the opensource world & coundnt understand some of your more
cryptic directions. I couldnt get the head or tail of the os deppendency
file. Perhaps you could ask me some questions like wether stack grows from
top or bottom & like to make me understand what the file requires.

>Woow, I had never seen this one, thanks for trying out.  ;-)
Its nice to do new things.

>Can you post the GNU triplet as returned by `./build-aux/config.guess'?
bash-2.05$ ./build-aux/config.guess
i786-stratus-vos

>Can you show the output of "grep -A2 -E '(libtool supports|shared lib)'
config.log" (assuming GNU grep here)?
bash-2.05$ grep -A2 -E '(libtool supports|shared lib)' config.log
configure:9171: checking whether the
/users/awarikoo/OpenSource/guile-1.8.7/buil
+d-aux/compile gcc linker (/system/gnu_library/bin/ld) supports shared
libraries
configure:10245: result: no
configure:10484: checking dynamic linker characteristics
--
configure:12167: checking if libtool supports shared libraries
configure:12169: result: no
configure:12172: checking whether to build shared libraries
configure:12193: result: no
configure:12196: checking whether to build static libraries
--
configure:28594: checking for shared library run path origin
configure:28607: result: done
configure:29108: checking for CFPreferencesCopyAppValue

>It shows that there's something wrong GC-wise.  It could be that the stack
is not correctly scanned on this platform.
>Could you try to reproduce the problem with a simple test case, e.g., by
running `./pre-inst-guile' and trying
>  (begin
>    (string-append (make-string 123) (make-string 123))
>    (gc))
>and variants thereof to try to trigger the problem?
bash-2.05$ ./pre-inst-guile
Backtrace:
In unknown file:
   ?: 47  (let (# #) (dynamic-wind # thunk #))
   ?: 48  [dynamic-wind #<procedure #f ()> #<procedure #f ()> #<procedure #f
()>]
   ?: 49* [#<procedure #f ()>]
   ?: 50* [primitive-load
"/users/awarikoo/OpenSource/guile-1.8.7/ice-9/safe-r5rs.scm"]
In /users/awarikoo/OpenSource/guile-1.8.7/ice-9/safe-r5rs.scm:
  20: 51* (define-module (ice-9 safe-r5rs) :re-export ...)
  20: 52  (eval-case (# #) (else #))
In unknown file:
    ...
   ?: 53  (let* ((m (process-define-module #))) (set-current-module m) m)
   ?: 54* [process-define-module (# # # # ...)]
   ?: 55  (let* (# # # #) (beautify-user-module! module) (# kws # # ...)
...)
   ?: 56* [loop (#:re-export (eqv? eq? equal? ...) #:export ...) () ...]
   ?: 57  (if (null? kws) (call-with-deferred-observers (lambda () # ...))
...)
    ...
   ?: 58  [dynamic-wind #<procedure #f ()> #<procedure #f ()> #<procedure #f
()>]
   ?: 59* [#<procedure #f ()>]
   ?: 60* [module-re-export! #<directory # 400abd50> (eqv? eq? equal?
number? ...)]
   ?: 61  (let* ((public-i #)) (for-each (lambda # #) names))
   ?: 62  [for-each #<procedure #f (name)> (eqv? eq? equal? ...)]
   ?: 63* [#<procedure #f (name)> string-ci<?]
   ?: 64* (let* ((var #)) (cond (# #) (# #) (else #)))
   ?: 65  (cond (# #) (# #) (else #))
    ...
   ?: 66  [scm-error misc-error #f "~A ~S" ("Undefined variable:"
string-ci<?) #f]

<unnamed port>: In procedure scm-error in expression (scm-error (quote
misc-error) #f ...):
<unnamed port>: Undefined variable: string-ci<?
bash-2.05$ (begin (string-append (make-string 123) (make-string 123)) (gc))
bash: syntax error near unexpected token `(string-append'

>You may want to look at `libguile/gc_os_dep.c' to see how it determines the
stack and whether it makes sense?
>You might need to add a new series of #ifdefs, possibly borrowed from
upstream libgc
>(http://bdwgc.cvs.sourceforge.net/viewvc/bdwgc/bdwgc/os_dep.c?revision=1.42&view=markup).
I will have a look at that after I get more understanding about the
compilation issues

>Can you also try `./check-guile' and report back?

bash-2.05$ ./check-guile
Testing /users/awarikoo/OpenSource/guile-1.8.7/pre-inst-guile ...
with GUILE_LOAD_PATH=/users/awarikoo/OpenSource/guile-1.8.7/test-suite
ERROR: In procedure symbol->string:
ERROR: Wrong type argument in position 1 (expecting symbol): #<freed cell
40087fd0; GC missed a reference>

Thanks
bornlibra23
-- 
View this message in context: http://www.nabble.com/Guile-Build-Errors-tp25167250p25236356.html
Sent from the Gnu - Guile - User mailing list archive at Nabble.com.





  reply	other threads:[~2009-09-01  8:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-27  8:19 Guile Build Errors bornlibra23
2009-08-31 12:38 ` Ludovic Courtès
2009-09-01  8:30   ` bornlibra23 [this message]
2009-09-02  8:44     ` Ludovic Courtès
2009-09-02  9:29       ` bornlibra23
2009-09-02 11:49         ` Ludovic Courtès
2009-10-04 22:25           ` Neil Jerram
2009-10-05  9:02             ` 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=25236356.post@talk.nabble.com \
    --to=awarikoo@nse.co.in \
    --cc=Guile-user@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).