Hi Everyone, This may be an opportunity for improvement in the build logs. I'm a fellow who helps maintain a library (Crypto++), which is packaged by a Debian maintainer (László).
I'm not familiar with the Debian build machines, so the additional information would be helpful to me during troubleshooting: > By the way, the script outputs: > > +----------------------------------------------------------+ > | Build environment | > +----------------------------------------------------------+ > > Kernel: Linux 4.9.0-8-armmp-lpae armhf (armv7l) > Toolchain package versions: binutils_2.31.1-11 > ... > > That should probably include a 'gcc --version', ' gcc -dumpmachine' > output, 'uname -a' and 'uname -m'. Jeff On Wed, Jan 30, 2019 at 8:12 AM Jeffrey Walton <[email protected]> wrote: > > Hi László, > > https://buildd.debian.org/status/fetch.php?pkg=libcrypto%2B%2B&arch=armel&ver=8.0.0-1 > > This looks interesting. It looks like we are misdetecting NEON availability. > > I'm going to need a little time to reproduce it and turn the knobs. I > perform the Armel testing locally, so I'm guessing the build machine > is setup a little differently than my test machines. > > Could you tell me the output of the following on the build machine: > > g++ -dumpmachine > uname -m > > By the way, the script outputs: > > +----------------------------------------------------------+ > | Build environment | > +----------------------------------------------------------+ > > Kernel: Linux 4.9.0-8-armmp-lpae armhf (armv7l) > Toolchain package versions: binutils_2.31.1-11 > ... > > That should probably include a 'gcc --version', ' gcc -dumpmachine' > output, 'uname -a' and 'uname -m'.
