Re: Any hope of compiling firefox port on ARM?

2017-04-20 Thread bob prohaska
On Wed, Apr 19, 2017 at 12:49:37PM +0200, Dimitry Andric wrote:
> How is that even possible?  I committed the fix on Oct 12, 2016:
> 
> Maybe you are seeing a different problem altogether?  

Perhaps. Along that line, I've submitted Bug 218782. Hope it was
done correctlythe diagnostic files were > 2MB, so I put them
at http://www.zefox.net/~fbsd/rpi2/firefox/ 

> Or your ports tree has no been updated?
>
 
/usr/ports is at 438916, /usr/src is at 317106

Thanks for reading, and any guidance!

bob prohaska

___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"


Re: Any hope of compiling firefox port on ARM?

2017-04-19 Thread Dimitry Andric
On 19 Apr 2017, at 00:17, bob prohaska  wrote:
> 
> On Tue, Apr 18, 2017 at 09:43:23PM +0200, Jan Beich wrote:
>> 
>> See bug 211069 which was duped against bug 203989 that triggered a
>> different assertion. The above error did show up on armv6 buildbot[1]
>> but nowadays is blocked by other ports.
>> 
> What is meant by the term "blocked by other ports"? The error still
> comes up with firefox and -current as of yesterday.

How is that even possible?  I committed the fix on Oct 12, 2016:

  https://svnweb.freebsd.org/changeset/ports/423893

then merged it to the 2016Q4 quarterly branch on Oct 14, 2016:

  https://svnweb.freebsd.org/changeset/ports/423974

Maybe you are seeing a different problem altogether?  Or your ports tree
has no been updated?

-Dimitry



signature.asc
Description: Message signed with OpenPGP


Re: Any hope of compiling firefox port on ARM?

2017-04-18 Thread bob prohaska
On Tue, Apr 18, 2017 at 09:43:23PM +0200, Jan Beich wrote:
> 
> See bug 211069 which was duped against bug 203989 that triggered a
> different assertion. The above error did show up on armv6 buildbot[1]
> but nowadays is blocked by other ports.
> 
What is meant by the term "blocked by other ports"? The error still
comes up with firefox and -current as of yesterday. 

Long ago I brought the issue up on the freebsd-arm list and was told,
iiuc, that it's an upstream problem in clang/llvm and not  fixable by 
the freebsd-arm community. My present query was more an effort to find
out if there is any prospect for a short-term workaround. Far as I can
tell there isn't even a cross-compiled firefox package for RPI2 

Thanks for replying!

bob prohaska
 
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"


Re: Any hope of compiling firefox port on ARM?

2017-04-18 Thread Dimitry Andric
On 18 Apr 2017, at 21:43, Jan Beich  wrote:
> 
> Dimitry Andric  writes:
> 
>> On 18 Apr 2017, at 20:47, bob prohaska  wrote:
>> 
>>> 
>>> For some time (years?) firefox compiles have failed with an error message
>>> along the lines of
>>> 
>>> Assertion failed: (isReg() && "This is not a register operand!"),
>>> function getReg, file
>>> /usr/src/contrib/llvm/include/llvm/MC/MCInst.h, line 64.
>>> c++: error: unable to execute command: Abort trap (core dumped)
>>> c++: error: clang frontend command failed due to signal (use -v to see 
>>> invocation)
>>> FreeBSD clang version 4.0.0 (tags/RELEASE_400/final 297347) (based on LLVM 
>>> 4.0.0)
>>> Target: armv6--freebsd12.0-gnueabihf
>>> Thread model: posix
>>> InstalledDir: /usr/bin
>>> c++: note: diagnostic msg: PLEASE submit a bug report to
>>> https://bugs.freebsd.org/submit/ and include the crash backtrace,
>>> preprocessed source, and associated run script.
>>> 
>>> Is there any hope of a fix, whether to clang or firefox?
>> 
>> Have you tried doing what it asks, e.g. file a bug report? :)
>> 
>> I can find no such bug report in our tracker.  Please submit a bug with
>> the two files (.sh and .cpp) it generates in /tmp.
> 
> See bug 211069 which was duped against bug 203989 that triggered a
> different assertion.

Hmm, annoying that bugzilla doesn't find those bugs, if you search for
any keyword in the error message.  So this bug has been solved for 6
months now, in any case.

-Dimitry



signature.asc
Description: Message signed with OpenPGP


Re: Any hope of compiling firefox port on ARM?

2017-04-18 Thread Jan Beich
Dimitry Andric  writes:

> On 18 Apr 2017, at 20:47, bob prohaska  wrote:
>
>> 
>> For some time (years?) firefox compiles have failed with an error message
>> along the lines of
>> 
>> Assertion failed: (isReg() && "This is not a register operand!"),
>> function getReg, file
>> /usr/src/contrib/llvm/include/llvm/MC/MCInst.h, line 64.
>> c++: error: unable to execute command: Abort trap (core dumped)
>> c++: error: clang frontend command failed due to signal (use -v to see 
>> invocation)
>> FreeBSD clang version 4.0.0 (tags/RELEASE_400/final 297347) (based on LLVM 
>> 4.0.0)
>> Target: armv6--freebsd12.0-gnueabihf
>> Thread model: posix
>> InstalledDir: /usr/bin
>> c++: note: diagnostic msg: PLEASE submit a bug report to
>> https://bugs.freebsd.org/submit/ and include the crash backtrace,
>> preprocessed source, and associated run script.
>> 
>> Is there any hope of a fix, whether to clang or firefox?
>
> Have you tried doing what it asks, e.g. file a bug report? :)
>
> I can find no such bug report in our tracker.  Please submit a bug with
> the two files (.sh and .cpp) it generates in /tmp.

See bug 211069 which was duped against bug 203989 that triggered a
different assertion. The above error did show up on armv6 buildbot[1]
but nowadays is blocked by other ports.

[1] http://beefy8.nyi.freebsd.org/data/latest-per-pkg/firefox/
http://beefy15.nyi.freebsd.org/data/latest-per-pkg/firefox/ (IPv6-only)
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"


Re: Any hope of compiling firefox port on ARM?

2017-04-18 Thread Dimitry Andric
On 18 Apr 2017, at 20:47, bob prohaska  wrote:
> 
> For some time (years?) firefox compiles have failed with an error message
> along the lines of
> 
> Assertion failed: (isReg() && "This is not a register operand!"), function 
> getReg, file /usr/src/contrib/llvm/include/llvm/MC/MCInst.h, line 64.
> c++: error: unable to execute command: Abort trap (core dumped)
> c++: error: clang frontend command failed due to signal (use -v to see 
> invocation)
> FreeBSD clang version 4.0.0 (tags/RELEASE_400/final 297347) (based on LLVM 
> 4.0.0)
> Target: armv6--freebsd12.0-gnueabihf
> Thread model: posix
> InstalledDir: /usr/bin
> c++: note: diagnostic msg: PLEASE submit a bug report to 
> https://bugs.freebsd.org/submit/ and include the crash backtrace, 
> preprocessed source, and associated run script.
> 
> Is there any hope of a fix, whether to clang or firefox?

Have you tried doing what it asks, e.g. file a bug report? :)

I can find no such bug report in our tracker.  Please submit a bug with
the two files (.sh and .cpp) it generates in /tmp.

-Dimitry



signature.asc
Description: Message signed with OpenPGP


Any hope of compiling firefox port on ARM?

2017-04-18 Thread bob prohaska
For some time (years?) firefox compiles have failed with an error message
along the lines of

Assertion failed: (isReg() && "This is not a register operand!"), function 
getReg, file /usr/src/contrib/llvm/include/llvm/MC/MCInst.h, line 64.
c++: error: unable to execute command: Abort trap (core dumped)
c++: error: clang frontend command failed due to signal (use -v to see 
invocation)
FreeBSD clang version 4.0.0 (tags/RELEASE_400/final 297347) (based on LLVM 
4.0.0)
Target: armv6--freebsd12.0-gnueabihf
Thread model: posix
InstalledDir: /usr/bin
c++: note: diagnostic msg: PLEASE submit a bug report to 
https://bugs.freebsd.org/submit/ and include the crash backtrace, preprocessed 
source, and associated run script.

Is there any hope of a fix, whether to clang or firefox?

Thanks for reading, and any insights...

bob prohaska

___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"