On Sun, 13 Oct 2024 17:55:07 +1300 Michael Cree wrote:
> Regarding:
>
> > opencv currently FTBFS on alpha due to missing files during dh_install [1]
>
> I note from the build log that the viz module was not built because
> it was disabled at cmake configure time at t
Source: ruby3.3
Version: 3.3.5-2
Severity: normal
User: debian-al...@lists.debian.org
Usertags: alpha
Hello,
ruby3.3 currently FTBFS on alpha due to an incorrect expectation in
the test suite [1]:
1) Failure:
TestFiddle#test_dlopen_linker_script_group_linux
[/<>/test/fiddle/test_fiddle.rb:52]:
Hello,
Regarding:
> opencv currently FTBFS on alpha due to missing files during dh_install [1]
I note from the build log that the viz module was not built because
it was disabled at cmake configure time at the start of the build.
Checking CMakeLists.txt in the opencv source I see:
OCV_OPTION(W
I have tried the suggested script (with a small modification to count
number of failures) running for a few hours on one of the packages
that had failed on the buildd and never saw cmake fail.
But then building a few packages locally with sbuild, apbs failed
first time to build with the cmake fail
Tags: patch
Further to my prior report it is not the use of variable length array
but the overwriting the end of the array that is the problem. This bug
is repeated multiple times throughout the source file src/detector.c.
It appears that there have been attempts to fix a couple of
occurrences of
On Wed, Sep 13, 2023 at 06:52:08PM -0300, Antonio Terceiro wrote:
> ohcount segfaults (and sometimes aborts with a Bus error) on arm64,
> almost 90% of the time. I tried this on an up to date arm64 Debian
Running ohcount under gdb traps on the segfault but can't get a
backtrace due to a corrupted
On Fri, Sep 08, 2023 at 11:24:47AM +0200, Dylan Aïssi wrote:
> Le dim. 3 sept. 2023 à 10:45, Michael Cree a écrit :
> > pipewire FTBFS on Alpha due to test suite failure. From the build
> > log [1]:
>
> Upstream has pushed two commits to fix the build o
Source: pipewire
Version: 0.3.79-1
Severity: important
Reason: fails to build from source but built in the past
User: debian-al...@lists.debian.org
Usertags: ftbfs
pipewire FTBFS on Alpha due to test suite failure. From the build
log [1]:
8/22 test-resample FAIL0.19s kill
On Wed, May 17, 2023 at 11:27:43AM +0200, John Paul Adrian Glaubitz wrote:
> Hi Michael!
>
> On Tue, 2023-05-16 at 20:25 +1200, Michael Cree wrote:
> > On Tue, May 16, 2023 at 09:38:56AM +0200, John Paul Adrian Glaubitz wrote:
> > > After a long discussion on IRC and t
On Tue, May 16, 2023 at 09:38:56AM +0200, John Paul Adrian Glaubitz wrote:
> After a long discussion on IRC and the mailing list, we have agreed to raise
> the
> baseline for the alpha architecture to EV56 to improve the generated code and
> fix
> a number of issues. The change is already being i
On Sun, Feb 05, 2023 at 03:35:39PM -0800, Otto Kekäläinen wrote:
> I applied the suggested fix now in
> https://salsa.debian.org/mariadb-team/mariadb-server/-/commit/9e7ac5852d8a0ab96e25c4dd38dbc88354ee1c9e
> and it will be included in next upload. There are so many build
> failures that I don't ha
On Thu, Feb 02, 2023 at 12:58:50PM +0400, Dmitry Shachnev wrote:
> Hi Michael!
>
> On Thu, Feb 02, 2023 at 09:00:07PM +1300, Michael Cree wrote:
> > On Wed, Feb 01, 2023 at 09:13:09AM -0300, Lisandro Damián Nicanor Pérez
> > Meyer wrote:
> > > It's from Thiag
On Sat, Jan 28, 2023 at 01:55:00PM -0300, Lisandro Damian Nicanor Perez Meyer
wrote:
> On viernes, 9 de diciembre de 2022 22:19:16 -03 Michael Cree wrote:
> > Source: qt6-base
> > Version: 6.3.1+dfsg-10
> > Severity: important
> > Tags: patch ftbfs
> > Justific
Package: usrmerge
Version: 35
Severity: normal
Dear Maintainer,
On upgrading Alpha system with the package libc6.1-alphaev67 installed
when installing usrmerge the following occurred:
Setting up usrmerge (35) ...
cp: cannot create regular file '/usr/lib/alpha-linux-gnu/ev67/libc.so.6.1': No
suc
> I suspect this might be better worked around with -Wl,-no-relax on the
> linking only rather than disabling compiler optimisations. I intend to
> run a test of that today.
Nice idea, but, it didn't solve the linker errors. Stick with reducing
compiler optimisation to -O1.
Cheers
Michael.
On Fri, Jan 13, 2023 at 08:05:43PM +0100, John Paul Adrian Glaubitz wrote:
> libdeflate currently FTBFS on alpha due to linker issues:
>
> cc -o libdeflate.so.0 -specs=/usr/share/dpkg/pie-link.specs -Wl,-z,relro
> -Wl,-z,now -fprofile-generate -O2 -fomit-frame-pointer -std=c99 -I. -Wall
> -Wunde
Source: qt6-base
Version: 6.3.1+dfsg-10
Severity: important
Tags: patch ftbfs
Justification: fails to build from source (but built successfully in the past)
The build fails with:
/<>/src/corelib/plugin/qelfparser_p.cpp:178:4: error: #error
"Unknown Q_PROCESSOR_xxx macro, please update."
Full log
On Sun, Nov 13, 2022 at 02:49:11PM -0800, Otto Kekäläinen wrote:
> Source: mariadb-10.6
> Version: 1:10.6.7-1
> Tags: upstream, confirmed, ftbfs
> User: debian-al...@lists.debian.org
> Usertags: alpha
> X-Debbugs-CC: debian-al...@lists.debian.org
>
> After upload of mariadb-10.6 1:10.6.7-1 I notic
Source: glibc
Version: 2.34
Severity: important
User: debian-al...@lists.debian.org
Usertags: ftbfs
Justification: Fails to build from source but built in the past.
glibc 2.34 FTBFS on Alpha with a segfault occuring during building
locales. From the build log:
Generating locale en_US.UTF-8: this
Source: glib2.0
Version: 2.72.0-1
Severity: important
Justification: fails to build from source when built in past
User: debian-al...@lists.debian.org
Usertags: ftbfs
X-Debbugs-Cc: debian-al...@lists.debian.org
glib2.0 FTBFS on alpha in the test suite with:
GLib-GIO:ERROR:../../../gio/tests/polla
On Fri, Oct 08, 2021 at 09:00:22PM +0200, John Paul Adrian Glaubitz wrote:
> On 10/8/21 20:52, Rob Browning wrote:
> > Then, once that's uploaded were you planning to handle the reverse dep
> > rebuilds, and/or what coordination might we need there?
>
> We can just rebuild all of these reverse dep
On Fri, Oct 08, 2021 at 03:03:38AM +0200, John Paul Adrian Glaubitz wrote:
> On 10/8/21 03:00, Rob Browning wrote:
> > If we've never had a 3.0 viable for alpha, for example, then we can of
> > course do whatever we like, with the realization that if we disable
> > threads there now, we may be stuc
On Sun, Oct 03, 2021 at 09:14:04PM +0200, John Paul Adrian Glaubitz wrote:
> On 10/3/21 20:29, Michael Cree wrote:
> > On Sun, Oct 03, 2021 at 11:33:31AM +0200, John Paul Adrian Glaubitz wrote:
> >> Both guile-2.2 and guile-3.0 FTBFS on alpha when built with thread
> >>
On Sun, Oct 03, 2021 at 11:33:31AM +0200, John Paul Adrian Glaubitz wrote:
> Both guile-2.2 and guile-3.0 FTBFS on alpha when built with thread
> support. Passing --without-threads to configure disables thread
> support and fixes the build.
The issue only appears on SMP systems. They build correc
On Mon, Aug 17, 2020 at 12:39:27PM +0200, Jonas Smedegaard wrote:
> Hi Michael,
>
> Quoting Michael Cree (2020-08-17 11:30:52)
> > Ffmpeg does not build on alpha as it currently depends on
> > libpocketsphinx-dev but pocketsphinx does not build on alpha
> > due
Package: ffmpeg
Version: 7:4.3.1-2
Severity: normal
Dear Maintainer,
Ffmpeg does not build on alpha as it currently depends on
libpocketsphinx-dev but pocketsphinx does not build on alpha
due to long standing test suite failures. I see the build
dependency has been removed on many other arches i
On Tue, May 12, 2020 at 01:04:06AM +0200, John Paul Adrian Glaubitz wrote:
> On 5/12/20 1:01 AM, John Paul Adrian Glaubitz wrote:
> > On 5/11/20 11:56 PM, Xavier wrote:
> >> Could someone help us here ? I forwarded this bug to upstream ([1]) but
> >> didn't receive any response for now.
> >>
> >> (
Hello,
This bug is the reason for the FTBFS of libspiro on Alpha and
presumably on HPPA also.
It is fixed upstream in commit:
35233450c922787dad42321e359e5229ff470a1e
I have verified that building on Alpha with that commit as a
patch in Debian source results in a successful build.
Cheers,
Micha
Source: e-antic
Version: 0.1.3+ds-2
Severity: wishlist
Tags: patch
User: debian-al...@lists.debian.org
Usertags: ftbfs
e-antic FTBFS on alpha during the configure stage with [1]:
checking flint/flint.h usability... no
checking flint/flint.h presence... no
checking for flint/flint.h... no
configur
On Mon, Sep 09, 2019 at 10:49:48PM +0200, John Paul Adrian Glaubitz wrote:
> Shortly after typing "root" and pressing enter, the following message is
> printed to the
> console which seems to be an alpha-specific syscall:
>
> [ 195.414939] do_entUnaUser: 7 callbacks suppressed
No, that is not a
On Mon, Sep 09, 2019 at 11:14:50PM +0200, John Paul Adrian Glaubitz wrote:
> On 9/9/19 10:49 PM, John Paul Adrian Glaubitz wrote:
> > Both on my Alpha XP-1000 as well as inside a qemu-user chroot, upgrading
> > glibc
> > to version 2.29-1 resulted in setuid/getuid breaking in a weird way:
>
> To
Note that disabling altivec does not fix the baseline issue for
ppc64, namely that x265 is compiling with -mcpu=power8 on ppc64.
The baseline is power5.
Cheers,
Michael.
On Tue, Jan 22, 2019 at 10:48:16AM +0100, Matthias Klose wrote:
> openjdk-11 ftbfs on alpha, linking libjvm.
The relocation errors can be worked around by linking with
-Wl,--no-relax, i.e., adding the following in debian/rules:
ifeq ($(DEB_HOST_ARCH),alpha)
export EXTRA_LDFLAGS_ZERO += -Wl,--no
Source: pulseaudio
Version: 12.2-2
Severity: important
Justification: fails to build from source but built in the past.
User: debian-al...@lists.debian.org
Usertags: alpha
Tags: patch
Pulseaudio FTBFS on alpha due to the volume-test test failing due to
a floating-point exception which in turn is d
Source: babl
Version: 0.1.50-1
Severity: important
Justification: failed to build from source (but built in the past)
Tags: patch
User: debian-al...@lists.debian.org
Usertags: ftbfs
babl FTBFS on Alpha [1] with what on the surface looks like a linker error
but is actually misuse of the -Ofast comp
Source: sip-tester
Version: 1:3.5.1-2
Severity: important
Justification: Fails to build from source (but built in the past)
User: debian-al...@lists.debian.org
Usertags: ftbfs
Tags: patch
sip-tester FTBFS on Alpha due to the sipp_socklen_t being set to int
instead of socklen_t in the include/socke
Source: plplot
Version: 5.13.0+dfsg-7
Severity: important
Justification: fails to build from source (but built in past)
User: debian-al...@lists.debian.org
Usertags: ftbfs
Tags: patch
plplot FTBFS on Alpha [1] with missing libcsirocsa.so files at the
install stage. One can trace this back to the
On Wed, Jun 06, 2018 at 09:43:20PM +1000, Alexander Zangerl wrote:
> On Wed, 06 Jun 2018 22:51:08 +1200, Michael Cree writes:
> >dump FTBFS on alpha with [1]:
> ...
> >Alpha Linux does not have the getpid syscall; it follows OSF1.0
>
> oh the joy of non-posix environment
Source: dump
Version: 0.4b46-4
Severity: important
Justification: Fails to build from source but built in past
User: debian-al...@lists.debian.org
Usertags: ftbfs
Tags: patch
dump FTBFS on alpha with [1]:
gcc -DHAVE_CONFIG_H -I. -I.. -I../dump -I../compat/include -I../common
-Wdate-time -D_FORTI
On Tue, May 01, 2018 at 10:21:11AM -0300, Lisandro Damián Nicanor Pérez Meyer
wrote:
> > qtbase-opensource-src FTBFS on Alpha [1] due to an ambiguous
>
> Thanks for the very clear explanation! There are two possible ways out here:
>
> 1) Preferred by us Qt maintainers: file a bug in bugreports.q
Source: libserialport
Version: 0.1.1-2
Severity: wishlist
User: debian-al...@lists.debian.org
Usertags: ftbfs
Tags: patch
libserialport FTBFS on Alpha [1] with:
linux_termios.c: In function 'set_termios_speed':
linux_termios.c:90:19: error: 'BOTHER' undeclared (first use in this
function)
term-
Source: qtbase-opensource-src
Version: 5.10.1+dfsg-5
Severity: important
Justification: fails to build from source (but built in past)
User: debian-al...@lists.debian.org
Usertags: ftbfs
Tags: patch
qtbase-opensource-src FTBFS on Alpha [1] due to an ambiguous
resolution of the overloaded call to a
How about the attached patch? Should detection of number of cores
fail it sets the number of cores to be one. With this patch
r-cran-nmf builds successfully on Alpha.
Cheers
Michael.
Index: r-cran-nmf-0.21.0/R/options.R
===
--- r-cr
On Fri, Mar 02, 2018 at 11:32:44PM -0500, James McCoy wrote:
> Thanks (again) for the very thorough analysis. Sorry it's taken so long
> for me to circle back to this.
>
> If I understand correctly, the easiest fix would be to memcpy()
> tc->source to an appropriately sized apr_uint16_t/apr_int32
Package: faketime
Version: 0.9.7-1
Severity: important
Tags: patch
The faketime package fails to work correctly on the Alpha
architecture. This failure of faketime to work correctly is the
reason for the mbedtls FTBFS, which uses faketime in its test
suite [1].
Consider the following test program
Source: vim
Version: 2:8.0.1401-2
Severity: important
Justification: fails to build from source (but built in the past)
User: debian-al...@lists.debian.org
Usertags: ftbfs
vim FTBFS on Alpha with the following [1]:
make[2]: Entering directory '/<>/src/vim-gtk/po'
../vim -u NONE -e -X -S check.vim
I extend the patch from Dave Anglin to also fix the FTBFS of
python-demgengeo on Alpha. Attached.
Cheers
Michael
--- a/m4/boost.m4
+++ b/m4/boost.m4
@@ -484,17 +484,17 @@
possible_paths="${with_boost}/lib ${with_boost}"
else
possible_paths="${boost_cv_inc_path%/include}/lib \
-
Source: kpmcore
Version: 3.2.1-2
Severity: important
Justification: was built in the past
User: debian-al...@lists.debian.org
Usertags: alpha
The latest build of kpmcore [1] did not package libkpmcore6 on Alpha,
and contained a comment in the changelog that "kde dependencies has
never been availab
Source: notmuch
Version: 0.25.2-1
Severity: important
Justification: fails to build from source (but built in the past)
User: debian-al...@lists.debian.org
Usertags: ftbfs
notmuch FTBFS on Alpha [1] in the test suite due to a broken gdb.
Please build notmuch on Alpha without the gdb build-depends
I've been investigating this FTBFS of emacs25 on Alpha. Interestingly
my manual build on one of the buildds built to completion. Running the
test manually I cannot get it to fail. I am using invocations such as:
./debian/build-nox/src/emacs-25.2.2 -batch -L
./debian/build-src/test/automated/ -
Source: qtwebkit-opensource-src
Version: 5.212.0~alpha2-5
Severity: important
Tags: patch
User: debian-al...@lists.debian.org
Usertags: ftbfs
qtwebkit-opensource-src FTBFS on Alpha [1] due missing logic in the
cmake architecture detection logic. I attach a patch that provides
the missing bits. W
Source: mozjs52
Version: 52.3.1-7
Severity: wishlist
Tags: patch
User: debian-al...@lists.debian.org
Usertags: ftbfs
mozjs52 FTBFS on alpha because there is a conflict in determining the
arch bitsize [1], and later on in the build an attempt to load libc.so.6
which does not exist in Alpha Linux.
Source: r-cran-nmf
Version: 0.20.6-1
Severity: wishlist
r-cran-nmf FTBFS on alpha, sparc64 and the non-linux arches, because
it calls R base function parallel::detectCores() and expects the
result to be an integer, however the detectCores() documentation
states that the result is an integer only i
Source: openjdk-9
Version: 9~b181-4
Severity: important
Justification: causes random FTBFS in java packages when built on SMP system
Tags: patch
User: debian-al...@lists.debian.org
Usertags: alpha
X-Debbugs-CC: John Paul Adrian Glaubitz
Java, javac and jar can all randomly lockup (and never compl
On Mon, Mar 13, 2017 at 09:04:15PM +0100, Bálint Réczey wrote:
> > kodi FTBFS on alpha due to Intel specific code [1].
> >
> > I attach a patch that enables generic code to be built rather
> > than Intel specific code and with that kodi builds to completion
> > on Alpha.
>
> Can kodi run on any al
Source: kodi
Version: 2:17.0+dfsg1-3
Severity: wishlist
Tags: patch
User: debian-al...@lists.debian.org
Usertags: alpha
kodi FTBFS on alpha due to Intel specific code [1].
I attach a patch that enables generic code to be built rather
than Intel specific code and with that kodi builds to completio
Source: lua-sandbox
Version: 1.2.1-4
Severity: wishlist
User: debian-al...@lists.debian.org
Usertags: alpha
lua-sandbox FTBFS on alpha due to a test-suite failure [1]
The following tests FAILED:
11 - test_heka_sandbox (Failed)
Running that test manually reveals the failure occurs random
I see that this bug is fallout from trying to fix #817884, which was
also reported as #817988 where it was noted that "Dynamic linking uses
the _abiname_, which is libm.so.6 in this case, but is may be
libm.so.6.1 or libm.so.0.3 in other cases." I note that the patch
applied to mpi4py in #817884 i
Source: mpi4py
Version: 2.0.0-2
Severity: important
Justification: fails to build from source (but built in the past)
User: debian-al...@lists.debian.org
Usertags: ftbfs
mpi4py FTBFS on Alpha with the following failure in the test suite [1]:
FAIL: testDL1 (test_dl.TestDL)
Source: marisa
Version: 0.2.4-8
Severity: wishlist
Tags: patch
User: debian-al...@lists.debian.org
Usertags: ftbfs
marisa FTBFS on Alpha due a test suite failure:
make[4]: Entering directory '/«PKGBUILDDIR»/tests'
FAIL: base-test
This test suite failure occurs because Alpha is not detected as a
Source: qtscript-opensource-src
Version: 5.6.1+dfsg-2
Severity: important
Justification: fails to build from source but built in past
Tags: patch
User: debian-al...@lists.debian.org
Usertags: alpha
qtscript-opensource-src FTBFS on Alpha due to a test suite failure [1]:
FAIL! : tst_QScriptJsTestS
Source: gfarm
Version: 2.6.11+dfsg-1
Severity: important
Justification: fails to build from source but built in the past
Tags: patch
User: debian-al...@lists.debian.org
Usertags: alpha
gfarm FTBFS on alpha with [1]:
cc -D_REENTRANT -pthread -g -O2 -fPIE -Wformat -Werror=format-security -Wall
-D_
On Mon, May 02, 2016 at 12:01:18AM -0400, James McCoy wrote:
> Thanks for the analysis and working on a patch. I'll note that
> _Alignas, if it had worked, would likely have been too new a compiler
> feature to use.
>
> It looks like Debian's ia64 porterbox is still running, so I can try
> reprod
Control: tags -1 - patch
Hi,
Sorry, patch I attached for subversion FTBFS is incorrect. (Thought I
had test built it but got mixed up with some other packages with
similar problem that I had successfully run test builds on.) The
Alignas does not work at that position in the code, however I am
c
Source: subversion
Version: 1.9.4-1
Severity: important
Justification: fails to build from source (but built in the past)
Tags: patch
User: debian-al...@lists.debian.org
Usertags: alpha
subversion FTBFS on Alpha due to a test suite failure [1]:
START: utf-test
PASS: lt-utf-test 1: test is_valid/
Source: mpd
Version: 0.19.14-2
Severity: important
Justification: fails to build form source (but built in the past)
Tags: patch
User: debian-al...@lists.debian.org
Usertags: alpha
mpd FTBFS on Alpha with a failure in the test suite [1]:
FAIL: test/test_byte_reverse
Source: vxl
Version: 1.17.0.dfsg2-4
Severity: important
Justification: fails to build from source (but built in past)
User: debian-al...@lists.debian.org
Usertags: alpha
vxl FTBFS on Alpha with [1]:
cd /«PKGBUILDDIR»/obj-alpha-linux-gnu/vcl/tests && /usr/bin/c++
-DVXL_LEGACY_ERROR_REPORTING -D
On Fri, Feb 19, 2016 at 10:06:35AM +0200, Alberto Garcia wrote:
> On Fri, Feb 19, 2016 at 07:36:38PM +1300, Michael Cree wrote:
>
> > webkit2gtk FTBFS on alpha due to the configure code not fully
> > configuring the build for the arch. I attach a patch which fixes
> >
Source: webkit2gtk
Version: 2.10.6-1
Severity: wishlist
Tags: patch
User: debian-al...@lists.debian.org
Usertags: ftbfs
webkit2gtk FTBFS on alpha due to the configure code not fully
configuring the build for the arch. I attach a patch which fixes
the issue.
Regards
Michael.
Index: webkit2gtk-2.1
Source: ecasound
Version: 2.9.1-7
Severity: important
Justification: fails to build from source but built in the past
User: debian-al...@lists.debian.org
Usertags: ftbfs
Ecasound FTBFS on Alpha due to a test-suite failure [1]:
make check-TESTS
make[5]: Entering directory '/«PKGBUILDDIR»/libecaso
Source: freerdp
Version: 1.1.0~git20140921.1.440916e+dfsg1-5
Severity: important
Justification: fails to build from source (but built in past)
User: debian-al...@lists.debian.org
Usertags: alpha
Freerdp FTBFS on Alpha with a failure in the test suite [1]:
Start 65: TestUnicodeConversion
65/
Pulseaudio fails to build on the Alpha architecture due to a failure
in the volume-test of the test suite. I had reported this to the
Debian bug tracker [1] but the maintainer has asked that I forward the
patch to this mail list. The failure in volume-test occurs because it
is compiled with -ffas
Control: tags -1 + patch
Here goes a patch to fix the FTBFS on Alpha. It protects the
floating point addition of volumes in dB from adding any infinities.
An assumption is made that negative infinity is the only possible
non-finite number since dB are calculated via a logarithm from
volumes and v
Source: pulseaudio
Version: 6.0-5
Severity: important
Justification: fails to build from source but built in the past.
User: debian-al...@lists.debian.org
Usertags: alpha
Pulseaudio FTBFS on alpha due to the volume-test test failing. From
the build log [1]:
FAIL: volume-test
=
R
Control: reassign -1 binutils 2.25.1-1
Control: retitle -1 binutils: ld reloc sorting causes segfaults on Alpha
This is a binutils bug. Confirmed that it not only causes segfaults
in the libc6.1-alphaev67 package but is also the reason for aptitude
FTBFS on Alpha.
Fixed upstream on the binutils-
Control: tags -1 upstream
The segfaults resulting from installing libc6.1-alphaev67 on an Alpha
ev67 (or better) system have been isolated down to ld reloc sorting
causing crashes in glibc as reported upstream:
https://sourceware.org/bugzilla/show_bug.cgi?id=18867
I'll leave it for the glibc and
On Thu, Jul 16, 2015 at 02:03:57PM +0200, Michael Biebl wrote:
> Am 16.07.2015 um 10:05 schrieb Michael Cree:
> > Patch to fix systemd to use the getxpid syscall on Alpha is available
> > from the Gentoo bug system:
> > https://bugs.gentoo.org/attachment.cgi?id=405976&am
On Thu, Jul 16, 2015 at 02:03:57PM +0200, Michael Biebl wrote:
> Am 16.07.2015 um 10:05 schrieb Michael Cree:
> > Systemd FTBFS on alpha due to missing syscalls. Build log at:
> > http://buildd.debian-ports.org/status/package.php?p=systemd&suite=sid
>
> Looks like sy
Package: libc6.1-alphaev67
Version: 2.19-19
Severity: important
Justification: breaks other software when installed
User: debian-al...@lists.debian.org
Usertags: alpha
Something has gone terribly wrong with the libc6.1-alphaev67 package
with the 2.19-19 upload. A segmentation violation occurs eve
Source: systemd
Version: 222-2
Severity: important
Justification: Fails to build from source but built in the past.
Tag: patch
User: debian-al...@lists.debian.org
Usertags: alpha
Systemd FTBFS on alpha due to missing syscalls. Build log at:
http://buildd.debian-ports.org/status/package.php?p=syst
On Tue, Jul 07, 2015 at 10:13:00AM +0200, Joachim Breitner wrote:
> Hi,
>
> Am Dienstag, den 07.07.2015, 10:09 +1200 schrieb Michael Cree:
> > I see build-depends restricted to the official linux arches for
> > libghc-hspec-dev and libghc-quickcheck2-dev. Could we get the
&g
Source: haskell-path-pieces
Version: 0.2.0-1
Severity: important
Justification: Fails to build from source but built in the past.
haskell-path-pieces FTBFS on the Debian-Ports arches (alpha, hppa and
ppc64) with:
Running debian/hlibrary.setup configure --ghc -v2
--package-db=/var/lib/ghc/package
On Wed, Jun 24, 2015 at 06:52:39PM +0200, Andreas Cadhalpun wrote:
> cmake failed to build on alpha with a testsuite failure:
> CMake Error in CMakeLists.txt:
> The compiler feature "c_function_prototypes" is not known to C compiler
Yeah, I had noticed this too and had tried to debug it but made
[I've trimmed the CCes a bit.]
On Mon, May 18, 2015 at 07:52:12PM +0100, Luke Kenneth Casson Leighton wrote:
> On Sun, May 17, 2015 at 3:48 PM, Andreas Henriksson wrote:
> > Hello Adrian!
> >
> > Thanks for raising awareness about this issue. If there's anything
> > I can do to help please tell m
On Thu, Feb 19, 2015 at 07:59:20PM +0100, Andreas Tille wrote:
> the problematic line is:
>
> ...
> g++ -O3 -DHAVE_BZLIB -Icityhash -Wall -Wsign-compare -g -c -o align.o
> align.cc
> In file included from align.cc:22:0:
> vsearch.h:30:23: fatal error: x86intrin.h: No such file or directory
> #i
reopen 693581
found 693581 7.6.3-20
retitle 693581 ghc in unstable FTBFS on alpha; fix is upstream
thanks
On Tue, Dec 09, 2014 at 10:15:05AM +, Debian Bug Tracking System wrote:
> From: Joachim Breitner
> To: 693581-d...@bugs.debian.org
> Subject: Alpha is removed from Debian
> X-Mailer: Evol
Source: git
Version: 2.1.3-1
Severity: important
Justification: Fails to build from source but built in the past.
Current git in unstable FTBFS with a failure in the test
t9500-gitweb-standalone-no-errors.sh. First noticed on alpha at
debian-ports, see:
http://buildd.debian-ports.org/status/packa
On Tue, Jul 29, 2014 at 11:11:28PM -0400, Mike Miller wrote:
> On Thu, Jul 24, 2014 at 20:00:44 -0400, Mike Miller wrote:
> > On Sun, May 4, 2014 at 12:25:01 +1200, Michael Cree wrote:
> > > octave FTBFS on alpha, with the following:
> > >
> > > ( echo &#
Source: ceph
Version: 0.80.5-1
Severity: normal
Tags: patch
User: debian-al...@lists.debian.org
Usertags: alpha
Ceph FTBFS on Alpha with:
libtool: compile: g++ -DHAVE_CONFIG_H -I. -D__CEPH__ -D_FILE_OFFSET_BITS=64
-D_REENTRANT -D_THREAD_SAFE -D__STDC_FORMAT_MACROS -D_GNU_SOURCE
-DCEPH_LIBDIR=\
Source: postgresql-9.4
Version: 9.4~beta2-1
Severity: wishlist
Tags: patch
User: debian-al...@lists.debian.org
Usertags: alpha
postgresql-9.4 FTBFS on alpha. From the build log [1]:
cc -g -O2 -Wformat -Werror=format-security -I/usr/include/mit-krb5 -fPIC -pie
-DLINUX_OOM_SCORE_ADJ=0 -Wall -Wmis
I am starting to think this tst-eintr3 test suite failure on Alpha
might is a kernel bug. My reasoning goes as follows.
Nowhere does glibc call the wruniq PALcall thus it is not glibc
setting up the thread pointer for a process. The thread pointer
is passed as an argument to the clone() syscall
Source: glibc
Version: 2.19-7
Severity: important
User: debian-al...@lists.debian.org
Usertags: alpha
Justification: Fails to build from source but built in the past.
The test tst-eintr3 sometimes fails in the build of glibc on alpha
and has done so twice in a row in attempting to build 2.19-7.
I
Source: graphviz
Version: 2.38.0-3
Severity: important
User: debian-al...@lists.debian.org
Usertags: alpha
Justification: fails to build from source but used to build
graphviz FTBFS on Alpha with a failed link of cmd/dot. From the build
log [1]
/bin/bash ../../libtool --tag=CC --mode=link alp
Source: openmpi
Version: 1.6.5-8
Severity: important
Tags: patch
User: debian-al...@lists.debian.org
Usertags: alpha
Justification: Causes FTBFS in other packages that built in the past.
The atomic operations defined for Alpha in openmpi can cause weird
behaviour including segfaults leading to fai
On Mon, Jun 30, 2014 at 11:02:24PM +0200, Aurelien Jarno wrote:
> On Sun, Jun 29, 2014 at 09:53:30PM +1200, Michael Cree wrote:
> > Source: glibc
> > Version: 2.19-4
> > Severity: important
> > User: debian-al...@lists.debian.org
> > Usertags: alpha
> > Ju
Source: glibc
Version: 2.19-4
Severity: important
User: debian-al...@lists.debian.org
Usertags: alpha
Justification: Fails to build from source but built in the past.
Finally the fixed gcc-4.8 arrived, however the rebuild of glibc on alpha
failed with unexpected test suite failures. From the log:
Hi
Actually the special casing of the linker flags with -Wl,--no-relax is
no longer needed on Alpha. The linker was fixed maybe a month ago and
relaxation is now working fine on large C/C++ programs.
I was just about to downgrade this bug to minor and retitle it to
suggest removing the alpha spe
Source: libreoffice
Version: 1:4.2.5-1
Severity: important
User: debian-al...@lists.debian.org
Usertags: alpha
Justification: Fails to build from source but built in the past.
Thanks for enabling the build of libreoffice on alpha. It built
successfully at version 1:4.1.6~rc1-1 but has FTBFS ever
Source: blender
Version: 2.70a-2
Severity: important
User: debian-al...@lists.debian.org
Usertags: alpha
Justification: Fails to build from source but built in the past.
blender FTBFS on alpha because it is a 64bit arch but is not listed in
the patch 0011-fix_FTBFS_on_unofficial_64bit_archs.patch
On Wed, Jun 11, 2014 at 02:35:38PM +0200, Aurelien Jarno wrote:
> On Wed, Jun 11, 2014 at 08:55:42PM +1200, Michael Cree wrote:
> > Aurelien: I guess I should file bugs against gcc-4.8 and gcc-4.9 to get
> > that fix into Debian's gcc as the commit does not seem to have been
1 - 100 of 254 matches
Mail list logo
