On 9/29/21 00:36, Cameron MacPherson wrote:
> i can confirm that the ppc64 snapshot packages work without illegal
> instructions
Comparing the build logs, it seems that this an issue with the newer version
of autoconf that was used to build version 3.4.2-2. Looking at the log for
3.4.2-2, a lot of
i can confirm that the ppc64 snapshot packages work without illegal
instructions
On Tue, Sep 28, 2021 at 12:54 PM John Paul Adrian Glaubitz <
glaub...@physik.fu-berlin.de> wrote:
> Hi!
>
> On 9/28/21 21:34, John Paul Adrian Glaubitz wrote:
> > OK. I'm regenerating the chroots on the build servers
On 9/28/21 22:27, John Paul Adrian Glaubitz wrote:
> Yes. And this is not acceptable because they are manipulating the baseline.
And just for confirmation. After closely inspecting the build log, it becomes
obvious that "-mcpu=power8" is actually passed to GCC during build.
Adrian
--
.''`. Jo
On Tue, Sep 28, 2021 at 10:27:59PM +0200, John Paul Adrian Glaubitz wrote:
> Yes. And this is not acceptable because they are manipulating the baseline.
>
> Thanks for catching this. This is our bug!
I would be surprised if powerpc is the only architecture bitten by this.
What is i386 being compi
On Tue, Sep 28, 2021 at 04:26:04PM -0400, Lennart Sorensen wrote:
> On Tue, Sep 28, 2021 at 09:34:23PM +0200, John Paul Adrian Glaubitz wrote:
> > OK. I'm regenerating the chroots on the build servers now and then
> > trigger another rebuild of the package. If that still doesn't help,
> > we know t
On 9/28/21 22:26, Lennart Sorensen wrote:
> Would this be a problem:
>
> powerpc*)
> cputype=`((grep cpu /proc/cpuinfo | head -n 1 | cut -d: -f2 | cut -d,
> -f1 | $SED 's/ //g') ; /usr/bin/machine ; /bin/machine; grep CPU
> /var/run/dmesg.boot | head -n 1 | cut -d" " -f2) 2> /dev/null`
>
On Tue, Sep 28, 2021 at 09:34:23PM +0200, John Paul Adrian Glaubitz wrote:
> OK. I'm regenerating the chroots on the build servers now and then
> trigger another rebuild of the package. If that still doesn't help,
> we know there is some runtime detection which enables these instructions
> during b
Hi!
On 9/28/21 21:34, John Paul Adrian Glaubitz wrote:
> OK. I'm regenerating the chroots on the build servers now and then
> trigger another rebuild of the package. If that still doesn't help,
> we know there is some runtime detection which enables these instructions
> during build and I have to
On 9/28/21 17:49, Riccardo Mottola wrote:
> Thanks. I got from there libffi8_3.4.2-2+b1_powerpc.deb
>
> I replaced the one I compiled myself and I immediately get illegal
> instruction in a libffi-using app.
OK. I'm regenerating the chroots on the build servers now and then
trigger another rebuil
Hello!
On 9/28/21 17:46, Riccardo Mottola wrote:
> I did this on my PowerBook G4 .
> I had some issues with build-dep - it doesn't like my deb-src in the
> sources file:
>
> apt-get build-dep libffi
> Reading package lists... Done
> E: You must put some 'deb-src' URIs in your sources.list
>
> I
i installed the b1 version of libffi8 and the illegal instruction messages
are back
[ 16.195961] fail2ban-server[384]: illegal instruction (4) at
3fffa5270970 nip 3fffa5270970 lr 3fffa526ff90 code 1 in
libffi.so.8.1.0[3fffa5268000+c000]
[ 16.196045] fail2ban-server[384]: code: b1090008 f949000
Hi Adrian
John Paul Adrian Glaubitz wrote:
>>
>
> It’s been moved:
>
> > http://incoming.ports.debian.org/buildd/packages/sid/main/
>
Thanks. I got from there libffi8_3.4.2-2+b1_powerpc.deb
I replaced the one I compiled myself and I immediately get illegal
instruction in a libffi-using app.
I
Hello,
John Paul Adrian Glaubitz wrote:
>
> It's not being built with -mnative as far I could tell from the logs.
>
> But you can verify whether this is the case or not by building the
> Debian package on your local machine:
>
> $ apt-get install devscripts
> $ dget -u
> https://deb.debian.org/de
> On Sep 28, 2021, at 3:14 PM, Riccardo Mottola
> wrote:
>
> Hello Adrian
>
> John Paul Adrian Glaubitz wrote:
>> $ wget http://incoming.ports.debian.org/libffi8_3.4.2-2+b1_powerpc.deb
>> $ dpkg -i libffi8_3.4.2-2+b1_powerpc.deb
>>
>> For ppc64:
>>
>> $ wget http://incoming.ports.debian.or
Hello Adrian
John Paul Adrian Glaubitz wrote:
> $ wget http://incoming.ports.debian.org/libffi8_3.4.2-2+b1_powerpc.deb
> $ dpkg -i libffi8_3.4.2-2+b1_powerpc.deb
>
> For ppc64:
>
> $ wget http://incoming.ports.debian.org/libffi8_3.4.2-2+b1_ppc64.deb
> $ dpkg -i libffi8_3.4.2-2+b1_ppc64.deb
I can
On 9/28/21 12:58, John Paul Adrian Glaubitz wrote:> On 9/28/21 12:55, Cameron
MacPherson wrote:
>> after building and installing it locally using your commands (i had to add
>> --no-sign to dpkg-buildpackage) it works. no illegal instructions
>
> Well, that's becoming intesting now. I'm going to
On 9/28/21 12:55, Cameron MacPherson wrote:
> after building and installing it locally using your commands (i had to add
> --no-sign to dpkg-buildpackage) it works. no illegal instructions
Well, that's becoming intesting now. I'm going to have the packages rebuilt
on the buildds now.
Adrian
--
after building and installing it locally using your commands (i had to add
--no-sign to dpkg-buildpackage) it works. no illegal instructions
On Tue, Sep 28, 2021 at 3:08 AM John Paul Adrian Glaubitz <
glaub...@physik.fu-berlin.de> wrote:
> Hi Cameron!
>
> On 9/28/21 11:38, Cameron MacPherson wrot
Hi Cameron!
On 9/28/21 11:38, Cameron MacPherson wrote:
> i recompiled everything with gcc-10 and there is no change vs gcc version 11
As a last test, can you try rebuilding the Debian package locally and test that?
$ apt-get install devscripts
$ dget -u https://deb.debian.org/debian/pool/main/l
i recompiled everything with gcc-10 and there is no change vs gcc version 11
On Tue, Sep 28, 2021 at 2:24 AM John Paul Adrian Glaubitz <
glaub...@physik.fu-berlin.de> wrote:
> On 9/28/21 11:22, Cameron MacPherson wrote:
> > after running the commands you listed i repeated my process with the new
On 9/28/21 11:22, Cameron MacPherson wrote:
> after running the commands you listed i repeated my process with the new
> libffi.so.8 from v3.4.2 vs HEAD and there is no change. both of them work.
> i am using gcc 11.2.0-7
Ah, the compiler is a good point.
Try building with gcc-10 instead by setti
after running the commands you listed i repeated my process with the new
libffi.so.8 from v3.4.2 vs HEAD and there is no change. both of them work.
i am using gcc 11.2.0-7
On Tue, Sep 28, 2021 at 2:07 AM John Paul Adrian Glaubitz <
glaub...@physik.fu-berlin.de> wrote:
> Hi Cameron!
>
> On 9/28/21
Hi Cameron!
On 9/28/21 10:59, Cameron MacPherson wrote:
> i ran apt install --reinstall libffi8, restarted the system and the
> following messages reappeared
>
> [ 16.874069] fail2ban-server[384]: illegal instruction (4) at
> 3fff7ef95970 nip 3fff7ef95970 lr 3fff7ef94f90 code 1 in
> libffi.so.8
i ran apt install --reinstall libffi8, restarted the system and the
following messages reappeared
[ 16.874069] fail2ban-server[384]: illegal instruction (4) at
3fff7ef95970 nip 3fff7ef95970 lr 3fff7ef94f90 code 1 in
libffi.so.8.1.0[3fff7ef8d000+c000]
[ 16.874154] fail2ban-server[384]: code: b1
Hello!
On 9/28/21 10:33, Cameron MacPherson wrote:
> after ./autogen.sh && ./configure && make i then copied the new
> libffi.so.8.1.0 from ~/libffi/powerpc64-unknown-linux-gnu/.libs to
> /usr/lib/powerpc64-linux-gnu and that solved it. no more illegal
> instruction messages
Did you verify that i
hi,
after ./autogen.sh && ./configure && make i then copied the new
libffi.so.8.1.0 from ~/libffi/powerpc64-unknown-linux-gnu/.libs to
/usr/lib/powerpc64-linux-gnu and that solved it. no more illegal
instruction messages
On Tue, Sep 28, 2021 at 12:44 AM John Paul Adrian Glaubitz <
glaub...@physik
Hello Riccardo!
On 9/26/21 19:31, Riccardo Mottola wrote:
> While out to a walk, I had the same idea.. I wasn't sure it would work
> but "ldd" confirms that the local version of the library is picked up.
>
> Thus I got latest git of libffi from the repository you usggested. Configured
> and buil
Hello!
On 9/28/21 06:18, Cameron MacPherson wrote:
> i too am having problems with libffi8 on a powermac g5
>
> # dmesg
> ...
> [ 16.257543] fail2ban-server[384]: illegal instruction (4) at
> 3fffb4283970 nip 3fffb4283970 lr 3fffb4282f90 code 1 in
> libffi.so.8.1.0[3fffb427b000+c000]
> ...
> #
Hello!
On 9/27/21 23:43, Riccardo Mottola wrote:
> yes please check that - I will access this computer only next weekend,
> so for now no test, I only have my laptop with me, but 32bit might not
> be affected.
It's not being built with -mnative as far I could tell from the logs.
But you can veri
i too am having problems with libffi8 on a powermac g5
# dmesg
...
[ 16.257543] fail2ban-server[384]: illegal instruction (4) at
3fffb4283970 nip 3fffb4283970 lr 3fffb4282f90 code 1 in
libffi.so.8.1.0[3fffb427b000+c000]
...
# ls -l libffi*
-rw-r--r-- 1 root root 68696 Feb 20 2021 libffi.so.7.1.
I confirm that. I had problem with Arctic fox an Fadedorb because of lack of
that lib.
On my G4 machines I have installed missing lib from Fienix repos.
Terv,
Kristoffer
--
Wiadomość wysłana za pomocą serwisu Tutanota, oferującego bezpieczną i wolną
od reklam usługę e-mail:
https://tutanot
Hi,
just for info - the issue happens also on PowerPC G4 32bit.
strange nobody else shares this?
Riccardo
Hi,
John Paul Adrian Glaubitz wrote:
No I cannot, 3.4.2 (cleaned, reconfigured, installed) seems to work fine out of
the box.
So either the release is not well tagged, or there is an issue with the Debian
package.
You could try rebuilding the libffi Debian package locally and see if that
ma
On 9/26/21 22:38, Riccardo Mottola wrote:
> No I cannot, 3.4.2 (cleaned, reconfigured, installed) seems to work fine out
> of the box.
>
> So either the release is not well tagged, or there is an issue with the
> Debian package.
You could try rebuilding the libffi Debian package locally and see
Hi Adrian,
On 2021-09-26 18:34:47 +0100 John Paul Adrian Glaubitz
wrote:
On 9/26/21 19:31, Riccardo Mottola wrote:
Would you like me to build the latest "release" of libffi ?
Yes, please test the 3.4.2 release by checking out the "v3.4.2" tag:
$ git checkout v3.4.2
If you can reproduce
On 9/26/21 19:31, Riccardo Mottola wrote:
> Would you like me to build the latest "release" of libffi ?
Yes, please test the 3.4.2 release by checking out the "v3.4.2" tag:
$ git checkout v3.4.2
If you can reproduce the issue then, please start bisecting with:
$ git bisect start
$ git bisect g
Hi Adrian,
On 2021-09-26 15:43:02 +0200 John Paul Adrian Glaubitz
wrote:
On 9/26/21 15:39, Riccardo Mottola wrote:
That's a bit a similar issue with building libffi locally. In
/usr/local
I am unsure it would be picked up. I can of course still do it and
perhaps
have GNUstep pick it up a
On 9/26/21 15:39, Riccardo Mottola wrote:
> That's a bit a similar issue with building libffi locally. In /usr/local
> I am unsure it would be picked up. I can of course still do it and perhaps
> have GNUstep pick it up and do some tests there.
>
> In the meanwhile, I'm setting up to configure and
Hello Adrian,
On 2021-09-26 13:54:33 +0100 John Paul Adrian Glaubitz
wrote:
Hello!
On 9/26/21 14:36, Riccardo Mottola wrote:
I upgraded my iMac G5 to latest debian, including kernel 5.14 !
The good thing is that the new kernel boots and X11 comes up.
The bad news is lots of applications
On 9/26/21 14:56, John Paul Adrian Glaubitz wrote:
> On 9/26/21 14:54, John Paul Adrian Glaubitz wrote:
>> Did you verify that downgrading the libffi package fixes the problem?
>>
>> If yes, you may file an upstream bug here [1]. The powerpc-related changes I
>> can
>> see at first glance are thes
On 9/26/21 14:54, John Paul Adrian Glaubitz wrote:
> Did you verify that downgrading the libffi package fixes the problem?
>
> If yes, you may file an upstream bug here [1]. The powerpc-related changes I
> can
> see at first glance are these [2].
My guess would be this change:
> https://github.
Hello!
On 9/26/21 14:36, Riccardo Mottola wrote:
> I upgraded my iMac G5 to latest debian, including kernel 5.14 !
> The good thing is that the new kernel boots and X11 comes up.
>
> The bad news is lots of applications crash and they all have one thing in
> common, libffi.
>
>
> So e.g. a bui
Hi,
I upgraded my iMac G5 to latest debian, including kernel 5.14 !
The good thing is that the new kernel boots and X11 comes up.
The bad news is lots of applications crash and they all have one thing
in common, libffi.
So e.g. a build of ArcticFox fails:
multix@PPC970FX:~/code/Arctic-Fox$ .
43 matches
Mail list logo
