From: Matt Kraai <kraai@ftbfs.org>
Cc: bug-guile@gnu.org
Subject: Re: Does not find header files or libraries under /usr/local
Date: Sat, 27 May 2006 16:17:02 -0700 [thread overview]
Message-ID: <20060527231702.GA2546@localhost.localdomain> (raw)
In-Reply-To: <87bqtjkr62.fsf@zagadka.de>
[-- Attachment #1.1: Type: text/plain, Size: 979 bytes --]
On Sun, May 28, 2006 at 02:02:13AM +0300, Marius Vollmer wrote:
> Matt Kraai <kraai@ftbfs.org> writes:
>
> > When I tried to compile Guile on a QNX 6.3.0 system, it did not find
> > the libtool and gmp libraries or the gmp header files that I'd built
> > and installed under /usr/local until I set the CPPFLAGS environment
> > variable to -I/usr/local/include and the LDFLAGS environment variable
> > to -L/usr/local/lib.
>
> That is expected. See this part of the README:
>
> Guile expects to be able to find these packages in the default
> compiler setup, it does not try to make any special arrangements
> itself. For example, for the `readline' package, Guile expects to
> be able to find the include file <readline/readline.h>, without
> passing any special `-I' options to the compiler.
So the correct solution is to ensure that the compiler looks in
/usr/local? Do you know why other programs don't require this?
--
Matt
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
[-- Attachment #2: Type: text/plain, Size: 137 bytes --]
_______________________________________________
Bug-guile mailing list
Bug-guile@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-guile
next prev parent reply other threads:[~2006-05-27 23:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-08 20:39 Does not find header files or libraries under /usr/local Matt Kraai
2006-05-27 23:02 ` Marius Vollmer
2006-05-27 23:17 ` Matt Kraai [this message]
2006-05-27 23:29 ` Marius Vollmer
2006-05-28 0:52 ` Matt Kraai
2006-05-30 14:56 ` Ludovic Courtès
2006-05-31 1:30 ` Kevin Ryde
2006-05-31 7:12 ` 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=20060527231702.GA2546@localhost.localdomain \
--to=kraai@ftbfs.org \
--cc=bug-guile@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).