LAST_UPDATED: Tue Mar 5 09:48:14 UTC 2019 (revision 269387)
Native configuration is arm-unknown-linux-gnueabi
=== libatomic tests ===
Running target unix
=== libatomic Summary ===
# of expected passes44
# of unsupported tests 5
LAST_UPDATED: Tue Mar 5 09:48:14 UTC 2019 (revision 269387)
=== acats tests ===
=== acats Summary ===
# of expected passes2320
# of unexpected failures0
Native configuration is i686-pc-linux-gnu
=== brig tests ===
Running tar
LAST_UPDATED: Tue Mar 5 09:48:14 UTC 2019 (revision 269387)
=== acats tests ===
=== acats Summary ===
# of expected passes2320
# of unexpected failures0
Native configuration is s390x-ibm-linux-gnu
=== g++ tests ===
Running ta
The issue does not appear related to raspicam itself, but to the loader
accessing the ELF file generated by GCC. I am not the only one
experiencing this issue. If you can explain what causes the error or
where to look for the actual source of the error, I will be happy to
provide more information
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:
cloog | 0.18.4-2 | source
cloog-isl | 0.18.4-2 | amd64, arm64, armel, armhf, hurd-i386, i386,
kfreebsd-amd64, kfreebsd-i386, mips, mips64el, mipsel, ppc64el, s390x
libcloog-isl-d
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:
isl-0.18 | 0.18-4 | source
libisl-0.18-dev | 0.18-4 | amd64, arm64, armel, armhf, hurd-i386, i386,
kfreebsd-amd64, kfreebsd-i386, mips, mips64el, mipsel, ppc64el, s390x
libisl1
6 matches
Mail list logo
