Re: wasm-ld for s390x

[Jan Staněk]

Carlos O'Donell  writes:
> It isn't being built because there is no s390x support in lld.
>
> Please add any comments here:
> https://github.com/llvm/llvm-project/issues/57097

OK, good to know.
It seems I will need to workaround this in the meantime.
--
Jan Staněk
Software Engineer, Red Hat
[e-mail]   irc: jstanek

wasm-ld for s390x

[Michael Dawson]

@Jan Stanek  let us know how hard a work around is? I
can reach out to people I know on the IBM side to at least let them know
this is another place/use case where support would be useful.

On Thu, Sep 14, 2023 at 7:24 AM Jan Staněk  wrote:
> Carlos O'Donell  writes:
> > It isn't being built because there is no s390x support in lld.
> >
> > Please add any comments here:
> > https://github.com/llvm/llvm-project/issues/57097
>
> OK, good to know.
> It seems I will need to workaround this in the meantime.
> --
> Jan Staněk
> Software Engineer, Red Hat
> [e-mail]   irc: jstanek
> _______________________________________________
> Wasm-sig mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/[e-mail].o...
> Do not reply to spam, report it:
> https://pagure.io/fedora-infrastructure/new_issue

wasm-ld for s390x

[Jan Staněk]

Michael Dawson  writes:
> @Jan Stanek  let us know how hard a work around is?

I need to package cjs-module-lexer as a separate RPM; this results in a
new cyclical dependency. However, we already have one of those in our
build process, so this should not be that much of an added work.

There is potential issue with using different version of
cjs-module-lexer than what was bundled originally (all NodeJS versions
will use the same rpm), but given that the lexer is feature-frozen,
I'm not too much concerned about that.

All in all, not that hard of a workaround :-)
Having the lld on all arches would still be a boon, though,
since it would enable us to go back to rebuilding the blobs during
nodejs build (as opposed to using separate RPM) if necessary.
--
Jan Staněk
Software Engineer, Red Hat
[e-mail]   irc: jstanek