unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Jon Wilson <j85wilson@fastmail.fm>
Subject: Re: problems in guile installation,help me
Date: Fri, 01 Dec 2006 10:20:17 -0600	[thread overview]
Message-ID: <45705641.6080005@fastmail.fm> (raw)
In-Reply-To: <399061.39178.qm@web37704.mail.mud.yahoo.com>

Hi Gopi,
Try adding, in eval.c, a line just before line 44, which is as follows:

#undef alloca

See if that works.  If so, I would file a bug report, with details about 
your BSD system, and what you had to do to make it work.

I'm doubtful that this is a real solution to the underlying problem, but 
it should be a quick fix that gets you up and running with guile.
Regards,
Jon

Gopi kumaran wrote:
> Hi Jon,
> Thanks for your reply. I somehow solved that problem. Now I am getting 
> a new error in make command in guile. The error says that
>  eval.c:44:1: "alloca" redefined
> In file included from ../libguile/scmconfig.h:29,
>                      from ../libguile/__scm.h:76,
>                      from eval.c:36:
> /usr/include/stdlib.h:230:1: this is the location of the 
> previous definition
> Error code 1
>  
>  
>  
> Expecting your early reply
>  
> regards
> Gopi    
>
> */Jon Wilson <j85wilson@fastmail.fm>/* wrote:
>
>     Hi Gopi,
>     Could you please send plain text emails with the actual message in
>     the
>     body of the email rather than an attached forwarded message? This
>     sort
>     of thing is slightly annoying and makes it slightly more difficult
>     for
>     us to help you.
>
>     I'm not really familiar with the BSDs, but perhaps you need to run
>     ldconfig (8).
>
>     From the manpage:
>
>     "/sbin/ldconfig - configure dynamic linker run time bindings"
>
>     This is often required after installing new shared libraries. If you
>     forget this step, the dynamic loader doesn't know where to find the
>     libs, regardless of them being in the correct directory. Also, before
>     running ldconfig (as root, btw), make sure that the directory your
>     new
>     shared libs are in is listed in /etc/ld.so.conf, otherwise
>     ldconfig will
>     not think to look there.
>
>     Of course, I don't know that BSD uses the same dynamic loading
>     system as
>     linux, so if you don't find ldconfig or ld.so.conf, ignore this
>     message.
>
>     Hope that helps.
>
>     Regards,
>     Jon
>
>
>
>
> ------------------------------------------------------------------------
> Want to start your own business? Learn how on Yahoo! Small Business. 
> <http://us.rd.yahoo.com/evt=41244/*http://smallbusiness.yahoo.com/r-index> 




_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-user


       reply	other threads:[~2006-12-01 16:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <399061.39178.qm@web37704.mail.mud.yahoo.com>
2006-12-01 16:20 ` Jon Wilson [this message]
2006-12-02 14:27   ` problems in guile installation,help me Neil Jerram
     [not found] <20061202033711.76193.qmail@web37713.mail.mud.yahoo.com>
2006-12-02  4:16 ` Jon Wilson
2006-11-29  9:54 Gopi kumaran
  -- strict thread matches above, loose matches on Subject: below --
2006-11-29  9:52 Gopi kumaran
2006-12-01  4:05 ` Jon Wilson

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=45705641.6080005@fastmail.fm \
    --to=j85wilson@fastmail.fm \
    /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).