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

2011-02-23 Thread Bruce Korb
On 02/22/11 20:15, Ken Raeburn wrote: > On Feb 22, 2011, at 07:00, Hans Aberg wrote: Perhaps 2.0 should have some check that it gets the right header. > > It wouldn't be that tough to do something like: > #define scm_init_guile scm_init_guile_v2_0 // encode version in symbol [...] > and te

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

2011-02-24 Thread Ken Raeburn
On Feb 23, 2011, at 15:14, Bruce Korb wrote: > * guile should provide autoconf macros to do checking, > like for wrong version headers. That seems like a good idea, but unless all the other packages' header directories have already been added to the include path by the time this test is run, it

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

2011-02-24 Thread Bruce Korb
On 02/24/11 08:35, Ken Raeburn wrote: > On Feb 23, 2011, at 15:14, Bruce Korb wrote: >> * guile should provide autoconf macros to do checking, >> like for wrong version headers. > > That seems like a good idea, but unless all the other packages' > header directories have already been added to the

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

2011-02-25 Thread Andy Wingo
On Thu 24 Feb 2011 17:35, Ken Raeburn writes: > If the library ABI is tweaked to code the version into a symbol name, > this test could become a simple compile-and-link test. Of course, that > approach has other issues, like getting backwards-compatible library > upgrades to work without recompi

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

2011-02-25 Thread Andy Wingo
On Wed 23 Feb 2011 21:14, Bruce Korb 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 co

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

2011-02-25 Thread Hans Aberg
On 25 Feb 2011, at 12:07, Andy Wingo wrote: >> * 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 a

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

2011-02-25 Thread Andy Wingo
On Fri 25 Feb 2011 12:46, Hans Aberg writes: > $ guile-config compile > -D_THREAD_SAFE -I/usr/local/include/guile/2.0 -I/usr/local/include The -I/usr/local/include is added for some other library that Guile depends on -- GMP or libgc or something else. For example on my system I have Guil

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

2011-02-25 Thread Hans Aberg
On 25 Feb 2011, at 13:42, Andy Wingo wrote: >> $ guile-config compile >> -D_THREAD_SAFE -I/usr/local/include/guile/2.0 -I/usr/local/include > > The -I/usr/local/include is added for some other library that Guile > depends on -- GMP or libgc or something else. > > For example on my system I h