Generic Autotools Advice:
1) modern autotools (last 10 years or more) support setting variables
like (CXX) on the command line, after any arguments. This is superior to
using the environment because the settings get stored in the logs, which
makes for easier debugging. Something like:
> I'm not sure what I should do at the moment. Is this a problem that
> needs attention? Or am I OK to make install?
Remove the custom CFLAGS and let the build system do its own thing.
The binaries it creates do hardware capability autodetection at startup,
so all the build system really cares
If so, read config.guess - it will tell you how to contribute your
architecture to that project.
Also, you should be able to work around it by specifying the architecture
instead of letting it guess.
Look up the ‹build and ‹target flags to configure.
On 8/1/16, 4:51 PM, "Jeffrey Walton"
On Tue, Aug 2, 2016 at 10:28 AM, Rob Boehne wrote:
> If so, read config.guess - it will tell you how to contribute your
> architecture to that project.
> Also, you should be able to work around it by specifying the architecture
> instead of letting it guess.
> Look up the
On Mon, Aug 1, 2016 at 5:35 PM, Jeffrey Walton wrote:
> Hi Everyone,
>
> I'm testing a Raspberry Pi 3. Its ARMv8 using Boradcom A53-based SoC.
> The SoC is lower end, so its got ASIMD and CRC32, but it lacks PMULL
> and other Crypto extensions. The gadget ships with a 32-bit
Hi Everyone,
I'm testing a Raspberry Pi 3. Its ARMv8 using Boradcom A53-based SoC.
The SoC is lower end, so its got ASIMD and CRC32, but it lacks PMULL
and other Crypto extensions. The gadget ships with a 32-bit Raspbian
OS, so its effectively in 32-bit mode.
My shell exports CFLAGS and