I have completed testing, it appears that the smapi error only happens
1 after retrieving mail through a poll, 2 on 64bit arm.
I have tried 32 bit arm works just fine
I have tried 64 bit arm of the following distros, manjaro,debian and ubuntu they all produce the smapi error after first poll and receipt
of pkts.
The only difference that happened in testing was the debian and ubuntu trial I had to set perl=0 in order to compile hpt, the manjaro 64 bit perl=1 and built fine.
Not being a programmer, in fact very little knowledge of the subject
but 11 installs in 24 hours tells me that perhaps its a problem with
64bit arm?
* Forwarded from area 'fidosoft.husky'
Hello Rick,
Sunday April 11 2021, Rick Smith wrote to All:
Not being a programmer, in fact very little knowledge of the
subject but 11 installs in 24 hours tells me that perhaps its a
problem with 64bit arm?
-mstructure-size-boundary=64
to OPTCFLAGS in your huskymak.cfg.
You may also try
-mstrict-align
I added this
# C-compiler: optimization
OPTCFLAGS=-c -s -O3 -fomit-frame-pointer -fstrength-reduce -fPIC -mstructure-size-boundary=64
got this during build
gcc: error: unrecognized command-line option ‘-mstructure-size-boundary=64’
make: *** [Makefile:43: adcase.o] Error 1
* Forwarded from area 'fidosoft.husky'
Hello Rick,
Monday April 12 2021, Rick Smith wrote to Michael Dukelsky:
I added this
# C-compiler: optimization
OPTCFLAGS=-c -s -O3 -fomit-frame-pointer -fstrength-reduce -fPIC
-mstructure-size-boundary=64
Do you build on your rpi or on a PC? What version of gcc do you use?
Do you build on your rpi or on a PC? What version of gcc do youYes I build it right on the pi itself, and I have version gcc version 10.2.0 (GCC) installed.
use?
I see. There is a possibility that some bug in the code manifests itself only
on a 64-bit ARM device. If some owner of such a device finds the bug, it can be
fixed. But I am not inclined to buy a Raspberry Pi just to see whether there is
such a bug or not, sorry.
In the meantime, you may use a 32-bit OS.
Hello Rick,
Monday April 12 2021, Rick Smith wrote to Michael Dukelsky:
I see. There is a possibility that some bug in the code manifests
itself only on a 64-bit ARM device. If some owner of such a device
finds the bug, it can be fixed. But I am not inclined to buy a
Raspberry Pi just to see whether there is such a bug or not, sorry.
device finds the bug, it can be fixed. But I am not inclined to
buy a Raspberry Pi just to see whether there is such a bug or
not, sorry.
Bummer... I would donate a Pi if someone were inclined to research it,
I do not possess such abilities but like hpt enough to contribute
Hello Rick!
13 Apr 21, Rick Smith wrote to Michael Dukelsky:
device finds the bug, it can be fixed. But I am not inclined to
buy a Raspberry Pi just to see whether there is such a bug or
not, sorry.
Bummer... I would donate a Pi if someone were inclined to
research it, I do not possess such abilities but like hpt enough
to contribute
Both of you could think about if a remote ssh session would be an
option.
I see. There is a possibility that some bug in the code manifests itself only on a 64-bit ARM device. If some owner of such a device finds the
bug, it can be fixed. But I am not inclined to buy a Raspberry Pi just to see whether there is such a bug or not, sorry.
In the meantime, you may use a 32-bit OS.
Michael wrote (2021-04-13):
In the meantime, you may use a 32-bit OS.
https://futurewei-cloud.github.io/ARM-Datacenter/qemu/how-to-launch-aa rch64-vm/
or someone could set it up and give you remote access.
Sysop: | Coz |
---|---|
Location: | Anoka, MN |
Users: | 2 |
Nodes: | 4 (0 / 4) |
Uptime: | 139:31:56 |
Calls: | 166 |
Files: | 5,389 |
Messages: | 223,236 |