I ran into something similar once. Don't use the -neon switch for
AARCH64 because it's built in.
On 2/27/19, Steve McIntyre wrote:
> On Wed, Feb 27, 2019 at 06:30:36PM -0500, Jeffrey Walton wrote:
>>On Wed, Feb 27, 2019 at 5:46 PM Steve McIntyre wrote:
>>>
>>> So, I've got to ask - what hardwar
On Wed, Feb 27, 2019 at 06:30:36PM -0500, Jeffrey Walton wrote:
>On Wed, Feb 27, 2019 at 5:46 PM Steve McIntyre wrote:
>>
>> So, I've got to ask - what hardware are you likely targeting here
>> where it matters to build stuff for armel yet also use NEON if it's
>> available? Most people with hardw
On Wed, Feb 27, 2019 at 5:46 PM Steve McIntyre wrote:
>
> ...
> >The problem is, I don't know what the output of or 'g++ -dumpmachine'
> >or 'uname -m' are, so I am not sure if we are misdetecting IS_ARM32 or
> >IS_NEON .
>
> So, I've got to ask - what hardware are you likely targeting here
> wher
On Wed, Feb 27, 2019 at 04:59:50PM -0500, Jeffrey Walton wrote:
>On Wed, Feb 27, 2019 at 4:01 PM Steve McIntyre wrote:
>>
>> OK. In your build log I can see
>>
>> n file included from aria_simd.cpp:19:
>> /usr/lib/gcc/arm-linux-gnueabi/8/include/arm_neon.h:31:2: error: #error
>> "NEON intrinsics
On Wed, Feb 27, 2019 at 4:01 PM Steve McIntyre wrote:
>
> On Wed, Feb 27, 2019 at 02:16:46PM -0500, Jeffrey Walton wrote:
> >
> >I'm investigating a failed build for ARMEL. I don't have access to the
> >build machine so I have to study the logs or ask our package
> >maintainer to run commands for
On Wed, Feb 27, 2019 at 02:16:46PM -0500, Jeffrey Walton wrote:
>Hi Everyone,
>
>I'm investigating a failed build for ARMEL. I don't have access to the
>build machine so I have to study the logs or ask our package
>maintainer to run commands for us.
>
>The build log is at
>https://buildd.debian.org
On Wed, Feb 27, 2019 at 2:59 PM Vagrant Cascadian wrote:
>
> On 2019-02-27, Jeffrey Walton wrote:
> > I'm investigating a failed build for ARMEL. I don't have access to the
> > build machine so I have to study the logs or ask our package
> > maintainer to run commands for us.
> >
> > The build log
On 2019-02-27, Jeffrey Walton wrote:
> I'm investigating a failed build for ARMEL. I don't have access to the
> build machine so I have to study the logs or ask our package
> maintainer to run commands for us.
>
> The build log is at
> https://buildd.debian.org/status/package.php?p=libcrypto%2B%2B&
Hi Everyone,
I'm investigating a failed build for ARMEL. I don't have access to the
build machine so I have to study the logs or ask our package
maintainer to run commands for us.
The build log is at
https://buildd.debian.org/status/package.php?p=libcrypto%2B%2B&suite=experimental
(package) and
9 matches
Mail list logo