On Sun, Apr 28, 2024 at 01:02:26PM +0100, Alberto Bertogli wrote:
The problem seems to be that some of the functions that have 64-bit
variants (e.g. pread64, pwrite64) have an assembler name declared for
the regular variant in the header; while other platforms don't do that
and have the two
On Sat, Apr 20, 2024 at 10:30:20AM +0100, Alberto Bertogli wrote:
On Sat, Apr 20, 2024 at 12:00:00AM +0200, Santiago Vila wrote:
I can't offer ssh access either (for now), but I've checked and
this error may be reproduced easily on an arm64 machine using an
armel chroot.
Oohhh this is good to
On Sat, Apr 20, 2024 at 12:00:00AM +0200, Santiago Vila wrote:
El 25/3/24 a las 20:12, Chris Lamb escribió:
Alberto Bertogli wrote:
If you know of a functional official image that I can use to try to
reproduce the problem, or recently-tested steps I can follow to get
a working qemu install,
El 25/3/24 a las 20:12, Chris Lamb escribió:
Alberto Bertogli wrote:
If you know of a functional official image that I can use to try to
reproduce the problem, or recently-tested steps I can follow to get
a working qemu install, please let me know.
Alas, I can't actually be helpful here.
On Mon, Mar 25, 2024 at 07:12:24PM +, Chris Lamb wrote:
Alberto Bertogli wrote:
If you know of a functional official image that I can use to try to
reproduce the problem, or recently-tested steps I can follow to get
a working qemu install, please let me know.
Alas, I can't actually be
Alberto Bertogli wrote:
> If you know of a functional official image that I can use to try to
> reproduce the problem, or recently-tested steps I can follow to get
> a working qemu install, please let me know.
Alas, I can't actually be helpful here. There are no official images
as far as I know…
On Sun, Mar 24, 2024 at 06:00:51PM +, Chris Lamb wrote:
Alberto Bertogli wrote:
I'll try to get a debian install to boot for armhf, but it'll take me a
bit because it's not straightforward (to put it mildly :).
Oh, yeah. :/ Perhaps qemu might be better option here. There might
even be
Alberto Bertogli wrote:
> I'll try to get a debian install to boot for armhf, but it'll take me a
> bit because it's not straightforward (to put it mildly :).
Oh, yeah. :/ Perhaps qemu might be better option here. There might
even be pre-built disk images flying around.
> How urgent/important
ghtforward (to put it mildly :).
How urgent/important is this issue?
Thanks,
Alberto
- Original message -
From: Sebastian Ramacher
To: Debian Bug Tracking System
Subject: Bug#1066938: libfiu: FTBFS on arm{el,hf}: /tmp/cc54dEva.s:726: Error:
symbol `open64' is alrea
it is, say, due to some *general* update to the GLIBC build toolchain.
Best wishes,
Chris
- Original message -
From: Sebastian Ramacher
To: Debian Bug Tracking System
Subject: Bug#1066938: libfiu: FTBFS on arm{el,hf}: /tmp/cc54dEva.s:726: Error:
symbol `open64' is already defined
Date
Source: libfiu
Version: 1.2-2
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org
https://buildd.debian.org/status/fetch.php?pkg=libfiu=armhf=1.2-2=1710292712=0
cc -D_XOPEN_SOURCE=600 -fPIC -DFIU_ENABLE=1
11 matches
Mail list logo