Hmm, if don't do so the performance will be greatly impacted, since i2pd is basically encrypting/decrypting all the time.
2018-01-05 11:36 GMT+08:00 Aaron M. Ucko <u...@debian.org>: > Source: i2pd > Version: 2.17.0-1 > Severity: important > Tags: upstream > Justification: fails to build from source > User: debian-...@lists.debian.org > Usertags: m68k > > Builds of i2pd for m68k and sh4 (admittedly not release architectures) > have been failing: > > g++ -g -O2 -fdebug-prefix-map=/<<PKGBUILDDIR>>=. > -specs=/usr/share/dpkg/pie-compile.specs -fstack-protector-strong -Wformat > -Werror=format-security -std=c++11 -fPIC -Ilibi2pd -Ilibi2pd_client -maes > -DAESNI -mavx -c -o obj/libi2pd/TunnelGateway.o libi2pd/TunnelGateway.cpp > g++: error: unrecognized command line option '-maes' > g++: error: unrecognized command line option '-mavx' > > (On sh4, g++ suggests that -maes may have been a typo for the vaguely > similar-looking -m2e.) > > Please refrain from using either flag on *any* architecture, since > they limit the portability of the resulting binaries. > > Thanks! > > -- > Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org) > http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu
