From: paper42 <paper42@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: New package: mozjs102-102.3.0
Date: Tue, 22 Nov 2022 22:00:30 +0100 [thread overview]
Message-ID: <20221122210030.WccFiTzc_eybS_U3WBmP1qZeiY19fdTZLDiZQWrsyyg@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-39498@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 2326 bytes --]
There's a merged pull request on the void-packages repository
New package: mozjs102-102.3.0
https://github.com/void-linux/void-packages/pull/39498
Description:
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: **briefly**
all patches are imported from mozjs91 except for:
* rebased fix-build-ppc32.patch
* imported use-fallback-atomic-operations-on-armv6.patch to fix some issues with armv6l
currently the armv6 builds fails with
```
/builddir/.xbps-mozjs102/wrappers/arm-linux-musleabihf-c++ --sysroot /usr/arm-linux-musleabihf -o Unified_cpp_js_src_jit12.o -c -I/builddir/firefox-102.3.0/js/src/dist/system_wrappers -include /builddir/firefox-102.3.0/config/gcc_hidden.h -fstack-protector-strong -DNDEBUG=1 -DTRIMMED=1 -DJS_HAS_CTYPES -DEXPORT_JS_API -DMOZ_HAS_MOZGLUE -I/builddir/firefox-102.3.0/js/src/jit -I/builddir/firefox-102.3.0/js/src/js/src/jit -I/builddir/firefox-102.3.0/js/src/js/src -I/builddir/firefox-102.3.0/js/src -I/builddir/firefox-102.3.0/js/src/dist/include -I/usr/arm-linux-musleabihf/usr/include/nspr -DMOZILLA_CLIENT -include /builddir/firefox-102.3.0/js/src/js/src/js-confdefs.h -Wall -Wempty-body -Wignored-qualifiers -Wpointer-arith -Wsign-compare -Wtype-limits -Wunreachable-code -Wno-invalid-offsetof -Wc++2a-compat -Wduplicated-cond -Wimplicit-fallthrough -Wno-error=maybe-uninitialized -Wno-error=deprecated-declarations -Wno-error=array-bounds -Wno-error=coverage-mismatch -Wno-error=free-nonheap-object -Wno-multistatement-macros -Wno-error=class-memaccess -Wno-error=deprecated-copy -Wformat -Wformat-overflow=2 -Wno-psabi -fno-sized-deallocation -fno-aligned-new -fstack-clash-protection -D_FORTIFY_SOURCE=2 -O2 -pipe -march=armv6 -mfpu=vfp -mfloat-abi=hard -I/usr/arm-linux-musleabihf/usr/include -fdebug-prefix-map=/builddir/firefox-102.3.0/js/src=. -fPIC -fno-rtti -ffunction-sections -fdata-sections -fno-exceptions -fno-math-errno -pthread -pipe -gdwarf-4 -fno-omit-frame-pointer -funwind-tables -Werror=format -Wno-attributes -fno-strict-aliasing -ffp-contract=off -MD -MP -MF .deps/Unified_cpp_js_src_jit12.o.pp Unified_cpp_js_src_jit12.cpp
{standard input}: Assembler messages:
{standard input}:14103: Error: selected processor does not support `isb' in ARM mode
```
prev parent reply other threads:[~2022-11-22 21:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-27 23:17 [PR PATCH] " paper42
2022-10-26 14:56 ` [PR PATCH] [Updated] " paper42
2022-11-13 7:44 ` oreo639
2022-11-13 7:46 ` oreo639
2022-11-22 16:33 ` [PR PATCH] [Updated] " paper42
2022-11-22 20:26 ` paper42
2022-11-22 20:59 ` oreo639
2022-11-22 21:00 ` paper42 [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20221122210030.WccFiTzc_eybS_U3WBmP1qZeiY19fdTZLDiZQWrsyyg@z \
--to=paper42@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).