Hi!
SBCL currently FTBFS[0][1] on armhf. THis is due to some changes in the
environment (I can build the current version in the environment from the
time of the last successfull armhf build and *cannot* build the "old"
sbcl in today's unstable). I'm willing to cooperate in debugging this
problem
Hi!
The current hg snapshot I've uploaded to experimental yesterday does
not seem to build as-is on arm* still.
Christoph
Hi folks!
I've prepared a new version of libgc in experimental which I intent to
upload to unstable soon. Unfortunately it FTBFS on (one of) your
architectures (arm64, ppc64el hangs ; mipsel fails a test). It would be
great if you can point me to a upstream commit (or a patch) to backport
so
Hi!
YunQiang Su wzss...@gmail.com writes:
I just test in on another machine manually.
it has not the gctest fail. :0:
Thanks for the prompt reply! Was that on a porterbox or some personal
machine?
On mips/mips64el, it has the same symbol files problem.
Exactly the same? would you mind
YunQiang Su wzss...@gmail.com writes:
Oh, no. mips64el misses more symbols. :(
Not an issue and thanks for the logs!
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=774885
should also have been fixed.
In theory it should build against the system's libatomic-ops (at least
now). I'll try to
Hi!
Wookey woo...@wookware.org writes:
Package: ffcall
Version: 1.10+cvs20100619-3
Severity: normal
User: debian-arm@lists.debian.org
Usertag: arm64
This package fails to build on arm64. The build log for the offical archive
is here:
Hi,
I am an active porter for the following architectures and I intend
to continue this for the lifetime of the jessie release:
For kfreebsd-*, I
- test packages on this architecture
This includes running a Desktop (Notebook) System on testing and am
therefore testing the relevant stack
7 matches
Mail list logo
