so
far becuase they thought you would.
Is your point that actually it's not just a matter of formwarding -
some armel-specific investigation is needed first to work out what's actually
wrong?
Wookey
--
Principal hats: Debian, Wookware, ARM
http://wookware.org/
signature.asc
Description: PGP signature
On 2023-11-24 18:58 +, Thorsten Glaser wrote:
> Unfortunately, eller is down
Eller had to move hosting provider at short notice. It is now racked
again but needs network configuration for new location. It will
hopefully re-appear by end-Monday.
Wookey
--
Principal hats: Debian, Wookw
3] << 3 | out_results[4] << 4 | out_results[5]
<< 5 |
out_results[6] << 6 | out_results[7] << 7);
}
// last bitmap should be non-zero, fired on gcc-9.3 aarch64 -O3
assert(bitmap[7] != 0);
return 0;
}
Attached is a tested patch.
--
Wookey
polymake codebase, which ICEs all the way back to GCC 6, so this has
been around for a while.
(Thanks for investigating, Alex)
Wookey
--
Principal hats: Linaro, Debian, Wookware, ARM
http://wookware.org/
signature.asc
Description: PGP signature
So this is the failing command from the build:
g++ -c -o
/home/wookey/debian/polymake-4.1/build/Opt/apps/common/cpperl/SparseMatrix-2.o
-MMD -MT
/home/wookey/debian/polymake-4.1/build/Opt/apps/common/cpperl/SparseMatrix-2.o
-MF
/home/wookey/debian/polymake-4.1/build/Opt/apps/common/cpperl
.
Building the one file alone:
g++ -c -o
/home/wookey/debian/polymake-4.1/build/Opt/apps/common/cpperl/SparseMatrix-2.o
-MMD -MT
/home/wookey/debian/polymake-4.1/build/Opt/apps/common/cpperl/SparseMatrix-2.o
-MF
/home/wookey/debian/polymake-4.1/build/Opt/apps/common/cpperl/SparseMatrix-2.o.d
as I have them working.
Wouldn't it make sense to leave this bug open for anyone that needs to
fix this for use on stable? I guess it's linked from the arm64ilp32
port page so the fairly small number of people that care can probably
find it even if closed.
Wookey
--
Principal hats:
6 +117,7 @@
pr77857 \
pr80533 \
pr60818 \
+arm64-ilp32-default \
ifeq ($(libstdcxx_abi),new)
debian_patches += libstdc++-functexcept
>From 7a35625da966a0aa0733843fee7d100e2f026808 Mon Sep 17 00:00:00 2001
From: Wookey
Date: Mon, 8 May 2017 01:58:54 +0100
Subject: [P
Package: gcc-4.9
Version: 4.9.2-3
Severity: normal
Tags: patch
gcc 4.9.1-19 removed the top-level option to set no_biarch_libs = yes when
building crosscompilers.
-ifdef DEB_CROSS_NO_BIARCH
- no_biarch_libs := yes
-endif
+no_biarch_libs :=
Then 4.9.2-2 removed another related stanza
- ifdef
build-deps so it's less of an issue.
Wookey
Index: cross-gcc/debian/rules.conf
===
--- cross-gcc.orig/debian/rules.conf
+++ cross-gcc/debian/rules.conf
@@ -91,7 +91,7 @@ ifeq ($(with_shared_libgcc),yes)
LIBGCC_DEP
+++ Helmut Grohne [2014-11-01 10:38 +0100]:
> On Sat, Nov 01, 2014 at 01:46:48AM +0000, Wookey wrote:
> > To me that sounds like this method is actually the
> > current de-facto default in Debian - it is certainly at least on a par.
>
> I don't think that a feature b
ack uploads in order to keep the
cross-binutils and cross-gcc packages in sync.
> > these bugs ? It seems to me that it would be easy to come up with a
> > workflow that allowed Matthias to usertag these kind of bugs and hand
> > them over to the cross teams.
>
> Sounds rea
Package: gcc-4.9
Followup-For: Bug #755061
More investigation has tracked this down to a missing patch in the
Debian glibc vs the Ubuntu glibc. So merging this bug with #759042.
--
To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact lis
+++ peter green [2014-08-12 04:14 +0100]:
Filed upstream with Linaro to see if they can shed any light.
https://bugs.linaro.org/show_bug.cgi?id=368
Wookey
--
Principal hats: Linaro, Emdebian, Wookware, Balloonboard, ARM
http://wookware.org/
--
To UNSUBSCRIBE, email to debian-gcc-requ
+++ Matthias Klose [2014-08-09 15:58 +0200]:
> Am 09.08.2014 um 12:17 schrieb Wookey:
> > +++ Wookey [2014-08-09 11:12 +0100]:
> >
> >> Can you please do an upload with this in ASAP as the only package that
> >> is out of date (and thus got rejected in the initi
it's not at all clear which package/binary is actually at
fault. Needs more investigation.
Wookey
--
To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive:
https://lists.debian.org/20140
+++ Wookey [2014-08-09 11:12 +0100]:
> Can you please do an upload with this in ASAP as the only package that
> is out of date (and thus got rejected in the initial upload to the
> main debian archive) is now gcc-4.9. And we need that bootstrap set to
> start the official build
-acle-intrinsics.texi exists
+
+ -- Wookey Sat, 09 Aug 2014 00:09:53 +
+
gcc-4.9 (4.9.1-4) unstable; urgency=high
* Update to SVN 20140731 (r213317) from the gcc-4_9-branch.
diff -u gcc-4.9-4.9.1/debian/rules.patch gcc-4.9-4.9.1/debian/rules.patch
--- gcc-4.9-4.9.1/debian/rules.patch
+++ gcc-4.9-
Package: gcc-4.9
Version: 4.9.1-4
Severity: important
User: debian-...@lists.debian.org
Usertag: arm64
Latest gcc failed to build for arm64:
http://buildd.debian-ports.org/status/fetch.php?pkg=gcc-4.9&arch=arm64&ver=4.9.1-4&stamp=1406833943
make[5]: *** No rule to make target 'aarch64-acle-intri
+++ Lisandro Damián Nicanor Pérez Meyer [2014-08-03 16:40 -0300]:
Copied up to Linaro toolchain team at:
https://bugs.linaro.org/show_bug.cgi?id=314
Wookey
--
Principal hats: Linaro, Emdebian, Wookware, Balloonboard, ARM
http://wookware.org/
--
To UNSUBSCRIBE, email to debian-gcc-requ
ce
so far) but in general I expect 4.9 to give less trouble than 4.8
except for things that are broken for all arches.
Did you try an arm64 rebuild with 4.9 in Ubuntu?
Wookey
--
Principal hats: Linaro, Emdebian, Wookware, Balloonboard, ARM
http://wookware.org/
--
To UNSUBSCRIBE, email to debi
bash
diff -u gcc-4.8-4.8.2/debian/changelog gcc-4.8-4.8.2/debian/changelog
--- gcc-4.8-4.8.2/debian/changelog
+++ gcc-4.8-4.8.2/debian/changelog
@@ -1,3 +1,10 @@
+gcc-4.8 (4.8.2-16+arm64.1) unreleased; urgency=low
+
+ * Non-maintainer upload.
+ * Ensure arm-acle-intrinsics.texi exists
+
+ -- wookey
ross-build the compiler itself. So we probably should build
that by default (and document how to turn it off for bootstrapping or
local-build purposes)
I'm not sure if the same argument applies to the D compiler?
Wookey
--
Principal hats: Linaro, Emdebian, Wookware, Balloonboard, ARM
http://wook
Package: gcc-4.7
Version: 4.7.2-12
Severity: normal
Tags: upstream patch
building cross gcc targetting arm64 fails during the gcc stage1 build
due to including limits.h even though stage1 is configured with
--without-headers.
This is the offending bit of log:
/home/wookey/linaro/armv8/toolchain
d a cross-compiler to get started.
Will investigate further.
Wookey
--
Principal hats: Linaro, Emdebian, Wookware, Balloonboard, ARM
http://wookware.org/
--
To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listma
lt, structure
packing being different from other arches, and the floating point
format being odd. There are a few details on
http://wiki.debian.org/ArmPort which may provide clues.
I think you need to debug the binary giving errors in order to get a
better idea where the problem might lie.
Wookey
26 matches
Mail list logo
