> On 13 Dec 2014, at 20:28, John Ralls wrote:
>
> Attempting to build Guile 2.0.11 on OS X 10.10 with Xcode 6.1.1 and
> MacOS10.10.sdk fails:
It worked fine with the version before, Xcode 6.1 [1].
1. https://developer.apple.com/downloads/index.action
> On 5 Dec 2014, at 00:47, Mark H Weaver wrote:
>
> Hans Aberg writes:
>
>>> On 4 Dec 2014, at 18:23, Ludovic Courtès wrote:
>>>
>>> Hans Aberg skribis:
>>>
>>>>> On 3 Dec 2014, at 23:21, Ludovic Courtès wrote:
>>>&
> On 4 Dec 2014, at 18:23, Ludovic Courtès wrote:
>
> Hans Aberg skribis:
>
>>> On 3 Dec 2014, at 23:21, Ludovic Courtès wrote:
>>>
>>> Could it be because Guile is being compiled against libeditline instead
>>> of GNU Readline?
>>
> On 3 Dec 2014, at 23:21, Ludovic Courtès wrote:
>
> Could it be because Guile is being compiled against libeditline instead
> of GNU Readline?
>
> Readline support in Guile requires GNU Readline.
It looked as though that the readline in the Guile distribution is too old - no
other readline
> On 2 Dec 2014, at 18:24, Mark H Weaver wrote:
>
> Hans Aberg writes:
>
>> The GC URL has changed to [1]; the guile-2.0.11 file README gives an old one.
>>
>> 1. http://www.hboehm.info/gc/
>
> Already fixed in d2fcbb193b67106d0c0b57cd1e988acf2d30ace7, wh
I get a build error [1] with guile-2.0.11 on OS X 10.10.1. It looks like an
illegal int to pointer conversion cause a name to not be defined, and then the
linking fails.
1. make
...
Making all in guile-readline
SNARF readline.x
/Applications/Xcode.app/Contents/Developer/usr/bin/make all-am
The GC URL has changed to [1]; the guile-2.0.11 file README gives an old one.
1. http://www.hboehm.info/gc/
On 6 Jul 2012, at 20:23, Andy Wingo wrote:
> Closing this one as done then. Whenever you give a newer Guile a try
> (like tomorrow's 2.0.6), we can look again.
Two tests failed. Drop me a note if you want further investigation.
Hans
$ make check
GEN public-submodule-commit
make c
On 1 Feb 2012, at 15:53, Andy Wingo wrote:
>> There is no issue with libffi from latest GIT compiled with
>> llvm-gcc-4.2, and guile-2.0.5 compiled with SVN gcc-4.7.
>
> But there is an issue with libffi from git compiled with llvm-gcc-4.2,
> and guile-2.0.5 compiled with llvm-gcc-4.2?
Right, on
On 1 Feb 2012, at 02:42, Mark H Weaver wrote:
>> Running bytevectors.test
>> FAIL: bytevectors.test: 2.3 Operations on Bytes and Octets:
>> bytevector-sint-ref [small] (eval)
>> FAIL: bytevectors.test: 2.3 Operations on Bytes and Octets:
>> bytevector-sint-ref [small] (compile)
>
> In the direc
On 1 Feb 2012, at 12:50, Andy Wingo wrote:
>> It suggests that problem is with llvm-gcc (an clang), I think. With
>> gcc-4.7 there is no libffi failure.
>
> Is it correct to say that you experience this issue if libffi is
> compiled with llvm-gcc / clang, …
Yes, and also guile-2.0.5 (see below f
On 1 Feb 2012, at 02:42, Mark H Weaver wrote:
> Hans Aberg writes:
>> With gcc-4.7.0 (from SVN), the test-ffi test now passes (libffi from
>> GIT)
>
> Excellent! I guess that this was a libffi bug.
No, I think it is with llvm-gcc, in view of that it remained in that comp
On 1 Feb 2012, at 02:49, Mark H Weaver wrote:
>> After doing this, the same failure with the LLVM-GCC compiler:
>> /usr/bin/cc -> llvm-gcc-4.2
>> /usr/bin/gcc -> llvm-gcc-4.2
>> i686-apple-darwin11-llvm-gcc-4.2 (GCC) 4.2.1
>>
>> This is the compiler that one will use on OS X 10.7 if one instal
On 31 Jan 2012, at 20:35, Mark H Weaver wrote:
The 'make check' gives this error, on OS X 10.7.2 using the compiler
i686-apple-darwin11-llvm-gcc-4.2 (GCC) 4.2.1 supplied by Xcode 4.2.1:
PASS: test-asmobs
bad return from expression `(f-sum -1 2000 -3 400)': exp
On 31 Jan 2012, at 20:35, Mark H Weaver wrote:
The 'make check' gives this error, on OS X 10.7.2 using the compiler
i686-apple-darwin11-llvm-gcc-4.2 (GCC) 4.2.1 supplied by Xcode 4.2.1:
PASS: test-asmobs
bad return from expression `(f-sum -1 2000 -3 400)': exp
On 31 Jan 2012, at 20:35, Mark H Weaver wrote:
The 'make check' gives this error, on OS X 10.7.2 using the compiler
i686-apple-darwin11-llvm-gcc-4.2 (GCC) 4.2.1 supplied by Xcode 4.2.1:
PASS: test-asmobs
bad return from expression `(f-sum -1 2000 -3 400)': exp
On 31 Jan 2012, at 20:35, Mark H Weaver wrote:
The 'make check' gives this error, on OS X 10.7.2 using the compiler
i686-apple-darwin11-llvm-gcc-4.2 (GCC) 4.2.1 supplied by Xcode 4.2.1:
PASS: test-asmobs
bad return from expression `(f-sum -1 2000 -3 400)': exp
On 31 Jan 2012, at 19:04, Mark H Weaver wrote:
>> The 'make check' gives this error, on OS X 10.7.2 using the compiler
>> i686-apple-darwin11-llvm-gcc-4.2 (GCC) 4.2.1 supplied by Xcode 4.2.1:
>>
>> PASS: test-asmobs
>> bad return from expression `(f-sum -1 2000 -3 400)': expected
>>
On 31 Jan 2012, at 16:18, Ludovic Courtès wrote:
>> The 'make check' gives this error, on OS X 10.7.2 using the compiler
>> i686-apple-darwin11-llvm-gcc-4.2 (GCC) 4.2.1 supplied by Xcode 4.2.1:
>
> What is this? Apple’s GCC? DragonEgg?
On OS X 10.7.2, Xcode 4.2 installs two system compilers
On 31 Jan 2012, at 15:40, Andy Wingo wrote:
> https://savannah.gnu.org/bugs/?30122
I used /usr/bin/gcc -> llvm-gcc-4.2, which is different from clang.
There is also this one
http://lists.gnu.org/archive/html/bug-guile/2011-11/msg00026.html
It asks for this output:
$ grep scm_t_int8 libguile/
On 30 Jan 2012, at 23:02, Ludovic Courtès wrote:
> We are pleased to announce GNU Guile release 2.0.5.
The 'make check' gives this error, on OS X 10.7.2 using the compiler
i686-apple-darwin11-llvm-gcc-4.2 (GCC) 4.2.1 supplied by Xcode 4.2.1:
PASS: test-asmobs
bad return from expression `(f-su
On 18 Nov 2011, at 07:38, Andy Wingo wrote:
With guile-2.0.3, OS X 10.7.2, Xcode 4.2,
i686-apple-darwin11-llvm-gcc-4.2 (GCC) 4.2.1, 'make check' fails on
test-ffi. Here, libffi-3.0.9 is used; libffi-3.0.10 does not compile
with the same setup.
>>>
>>> How does it fail?
>>
>>
On 16 Nov 2011, at 20:30, Andy Wingo wrote:
>> With guile-2.0.3, OS X 10.7.2, Xcode 4.2,
>> i686-apple-darwin11-llvm-gcc-4.2 (GCC) 4.2.1, 'make check' fails on
>> test-ffi. Here, libffi-3.0.9 is used; libffi-3.0.10 does not compile
>> with the same setup.
>
> How does it fail?
I redid the check
On 16 Nov 2011, at 22:46, Andy Wingo wrote:
> On Wed 16 Nov 2011 21:16, Hans Aberg writes:
>
>> On 16 Nov 2011, at 20:30, Andy Wingo wrote:
>>
>>> On Thu 10 Nov 2011 22:16, Hans Aberg writes:
>>>
>>>> With guile-2.0.3, OS X 10.7.2, Xcode
On 16 Nov 2011, at 20:30, Andy Wingo wrote:
> On Thu 10 Nov 2011 22:16, Hans Aberg writes:
>
>> With guile-2.0.3, OS X 10.7.2, Xcode 4.2,
>> i686-apple-darwin11-llvm-gcc-4.2 (GCC) 4.2.1, 'make check' fails on
>> test-ffi. Here, libffi-3.0.9 is used; libffi-3
With guile-2.0.3, OS X 10.7.2, Xcode 4.2, i686-apple-darwin11-llvm-gcc-4.2
(GCC) 4.2.1, 'make check' fails on test-ffi. Here, libffi-3.0.9 is used;
libffi-3.0.10 does not compile with the same setup.
Hans
For a bugreport, I tried to recompile the old Guile-1.9.15 on OS X 7.2, with
Xcode 4.2, i686-apple-darwin11-llvm-gcc-4.2 (GCC) 4.2.1, and I got the error
below. I wonder what it means. It is not really important, since it is an old
version.
Hans
$ make V=1
make all-recursive
Making all in l
On 12 Aug 2011, at 22:08, Andy Wingo wrote:
>> FYI: running this file with Guile 2.0.2, the last test claims does not have
>> call/cc safe 'map'.
>> http://sisc-scheme.org/r5rs_pitfall.scm
>
> This behaviour is permissible in the R5RS. In R6RS it is not, and it
> doesn't look like it will be p
FYI: running this file with Guile 2.0.2, the last test claims does not have
call/cc safe 'map'.
http://sisc-scheme.org/r5rs_pitfall.scm
Hans
On 17 Jun 2011, at 11:26, Andy Wingo wrote:
On Mac OS X 10.6.7, compiled using Xcode Version 3.2.6 64-bit,
i686-apple-darwin10-gcc-4.2.1 (GCC) 4.2.1, scm_init_guile() gives the
error:
Failed to get stack base for current thread.
>>
>>> As you can see we rely on libgc her
On 25 May 2011, at 18:54, Mark H Weaver wrote:
Right, but as the result is unspecified according to the standard, the
Guile manual suggests that the value SCM_UNSPECIFIED as an
interpretation of that. I merely say that I think it would be a good
idea.
>> ...
>>> Having said all
On 25 May 2011, at 02:25, Mark H Weaver wrote:
>> Right, but as the result is unspecified according to the standard, the
>> Guile manual suggests that the value SCM_UNSPECIFIED as an
>> interpretation of that. I merely say that I think it would be a good
>> idea.
...
> Having said all this, one co
On 24 May 2011, at 17:07, Andy Wingo wrote:
The Guile manual, sec. 10.2.5.2, says that SCM_UNSPECIFIED is to be used
when the Scheme standard says the return is an unspecified value.
So this Lisp extension breaks off from that. If one wants it, > perhaps,
there should b
On 24 May 2011, at 15:11, Andy Wingo wrote:
> But, it is 1 and 2, currently. (+ FOO) inlines just to FOO, too
> optimistically.
It is unspecified according to rsr5.
>>>
>>> I know. I'm talking about Guile here.
>>
>> The Guile manual, sec. 10.2.5.2, says that SCM_UNSPECIFIED
On 23 May 2011, at 15:49, Andy Wingo wrote:
>>> But, it is 1 and 2, currently. (+ FOO) inlines just to FOO, too
>>> optimistically.
>>
>> It is unspecified according to rsr5.
>
> I know. I'm talking about Guile here.
The Guile manual, sec. 10.2.5.2, says that SCM_UNSPECIFIED is to be used whe
On 23 May 2011, at 15:49, Andy Wingo wrote:
>>> But, it is 1 and 2, currently. (+ FOO) inlines just to FOO, too
>>> optimistically.
>>
>> It is unspecified according to rsr5.
>
> I know. I'm talking about Guile here.
I know. You perhaps haven't described clearly enough what it should be. If
On 22 May 2011, at 16:02, Andy Wingo wrote:
> But, it is 1 and 2, currently. (+ FOO) inlines just to FOO, too
> optimistically.
It is unspecified according to rsr5.
Hans
On 20 May 2011, at 12:11, Andy Wingo wrote:
>> On Mac OS X 10.6.7, compiled using Xcode Version 3.2.6 64-bit,
>> i686-apple-darwin10-gcc-4.2.1 (GCC) 4.2.1, scm_init_guile() gives the
>> error:
>>
>> Failed to get stack base for current thread.
> As you can see we rely on libgc here, and so this
On 20 May 2011, at 12:11, Andy Wingo wrote:
>> On Mac OS X 10.6.7, compiled using Xcode Version 3.2.6 64-bit,
>> i686-apple-darwin10-gcc-4.2.1 (GCC) 4.2.1, scm_init_guile() gives the
>> error:
>>
>> Failed to get stack base for current thread.
>
> The code in question does this:
>
>void
>
On 20 May 2011, at 15:58, Andy Wingo wrote:
> Did you enable threads? `grep PTHREAD scmconfig.h` to check.
$ grep PTHREAD libguile/scmconfig.h
#define SCM_USE_PTHREAD_THREADS 1 /* 0 or 1 */
/* Define to 1 if need braces around PTHREAD_ONCE_INIT (for Solaris). */
#define SCM_NEED_BRACES_ON_PTHREAD
On 20 May 2011, at 15:10, Andy Wingo wrote:
On Mac OS X 10.6.7, compiled using Xcode Version 3.2.6 64-bit,
i686-apple-darwin10-gcc-4.2.1 (GCC) 4.2.1, scm_init_guile() gives the
error:
Failed to get stack base for current thread.
>> ...
>>> As you can see we rely on libgc
On 20 May 2011, at 12:11, Andy Wingo wrote:
>> On Mac OS X 10.6.7, compiled using Xcode Version 3.2.6 64-bit,
>> i686-apple-darwin10-gcc-4.2.1 (GCC) 4.2.1, scm_init_guile() gives the
>> error:
>>
>> Failed to get stack base for current thread.
...
> As you can see we rely on libgc here, and so t
On 20 May 2011, at 12:11, Andy Wingo wrote:
>> On Mac OS X 10.6.7, compiled using Xcode Version 3.2.6 64-bit,
>> i686-apple-darwin10-gcc-4.2.1 (GCC) 4.2.1, scm_init_guile() gives the
>> error:
>>
>> Failed to get stack base for current thread.
>
> The code in question does this:
>
>void
>
On Mac OS X 10.6.7, compiled using Xcode Version 3.2.6 64-bit,
i686-apple-darwin10-gcc-4.2.1 (GCC) 4.2.1, scm_init_guile() gives the error:
Failed to get stack base for current thread.
The program 'guile' works, though. And scm_init_guile() works in Guile 2.0.0.
(On this platform, there is a la
On 4 May 2011, at 22:44, Brett Hoerner wrote:
> For what it's worth, 2.0.1 seems to compile fine using XCode 4's GCC chain.
It comes and goes with the version.
> I opened a bug with Apple but have since closed it.
So you should not have closed...
>
> On Wed, Apr 27,
On 27 Apr 2011, at 02:58, Brett Hoerner wrote:
> Thanks for your quick reply. For future Google searches, the bug is
> only in the GCC included with XCode 4. Downgrading to XCode 3 did the
> trick for now. I'm going to report the bug to Apple shortly.
Xcode 4 doesn't use a GCC derivation, but is
On 25 Mar 2011, at 18:25, Mark Harig wrote:
> Andy Wingo reported that he had fixed the deprecated code in this
> message (after Guile 2.0 was released):
>
> http://lists.gnu.org/archive/html/bug-guile/2011-02/msg00114.html
OK.
> Also, there has been some discussion of using "guile-config"
> ve
The example in the Guile 2.0.0 manual, "Writing Guile Extensions", sec. 2.4,
uses deprecated code, and does not indicate correct compiling options.
Below is a modified code, which I compiled (Mac OS X 10.6.6) using
gcc `guile-config compile` `guile-config link` -dynamiclib -o
libguile-bessel.so
On 10 Feb 2011, at 23:16, Ludovic Courtès wrote:
vm.c:907: internal compiler error: Segmentation fault
Please submit a full bug report,
with preprocessed source if appropriate.
See http://developer.apple.com/bugreporter> for instructions.
>>>
>>> Please bring this up with your
On 6 Mar 2011, at 11:02, Andy Wingo wrote:
>> I stopped in the function, and it seems to be correct. I checked to the
>> map, and the value was right, it wasn't NULL. I tried to stop in strncmp
>> and see what that parameters were. Wasn't very successful the first
>> tried. I haven't used gdb for
might try not overwriting the system installation.
> steve
> On Mar 6, 2011, at 7:08 AM, Hans Aberg wrote:
>
>> On 6 Mar 2011, at 11:02, Andy Wingo wrote:
>>
>>> The solution is to use GNU readline, not the editline-based thing that
>>> Apple ships.
>>
On 6 Mar 2011, at 11:02, Andy Wingo wrote:
> The solution is to use GNU readline, not the editline-based thing that
> Apple ships.
This is a notorious problem - perhaps configure should check the different
types. From what I could see, editline is a BSD fork of readline that no longer
is compat
On 5 Mar 2011, at 22:25, Andy Wingo wrote:
> On Sat 05 Mar 2011 18:27, Steven Wu writes:
>
>> #0 0x7fff83bec7f0 in strncmp ()
>> #1 0x0001019e9684 in init_bouncing_parens [inlined] () at
>> /Users/wus/local/src/gnu/guile-2.0.0/guile-readline/readline.c:445
...
> Are you certain you ar
On 5 Mar 2011, at 21:14, Steven Wu wrote:
> My is also MacOS X 10.6.6, the kernel version is 10.6.0 which is what uname
> will gives. It seems like readline issue. and I am debugging it now.
Some seem to have problems with that, but readline-6.1 works for me. I just did
./configure && make.
Ha
On 5 Mar 2011, at 18:27, Steven Wu wrote:
> I built guile-2.0.0 from the tarball, and when I started it, it crashed.
>
> The config option:
> $./config.status --config '--enable-error-on-warning' '--disable-deprecated'
> '--prefix=/usr'
Note that on BSD systems (as Mac OS X), /usr/ without /usr/
On 4 Mar 2011, at 04:00, Bob Friesenhahn wrote:
>> So guile-2.0.0 using libltdl.7.dylib of libtool-2.4, can on Mac OS X 10.6.6
>> only open a dynamic library if the name of what it actually opens ends in
>> .so (say by making a soft link using 'ln -s'); if it ends in .dylib, it
>> cannot open i
On 4 Mar 2011, at 03:59, Peter O'Gorman wrote:
>>> Mac OS X does not care about file name extensions; .dylib is just a
>>> convention for native dynamic libraries.
>
> The static linker when it sees a -l flag will look for files beginning with
> "lib" and ending in ".dylib", ".so" (though this
[I'm not on the bug-libtool list, so please cc me.]
Despite being reported a year ago, Guile can still not open dynamic libraries
ending with .dylib on Mac OS X. Looking throw the past discussion, it looks as
though developers of the one package hold the opinion that those of the other
package
On 3 Mar 2011, at 10:25, Andy Wingo wrote:
> On Wed 02 Mar 2011 23:15, Hans Aberg writes:
>
>> scheme@(guile-user)> (dynamic-link "libm")
>> ERROR: In procedure dynamic-link:
>> ERROR: In procedure dynamic-link: file: "libm", message: &qu
On 2 Mar 2011, at 22:22, Andy Wingo wrote:
> What if you leave off the suffix?
>
>scheme@(guile-user)> (use-modules (system foreign))
>scheme@(guile-user)> (dynamic-link "libm")
>$1 = #
That does not work for me.
scheme@(guile-user)> (dynamic-link "libm")
ERROR: In procedure dyna
On 2 Mar 2011, at 21:07, Michael Ellis wrote:
> Trying to follow the examples in section 6.20.6 in the manual I get
> the following.
>
> scheme@(guile-user)> (define libm (dynamic-link "/usr/lib/libm.dylib"))
> ERROR: In procedure dynamic-link: file: "/usr/lib/libm.dylib",
> message: "file not
On 21 Feb 2011, at 20:27, Michael Ellis wrote:
(use-modules (ice-9 readline))
(activate-readline)
>>>
>>> This works just fine.
>>
>> Thanks, that helps narrow the search. Sounds like it could be either
>> a 32 vs 64 problem or perhaps loading an old version of readline or
>> one of i
On 21 Feb 2011, at 19:17, Michael Ellis wrote:
>>> Commenting out readline in my .guile avoids the segfault.
>>
>> I do not have a ~/.guile file.
>
> I'm assuming readline works for you in guile. How do you activate it?
I just assumed it would be activated automatically. I am not using Guile
On 21 Feb 2011, at 18:48, Michael Ellis wrote:
> Commenting out readline in my .guile avoids the segfault.
I do not have a ~/.guile file.
On 21 Feb 2011, at 18:03, Michael Ellis wrote:
>> I am using Xcode 3.2.5,
>> gcc --version
>> i686-apple-darwin10-gcc-4.2.1 (GCC) 4.2.1 (Apple Inc. build 5664)
>> And there was no problem compiling guile-2.0.0.
...
> Updating to XCode 3.2.5 and starting over by re-extracting guile-2.0.0
> went
On 21 Feb 2011, at 15:21, Michael Ellis wrote:
> There's no other error message but I notice it looks very much like
> the problem you reported in the recent "Compiling from GIT" thread (
> http://www.mail-archive.com/bug-guile@gnu.org/msg05621.html ), except
> that I'm not seeing the seg fault m
On 20 Feb 2011, at 23:17, Michael Ellis wrote:
> ... I'm suspecting this has something to
> do with MacPorts because I found some reports of the same error text
> (in a different context) and some discussion to the effect that if
> you're using MacPorts you shouldn't have anything in /usr/local/.
On 17 Feb 2011, at 13:02, Fu-Gangqiang wrote:
> I learn guile from manual,and I can not work with libguile and find some
> manual bugs.
> In manual section 2.3(Linking Guile into Programs)
>
> I follow the example,run it and have something wrong:
> >cut here<
> $ gcc -o simple-guile sim
On 16 Feb 2011, at 11:29, Ludovic Courtès wrote:
> We are pleased to announce GNU Guile release 2.0.0, ...
> Here are the compressed sources:
> ftp://ftp.gnu.org/gnu/guile/guile-2.0.0.tar.gz (5.4MB)
It compiles on Mac OS X 10.6.6 with the system supplied compiler
$ gcc --version
i686-appl
On 12 Feb 2011, at 13:02, Andy Wingo wrote:
>> When compiling guile from GIT or guile-1.9.1, libguile/Makefile just
>> writes
>> CC libguile_2.0_la-vm.lo
>> What commands are processed? - For the compiler internal segmentation
>> fault bugreport, I need to modify the gcc arguments (also getti
When compiling guile from GIT or guile-1.9.1, libguile/Makefile just writes
CC libguile_2.0_la-vm.lo
What commands are processed? - For the compiler internal segmentation fault
bugreport, I need to modify the gcc arguments (also getting the preprocessed
vm.c).
On 10 Feb 2011, at 23:16, Ludovic Courtès wrote:
vm.c:907: internal compiler error: Segmentation fault
Please submit a full bug report,
with preprocessed source if appropriate.
See http://developer.apple.com/bugreporter> for instructions.
>>>
>>> Please bring this up with your
On 9 Feb 2011, at 21:01, Andy Wingo wrote:
> On Wed 09 Feb 2011 11:40, Hans Aberg writes:
>
>> I made a new system installation, and now the GIT version does not
>> generate 'configure'. I thought one should just run ./autogen.sh;
>> however, this fails, becau
On 10 Feb 2011, at 17:50, Andy Wingo wrote:
>> vm.c:907: internal compiler error: Segmentation fault
>> Please submit a full bug report,
>> with preprocessed source if appropriate.
>> See http://developer.apple.com/bugreporter> for instructions.
>
> Please bring this up with your OS vendor; it is
> I made a new system installation, and now the GIT version does not generate
> 'configure'. I thought one should just run ./autogen.sh; however, this fails,
> because autoconf (called via autoreconf in this script) cannot find
> gettext.m4, which is in /usr/local/share/aclocal/, which should be
On 10 Feb 2011, at 09:40, Andy Wingo wrote:
>>> However, it uses /usr/share/aclocal/, not /usr/local/share/aclocal/. I
>> can see that by changing the name of the former - it still does not
>> work. But if I in addition set a symbolic link to the latter, then it
>> works.
>>
>> That is, I get the
> However, it uses /usr/share/aclocal/, not /usr/local/share/aclocal/. I can
> see that by changing the name of the former - it still does not work. But if
> I in addition set a symbolic link to the latter, then it works.
That is, I get the compiler internal segmentation fault mentioned before.
On 9 Feb 2011, at 21:01, Andy Wingo wrote:
>> I made a new system installation, and now the GIT version does not
>> generate 'configure'. I thought one should just run ./autogen.sh;
>> however, this fails, because autoconf (called via autoreconf in this
>> script) cannot find gettext.m4, which is
I made a new system installation, and now the GIT version does not generate
'configure'. I thought one should just run ./autogen.sh; however, this fails,
because autoconf (called via autoreconf in this script) cannot find gettext.m4,
which is in /usr/local/share/aclocal/, which should be copied
On 29 Jan 2011, at 22:47, Ludovic Courtès wrote:
Undefined symbols:
"_GC_register_finalizer_no_order", referenced from:
_make_c_exception in exception.o
_make_exception in exception.o
_make_tuple in tuple.o
ld: symbol(s) not found
Oooh, I finally got your point about SCM_NEWSMO
On 29 Jan 2011, at 23:32, Ludovic Courtès wrote:
The bug is this: first
make
make pdf
This produces the PDF. Then
make clean
This takes away the pdf. Then try to repeat
make pdf
This fails.
I think commit 41d82ac9904c883a0c281cd1a89c03d9d968a801 fixes this.
Fine. I have noticed in packag
On 27 Jan 2011, at 10:03, Andy Wingo wrote:
On Mac OS X, there are two locations for cached objects; when put
there,
the system will assume they can be regenerated and not be backed
up. These would be
~/Library/Caches/Guile/
/Library/Caches/Guile/
if keeping to Mac tradition using uppercase
On 27 Jan 2011, at 10:00, Andy Wingo wrote:
If you wish to preserve a potentially
multiply-valued return, you will need to set up a multiple-value
continuation, using `call-with-values'.
But this is false.
According to the standard, passing an unintended number of values to a
continuat
On 26 Jan 2011, at 23:57, Andy Wingo wrote:
Then I made 'make clean' only to discover that the docs I was reading
did not exits anymore. And then they could not be remade.
Apologies for all the mess! But I am unclear: do you have 1.8 and 1.9
docs now?
I have only 1.9 now, as I made the tran
On 26 Jan 2011, at 22:10, Andy Wingo wrote:
When starting with 'guile -l', autocompiling fails, even with an
empty file.
I found the error:
On my computer, the directory ~/.cache/ had already been created by
another program, setting another owner so that guile could not create
its directories
On 26 Jan 2011, at 21:57, Andy Wingo wrote:
However, quietly loosing values is inviting bugs.
True. Common Lisp does it though, FWIW. I find it convenient.
From what I can see, one can implement a very nice infix notation
syntax on top of Guile, which function calls f(x_1, ..., x_k). The
On 26 Jan 2011, at 21:55, Andy Wingo wrote:
The file gc.h says that it is only for Java implementations.
Assuming you refer to gc_register_finalizer_no_order, that is not the
case; it implements a finalizer with semantics that were needed when
Java-style finalizers were added to libgc. It hap
On 26 Jan 2011, at 21:52, Andy Wingo wrote:
$ make
gcc parser.o lexer.o driver.o guile++.o guile.o exception.o tuple.o
guile-config link` -lstdc++ -o guile++
This line was mangled by your mailer, I think (missing backquote,
newline inserted).
By your mailer, I would think: when I send it to
On 26 Jan 2011, at 21:46, Andy Wingo wrote:
The code below causes Guile 1.9.14.68-a7d8a to crash (segmentation
fault
after awhile), on Mac OS X 10.5.8 PPC G4.
(defmacro call (f g)
`(apply ,g (,f)))
(call (lambda () (values 4 5))
(lambda (a b) b))
Good catch! It was an error in the er
On 26 Jan 2011, at 21:51, Andy Wingo wrote:
It seems it is not only 'values' writing, but the new behavior
seems to
be to strip trailing values quietly:
(define a (values 2 3 4))
(call-with-values (lambda () a) (lambda x x))
in Guile 1.9.14.68-a7d8a computes to
$1 = (2)
By contrast, in gui
On 26 Jan 2011, at 21:02, Andy Wingo wrote:
After first making (& installing) Guile from GIT,
make pdf
make clean
make pdf
failed. It seems 'clean' also removes a file 'standard-library.texi',
which is needed for 'make pdf'. It is in the guile-1.9.14
distribution,
so it is not a file gene
On 21 Jan 2011, at 17:02, Ludovic Courtès wrote:
Can you post the exact link command line and error message?
$ make
gcc parser.o lexer.o driver.o guile++.o guile.o exception.o tuple.o
guile-config link` -lstdc++ -o guile++
This line was mangled by your mailer, I think (missing backquote,
ne
On 20 Jan 2011, at 22:18, Ludovic Courtès wrote:
It is discussed here, along with some other ideas.
https://groups.google.com/group/comp.lang.scheme/browse_thread/thread/b72d987aa6626cd2/e2f7cfa55fb51d55?hl=en
Interesting thread.
It is possible to extend Scheme values as to infix tuples usa
On 21 Jan 2011, at 00:07, Mark Harig wrote:
When starting with 'guile -l', autocompiling fails, even with an
empty file.
$ guile -l empty.scm
;;; note: autocompilation is enabled, set GUILE_AUTO_COMPILE=0
;;; or pass the --no-autocompile argument to disable.
;;; compiling empty.scm
;;; WARNIN
On 21 Jan 2011, at 09:09, Hans Aberg wrote:
The problem is due to scm_from_latin1_symbol() in file load.c
together with that I set the locale to LC_CTYPE=en_US.UTF-8. It
works with either the default locale on Mac OS X 10.5.8, which is
LC_CTYPE=UTF-8, or LC_CTYPE=en_US.ISO8859-1. However
On 21 Jan 2011, at 00:07, Mark Harig wrote:
When starting with 'guile -l', autocompiling fails, even with an
empty file.
$ guile -l empty.scm
;;; note: autocompilation is enabled, set GUILE_AUTO_COMPILE=0
;;; or pass the --no-autocompile argument to disable.
;;; compiling empty.scm
;;; WARNIN
On 20 Jan 2011, at 22:18, Ludovic Courtès wrote:
There seems to be a bug in GIT version when writing the 'values'
data
type.
(list 2 (values 3 4) 5)
$1 = (2 3 5)
This behavior is correct: in Guile 1.9, multiple-value returns are
truncated any time the continuation expects fewer values.
Here
On 20 Jan 2011, at 22:01, Ludovic Courtès wrote:
Can you post the exact link command line and error message?
$ make
gcc parser.o lexer.o driver.o guile++.o guile.o exception.o tuple.o
`guile-config link` -lstdc++ -o guile++
Undefined symbols:
"_GC_register_finalizer_no_order", referenced
On 20 Jan 2011, at 16:17, Ludovic Courtès wrote:
It seems it is not only 'values' writing, but the new behavior seems
to be to strip trailing values quietly:
(define a (values 2 3 4))
(call-with-values (lambda () a) (lambda x x))
in Guile 1.9.14.68-a7d8a computes to
$1 = (2)
By contrast, in gui
On 20 Jan 2011, at 16:20, Ludovic Courtès wrote:
In 'guile-config link', the flag '-lgc' is missing; it is needed when
linking smobs. The function SCM_NEWSMOB calls
GC_register_finalizer_no_order() in header gc.h
It shouldn’t be needed when libguile is a shared library, at least not
on ELF pla
1 - 100 of 130 matches
Mail list logo
