Package binaries are installed into locations specific to the current <s>CPU</s> arch

[yurivict]

On FreeBSD binary paths contain amd64-portbld-freebsd14.3-default64-kv10.
For example: .../pkg/normalizinterface/bin/amd64-portbld-freebsd14.3-default64-kv10/NormalizInterface.so

kv10 is the code of my CPU. But the binaries that were built aren't specific for this CPU. One needs to use -march=native in order to make binaries specific to the current CPU.

This isn't done, and shouldn't be done in general.

Therefore, the kv10 part shouldn't be present. It is meaningless and would likely cause failures if GAP would be run on a different CPU.

Furthermore, the 14.3 part should also not be present. On FreeBSD binaries build on any FreeBSD 14.x run on any other FreeBSD 14.x
Therefore this part is also meaningless and shouldn't be present.

Is there a build-time option of change the string like "amd64-portbld-freebsd14.3-default64-kv10" to some simple fixed string?

This would unbreak it in the above mentioned situations and make it much more package friendly.

[fingolfin]

kv10 stands for "(GAP) kernel version 10" and has nothing to do with your CPU.

[yurivict]

Oh, I see.

But still, freebsd14.3 is harmful.

How can this whole string be changed GAP-wide?

[fingolfin]

The part before "default64" is from config.guess. You can overwrite it with something neutral by passing a suitable --host=TARGETNAME option to configure. I can write and explain more later, I am typing on a phone while feeding the kids right now

[fingolfin]

As explained, you can override this string with the --host=TARGETNAME setting. But given that it appears as amd64-portbld-freebsd14.3 which is not something config.guess can produce, so I am guessing you are already doing that? So instead of passing --host=amd64-portbld-freebsd14.3 perhaps you could just pass --host=amd64-portbld-freebsd14 ?