guile-devel
[Top][All Lists]
Advanced

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

Re: SCM_BOOL_T became #nil -- et al. ?


From: Andy Wingo
Subject: Re: SCM_BOOL_T became #nil -- et al. ?
Date: Fri, 25 Feb 2011 12:07:45 +0100
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/23.2 (gnu/linux)

On Wed 23 Feb 2011 21:14, Bruce Korb <address@hidden> writes:

> * Developers should be clearly warned that -I/usr/local/include
>   needs to be after all other -I options, due to guile
>   header naming conflicts.

This is incorrect.  Guile 2.0 (and later) does not add
-I/usr/local/include to the CFLAGS in any configuration.  If you install
to /usr/local, it adds -I/usr/local/include/guile/2.0, or /2.2, etc.

The problem this thread is about is if you have Guile 1.8 or previous
eheaders installed in /usr.

Andy
-- 
http://wingolog.org/



reply via email to

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