On Mon, Apr 19, 2021 at 09:24:31AM +0300, Gleb Popov wrote:
> On Mon, Apr 19, 2021 at 8:52 AM The Doctor via freebsd-ports <
> freebsd-ports@freebsd.org> wrote:
>
> > Why am I getting:
> >
> > In file included from Unified_cpp_libsoundtouch_src0.cpp:47:
> > /usr/ports/www/firefox/work/firefox-88.0
On Mon, Apr 19, 2021 at 8:52 AM The Doctor via freebsd-ports <
freebsd-ports@freebsd.org> wrote:
> Why am I getting:
>
> In file included from Unified_cpp_libsoundtouch_src0.cpp:47:
> /usr/ports/www/firefox/work/firefox-88.0/media/libsoundtouch/src/InterpolateShannon.cpp:71:9:
> warning: 'PI' macr
Why am I getting:
In file included from Unified_cpp_libsoundtouch_src0.cpp:47:
/usr/ports/www/firefox/work/firefox-88.0/media/libsoundtouch/src/InterpolateShannon.cpp:71:9:
warning: 'PI' macro redefined [-Wmacro-redefined]
#define PI 3.1415926536
^
/usr/ports/www/firefox/work/firefox-88.0
Michal Meloun writes:
> On 08.05.2017 10:56, Dimitry Andric wrote:
>
>> On 8 May 2017, at 05:33, bob prohaska wrote:
>>>
>>> On Fri, May 05, 2017 at 10:01:40PM -0700, bob prohaska wrote:
It appears that using
make CFLAGS='-mcpu=cortex-a7'
is sufficient to get past the NEON not ena
On Mon, May 08, 2017 at 01:08:46PM +0200, Michal Meloun wrote:
>
> On 08.05.2017 10:56, Dimitry Andric wrote:
> > On 8 May 2017, at 05:33, bob prohaska wrote:
> >>
> >> Is this worth a bug report, or is firefox too far over the horizon
> >> for freebsd-arm?
> >>
> >
> > Also, I wonder why they do
On 8 May 2017, at 05:33, bob prohaska wrote:
>
> On Fri, May 05, 2017 at 10:01:40PM -0700, bob prohaska wrote:
>> It appears that using
>> make CFLAGS='-mcpu=cortex-a7'
>> is sufficient to get past the NEON not enabled error.
>>
>
> The next problem appears to be
>
>
> /usr/ports/www/firefox
On Fri, May 05, 2017 at 10:01:40PM -0700, bob prohaska wrote:
> It appears that using
> make CFLAGS='-mcpu=cortex-a7'
> is sufficient to get past the NEON not enabled error.
>
The next problem appears to be
/usr/ports/www/firefox/work/firefox-53.0.2/media/openmax_dl/dl/sp/src/armSP_FFT_CToC_FC
On Fri, May 05, 2017 at 05:44:16PM -0700, Mark Millard wrote:
>
> (There are some fairly general, but not universal,
> techniques for supplying compiler options to ports.
> I've no clue were firefox lands for such
> properties.)
>
It appears that using
make CFLAGS='-mcpu=cortex-a7'
is sufficient
On 2017-May-5, at 4:01 PM, bob prohaska wrote:
> On Fri, May 05, 2017 at 12:38:14PM -0700, Mark Millard wrote:
>>
>> An rpi2 has Cortex-A7 (armv7-A) cores that have NEON
>> but armv6 does not.
>>
>> There is some possibility that with something like
>> -mcpu=cortex-a7 in use as a compiler optio
On Fri, May 05, 2017 at 12:38:14PM -0700, Mark Millard wrote:
>
> An rpi2 has Cortex-A7 (armv7-A) cores that have NEON
> but armv6 does not.
>
> There is some possibility that with something like
> -mcpu=cortex-a7 in use as a compiler option that
> NEON would be used.
What's the simplest way to
On 2017-May-5, at 11:28 AM, bob prohaska wrote:
> On Fri, May 05, 2017 at 09:30:39AM -0700, Mark Millard wrote:
>>
>> Wrong neon.
>>
>>
> Ahh, what I feared 8-)
>
>
>> https://developer.arm.com/technologies/neon says:
>>
>
> I did find that page, but harbored a faint (and apparently
> misg
On Fri, May 05, 2017 at 09:30:39AM -0700, Mark Millard wrote:
>
> Wrong neon.
>
>
Ahh, what I feared 8-)
> https://developer.arm.com/technologies/neon says:
>
I did find that page, but harbored a faint (and apparently
misguided) hope that the port might in some fashion implement
the vector i
On 2017-May-5, at 8:13 AM, bob prohaska wrote:
> In trying to compile www/firefox on RPI2 running -current the build now stops
> with
>
> error: "NEON support not enabled"
>
> The port at www/neon is compiled and installed.
Wrong neon.
> Thanks for reading, any guidance appreciated.
https:
In trying to compile www/firefox on RPI2 running -current the build now stops
with
error: "NEON support not enabled"
The port at www/neon is compiled and installed.
Thanks for reading, any guidance appreciated.
bob prohaska
___
freebsd-ports@freebsd
14 matches
Mail list logo
