From: "Germán Arias" <germanandre@gmx.es>
To: guile-user@gnu.org
Subject: Re: Install Guile 2.0.11 failed on L-Ubuntu 12.04
Date: Sat, 24 May 2014 23:12:21 -0600 [thread overview]
Message-ID: <fcac28c51d03a93a19ab0b0a7d95095c@german-desktop> (raw)
In-Reply-To: <CALC+4DCdy_ej2ReGCxU2KZmxp44-2vJ5JEGFnZVGSigbLgrizg@mail.gmail.com>
Hi Mark
On 2014-05-24 15:21:11 -0600 mark damerell <markdamerell@googlemail.com> wrote:
> Trying to install guile 2.0.11 on L-ubuntu 12.04. Shell is /bin/bash .
>
> Downloaded the tarfile from the Gnu website.
>
> configured with no options
>
> make check produced warnings and "unresolved" messages and one failure,
> bug 27450. It said "please report this" but I believe that as this is a
> known
> bug, you do not want me to.
>
>
> make install ran with no visible error.
>
>
> make installcheck failed. After several "nothing to do" messages, it said:
>
> make[1]: Entering directory `/home/manager/downloads/guile-2.0.11/examples'
> /bin/mkdir -p box
> gcc `PATH=/usr/local/bin:$PATH PKG_CONFIG_PATH=/usr/local/lib/pkgconfig
> /usr/local/bin/guile-config compile` -c box/box.c -o box/box.o
> /usr/local/bin/guile: error while loading shared libraries:
> libguile-2.0.so.22: cannot open shared object file: No such file or
> directory
> box/box.c:22:22: fatal error: libguile.h: No such file or directory
> compilation terminated.
> make[1]: *** [box/box.o] Error 1
>
>
> The shell command
>
> guile
>
> produces
>
> guile: error while loading shared libraries: libguile-2.0.so.22: cannot
> open shared object file: No such file or directory
>
>
> find(1) found both files:
>
> /usr/local/include/guile/2.0/libguile.h
> /usr/local/lib/libguile-2.0.so.22
>
>
> I conjecture that gcc was using incorrect search paths. So I did:
>
> printenv | grep -i path
>
> and got:
>
> XDG_SESSION_PATH=/org/freedesktop/DisplayManager/Session0
> XDG_SEAT_PATH=/org/freedesktop/DisplayManager/Seat0
> DEFAULTS_PATH=/usr/share/gconf/Lubuntu.default.path
> PATH=/usr/lib/lightdm/lightdm:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
> MANDATORY_PATH=/usr/share/gconf/Lubuntu.mandatory.path
>
>
> I expected to see a CPATH and a LIBRARY_PATH as described in man gcc.
>
> Please is this problem known? what should I do about it? Thank you.
>
In general, when you install something from a source tarball this is installed in non standard path. So, to use guile you should add the path where this is installed. At your file ".profile" (in your user directory) you could add:
export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/lib
To use the headers, you will need make a symbolic link at /usr/include. Something like:
sudo ln -s /usr/local/include/guile/ /usr/include/
Hope this help.
Germán.
next prev parent reply other threads:[~2014-05-25 5:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-24 21:21 Install Guile 2.0.11 failed on L-Ubuntu 12.04 mark damerell
2014-05-25 5:12 ` Germán Arias [this message]
2014-05-25 9:10 ` Chris Vine
2014-05-25 23:59 ` Germán Arias
2014-05-26 21:10 ` Chris Vine
2014-05-27 6:28 ` Germán Arias
-- strict thread matches above, loose matches on Subject: below --
2014-05-27 9:32 mark damerell
2014-05-27 10:38 ` Chris Vine
2014-05-28 8:36 ` mark damerell
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=fcac28c51d03a93a19ab0b0a7d95095c@german-desktop \
--to=germanandre@gmx.es \
--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).