From: Marc Glisse <marc.glisse@inria.fr>
To: Vincent Diepeveen <diep@xs4all.nl>
Cc: gcc-help@gcc.gnu.org
Subject: Re: GCC 4.7 build problems
Date: Sun, 15 Apr 2012 20:46:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.02.1204152236450.2580@laptop-mg.saclay.inria.fr> (raw)
In-Reply-To: <D9673A3C-0383-4D17-BC52-667AF6FB2905@xs4all.nl>
On Sun, 15 Apr 2012, Vincent Diepeveen wrote:
> Seems libmpc.so.2 is the file it couldn't find.
> I could find it in /usr/local/lib
>
> when i typed
> echo $PATH
>
> then indeed /usr/local/lib wasn't in the path
>
> typed:
> export PATH=/usr/local/lib:$PATH
That might make sense on windows but not on unix, where libraries and
executables are separated.
> I must set a librarypath maybe, if so, what is its name?
man ld.so
(really, there are several ways and the best one is for you to chose)
http://gcc.gnu.org/install/configure.html
mentions the name of an environment variable in the paragraph about mpc.
The entry in the FAQ just before the one I referred to gives a simple
technique to work around this issue.
--
Marc Glisse
next prev parent reply other threads:[~2012-04-15 20:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <171979E8-3362-4C94-B69A-2757BF6BB24B@xs4all.nl>
[not found] ` <alpine.DEB.2.02.1204151834250.2580@laptop-mg.saclay.inria.fr>
2012-04-15 20:29 ` Vincent Diepeveen
2012-04-15 20:46 ` Marc Glisse [this message]
2012-04-15 21:00 ` Jonathan Wakely
2012-04-15 21:10 ` Vincent Diepeveen
2012-04-15 21:13 ` Jonathan Wakely
2012-04-15 21:15 ` Jonathan Wakely
2012-04-15 21:52 ` Vincent Diepeveen
2012-04-15 22:00 ` Jonathan Wakely
2012-04-15 22:03 ` Jonathan Wakely
2012-04-15 22:24 ` Vincent Diepeveen
2012-04-15 23:19 ` Jonathan Wakely
2012-04-15 23:37 ` Vincent Diepeveen
2012-04-16 0:25 ` Vincent Diepeveen
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.DEB.2.02.1204152236450.2580@laptop-mg.saclay.inria.fr \
--to=marc.glisse@inria.fr \
--cc=diep@xs4all.nl \
--cc=gcc-help@gcc.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).