Am 14.06.2015 um 17:03 schrieb Peter Bex:
Also there's something strange going on - I observe object references
being mixed up. (Though this could be an unrelated bug, it never
happened in the past couple of years.)
Can you make a program that can reproduce these problems?
Fixed.
This
On Tue, Jun 09, 2015 at 09:59:27PM +0200, Peter Bex wrote:
Operating system: Debian 8.1
Hardware platform: Powerpc (32 bits, iBook G4)
C Compiler: Clang 3.5.0-10
Installation works?: yes
Tests work?: no
Installation of eggs works?: no
The clang build segfaults on the very first test, and
On Sun, Jun 14, 2015 at 04:48:58PM +0200, Jörg F. Wittenberger wrote:
That's interesting. I just succeeded to build chicken (both the 4.9.1
and my local deviations) with gcc 4.9.2 and clang 3.5.0 on both amd64
and armhf.
Clang works fine on i386 and amd64 for me, as well. It's just on
Peter Bex scripsit:
I tried digging in, but I hit a wall as soon as I tried gdb on a
basic csi session: it fails right at the start, in C_toplevel:
it looks like the toplevel_trampoline argument it passes to
C_reclaim (a function pointer) already gets mangled. This might
be a problem with
Interesting. I can't fint that tag:
$ git fetch origin 4.10.0rc1
remote: Counting objects: 3, done.
remote: Compressing objects: 100% (3/3), done.
remote: Total 3 (delta 2), reused 0 (delta 0)
Unpacking objects: 100% (3/3), done.
From git://code.call-cc.org/chicken-core
* tag
* Kristian Lein-Mathisen kristianl...@gmail.com [150609 11:25]:
Interesting. I can't fint that tag:
How did you update? Git will only fetch tags from the server if you tell
it to do so, for example git fetch --tags.
The tag interestingly resides on a commit without a branch though, it
sits on
Interesting! I didn't know about git fetch --tags, that worked. But yes,
it's not on a branch. We'll use this for our tests. Thanks everyone!
K.
On Tue, Jun 9, 2015 at 11:31 AM, Christian Kellermann ck...@pestilenz.org
wrote:
* Kristian Lein-Mathisen kristianl...@gmail.com [150609 11:25]:
Hi all,
thanks for suppying the new release candidate.
I installed it, albeit the check target seemed to freeze at
testing apply: I waited about 5 minutes on a lame machine, before I
stopped it.
Except numbers (Peter knows the reason), all the eggs I tested went
through without troubles.
Here
Great work Moritz and the team! Looking forward to test this on our
systems.
We are building from the git repo, is there a tag/branch for 4.10.0?
prerelease perhaps?
K.
On Sun, Jun 7, 2015 at 5:16 PM, Moritz Heidkamp mor...@twoticketsplease.de
wrote:
Hello everyone,
we are happy to announce
On Tue, Jun 09, 2015 at 09:24:34AM +0200, Kristian Lein-Mathisen wrote:
Great work Moritz and the team! Looking forward to test this on our
systems.
Excellent! I'd love to hear your feedback.
We are building from the git repo, is there a tag/branch for 4.10.0?
prerelease perhaps?
Yes,
On Sun, Jun 07, 2015 at 05:16:07PM +0200, Moritz Heidkamp wrote:
If you can, please let us know the following information about the
environment you tested the RC tarball on:
Operating system: FreeBSD 10.0
Hardware platform: x86-64
C Compiler: clang-3.3
Installation works?: yes
Tests work?: yes
Hi,
On 9 June 2015 12:56 CEST, Kristian Lein-Mathisen wrote:
Interesting! I didn't know about git fetch --tags, that worked. But yes,
it's not on a branch. We'll use this for our tests. Thanks everyone!
turns out I only pushed the tag but not the commit it points to -- git's
UI is indeed a
On Sun, Jun 07, 2015 at 05:16:07PM +0200, Moritz Heidkamp wrote:
If you can, please let us know the following information about the
environment you tested the RC tarball on:
Operating system: Debian 8.1
Hardware platform: Powerpc (32 bits, iBook G4)
C Compiler: GCC 4.9.2
Installation works?:
Hello Moritz and the entire Chicken community,
First of all thank you very much for the release!
Moritz Heidkamp writes:
[...]
If you can, please let us know the following information about the
environment you tested the RC tarball on:
[...]
Operating system: NetBSD/amd64 7.99.18
Hardware
Hi Jürgen!
Juergen Lorenz j...@jugilo.de writes:
Compiler:
gcc-4.9.2-2
This compiler is known to cause this trouble. If you disable
optimisations for this test, i.e. set -O0 for gcc the problem should go
away.
We still have to narrow it down to a small example we can report to the
gcc
15 matches
Mail list logo
