Hello,
> Either build from ports with the MODCARGO_RUSTFLAGS line changed to this:
>
> MODCARGO_RUSTFLAGS = -C debuginfo=0 -C target-cpu=i586
I get some errors trying to build it from port:
===> Configuring for ripgrep-13.0.0p3
Illegal instruction (core dumped)
*** Error 132 in . (/usr/ports/in
On 2023-06-05, Radek wrote:
> RipGrep caused my issue. When I replaced ripgrep with ggrep the script
> started to work fine.
Can you try a new ripgrep binary built with a different target-cpu type
for me please? The default for the rust compiler is to use SSE instructions
which aren't present on
Just realized that if I edit the subject it will create a new thread in
marc.info.
So.. closing the thread, the solution is here:
https://marc.info/?l=openbsd-misc&m=168594789107213&w=2
Sorry for the mess.
On Sat, 3 Jun 2023 17:37:08 -0500
Andrew Daugherity wrote:
> Unfortunately it looks like
Unfortunately it looks like sh -x does not trace into functions, and
it is something inside "main" which is crashing:
> > set -x or something.
> Sorry, I should have started with that.
>
> test73# doas -u _pfbadhost pf-badhost -O openbsd
> [ ... ]
> + command -v typeset
> + > /dev/null
> + 2>&1
>
On 2023-06-01, Radek wrote:
> Hello Stuart,
>
>> What is the name of the core dump file?
> Actually there isn't any .core file.
> test73# find / -name '*.core'
> test73#
>From your earlier mail:
test73# doas -u _pfbadhost pf-badhost -O openbsd
Hello Diana,
> I realize he shared it here, but this an OpenBSD mailing list. I strongly
> suggest you contact the author, don't just "hope" he regularly monitors this
> list.
>
> I've contacted him before at his email address and he was very prompt in
> reply.
If I don't solve the problem he
Hello Stuart,
> What is the name of the core dump file?
Actually there isn't any .core file.
test73# find / -name '*.core'
test73#
On Tue, 30 May 2023 14:41:37 - (UTC)
Stuart Henderson wrote:
> On 2023-05-30, Radek wrote:
> > Hello and sorry for the late reply,
> >
> >> Did you contact th
I realize he shared it here, but this an OpenBSD mailing list. I strongly
suggest you contact the author, don't just "hope" he regularly monitors this
list.
I've contacted him before at his email address and he was very prompt in reply.
73
diana
KI5PGJ
On May 30, 2023 8:05:04 AM MDT, Radek
On 2023-05-30, Radek wrote:
> Hello and sorry for the late reply,
>
>> Did you contact the individual who provides pf-bafhost script? He has
>> always responded to me when I contacted him.
> No, I didn't. Jordan shared his scripts here, I hope he reads misc@.
>
>> what program dumped core?
> So
Hello and sorry for the late reply,
> Did you contact the individual who provides pf-bafhost script? He has always
> responded to me when I contacted him.
No, I didn't. Jordan shared his scripts here, I hope he reads misc@.
> what program dumped core?
Some parts of [1]. How can I determine whi
On 2023-05-25, Radek wrote:
> Hello,
> I am getting the following error message when I try to run pf-badhost script
> [1] at fresh install 7.3/i386. Have I missed something?
>
> 1. https://www.geoghegan.ca/pub/pf-badhost/latest/install/openbsd.txt
>
> test73# doas -u _pfbadhost pf-badhost -O open
Did you contact the individual who provides pf-bafhost script? He has always
responded to me when I contacted him.
diana
On May 25, 2023 8:26:31 AM MDT, Radek wrote:
>Hello,
>I am getting the following error message when I try to run pf-badhost script
>[1] at fresh install 7.3/i386. Have I m
Hello,
I am getting the following error message when I try to run pf-badhost script
[1] at fresh install 7.3/i386. Have I missed something?
1. https://www.geoghegan.ca/pub/pf-badhost/latest/install/openbsd.txt
test73# doas -u _pfbadhost pf-badhost -O openbsd
doas (r...@test73.my.domain) password
13 matches
Mail list logo
