[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: problems in guile installation,help me

From: Jon Wilson
Subject: Re: problems in guile installation,help me
Date: Fri, 01 Dec 2006 22:16:41 -0600
User-agent: Thunderbird (X11/20061115)

Hi Gopi,
It is best if write replies not to me but to address@hidden That way everyone on the list can see and help. I'm no guru, so it is quite probable that you'll run into something I can't fix, or that I don't know the best way to fix.

Do you know what libc you are using? That might help with the alloca problem. It looks to me like a bug (whether in guile, or in gnu autotools, or in BSD's libc I don't know), and it'd be best if we could figure out how to prevent it from happening again for anyone else.

About the first problem you had, with the guile configure script being unable to find libtool: did you reboot your machine or anything like that in between having the problem and not having the problem? These bugs which spontaneously disappear are the hardest to fix permanently.

Gopi kumaran wrote:
Hi Jon
Thanks for the reply.Now i dont have a problem with alloca what i did is i went to /usr/include/libguile/eval.c line number 50 and commented #define alloca _alloca.I didnt get that redefined problem again.But after seeing ur mail i removed the comment and added #undef alloca in line 43.Now make runs without any problem.The crazy thing is even after i remove the comment and removed the undef alloca(which u said,just to check what will happen), i was shocked that i didnt get any error of alloca redfined :).I dont know why this make , ./configure behaves differently sometimes.anyhow iam continuing with ur #undef on line 43 to next error i.e permission denied.let me see that and reply u in another mail. Gopi

*/Jon Wilson <address@hidden>/* wrote:

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

    #undef alloca

    See if that works. If so, I would file a bug report, with details
    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.

    Gopi kumaran wrote:
    > Hi Jon,
    > Thanks for your reply. I somehow solved that problem. Now I am
    > 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 /* 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,
    > running ldconfig (as root, btw), make sure that the directory your
    > new
    > shared libs are in is listed in /etc/, 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, ignore this
    > message.
    > Hope that helps.
    > Regards,
    > Jon
    > Want to start your own business? Learn how on Yahoo! Small

    Guile-user mailing list

Need a quick answer? Get one in minutes from people who know. Ask your question on Yahoo! Answers <;_ylc=X3oDMTFvbGNhMGE3BF9TAzM5NjU0NTEwOARfcwMzOTY1NDUxMDMEc2VjA21haWxfdGFnbGluZQRzbGsDbWFpbF90YWcx>.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]