Did anyone receive a similar mistake?

==> Build () ... 
 LD   wg
Collect2: Fatal Error: Cannot Find "ld"
The compilation is interrupted.
Make: *** [<built -in>: wg] error 1
==> Error: There was a failure in Build (). 
    Interrupt...

UPD I was found a problem LDFLAGS in makepkg.cfg contains the -fuse-ld=mold flag, but the mold package was not installed on the system.

Is AWG 2.0 config compatible with the vanilla parameters and with the Wireguard servers themselves? Jc, Jmin, Jmax, S1-2, H1-4...

I'm struggling to understand Amnezia's documentation. It vaguely claims to be Wireguard compatible even with the 1.5 release, but that's simply not true AFAIK.

Unfortunately, the documentation does not provide detailed information about the parameters. Zane (developer of WG Tunnel) has provided a configuration that is backward compatible with Vanilla WireGuard: https://zaneschepke.com/wgtunnel-docs/features.html#how-to-convert-an-existing-wireguard-config-to-amnezia

Alternatively - self-promotion - I have also written about AmneziaWG and the meaning of the parameters on my website. https://mk16.de/blog/amneziawg-en/

I was asking whether this update broke compatibility with the previous amnezia release, i.e with the 1.5 awg params

If you're not using awg params (Jc, Jmin, Jmax, S1-2, H1-4...), then it support vanilla wireguard. If you start using it, then you're using awg.

1.0.20250901

Is AWG 2.0 config compatible with the vanilla parameters and with the Wireguard servers themselves? Jc, Jmin, Jmax, S1-2, H1-4...

I'm struggling to understand Amnezia's documentation. It vaguely claims to be Wireguard compatible even with the 1.5 release, but that's simply not true AFAIK.

And why did they update amnezia-tools to 2.0 when amnezia-go (f6542209f40f3f8f9e3dc9403d331ad2881fd7e3) is still untagged?

Yea, it looks like the latest changes were reverted in 1.0.20250706 since they were causing issues. Upgraded to that version and "Invalid argument" error is gone.

Seems like 1.0.20250704-1 breaks awg-quick? My known good config broke after this with unable to resolve IP address and invalid argument errors, downgrading solved it.

I'm not sure whether this should go here or elsewhere, but it appears that updating the kernel breaks this package - trying the awg-quick command complains about an unknown connection type, which is only solved by reinstalling this package and amneziawg-linux. Maybe add a pacman hook to reinstall this package after a kernel update?

@VVL Thanks for the quick fix!

@VVL resolvconf should be optional, as it is not necessary if you do not control the DNS via Amnezia! (After settings it to optional please increase pkgrel again)