From: ng0 <ng0@libertad.pw>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: Mozilla help needed - 0ad, or: how to pass the version to mozjs-38?
Date: Fri, 06 Jan 2017 20:44:48 +0000 [thread overview]
Message-ID: <874m1bkjen.fsf@wasp.i-did-not-set--mail-host-address--so-tickle-me> (raw)
In-Reply-To: <878tqo2i52.fsf@gmail.com>
Hi,
Maxim Cournoyer <maxim.cournoyer@gmail.com> writes:
> Hi ng0!
>
> Have you tried defining MOZJS_MAJOR_VERSION or MOZJS_MINOR_VERSION?
> These are the first errors. Fixing those might make the picture a bit prettier?
It's not about pretty, it's about this being a terrible piece of
unstable, not 100% released software which is public available
and being bundled by some applications (for example 0ad) and you
either accept the bundle or unbundle it.
Today I've found
https://mskalick.fedorapeople.org/mozjs38/mozjs38.spec referenced
from https://bugzilla.redhat.com/show_bug.cgi?id=1269539 and I've
updated my branch but did not progress visibly. Check the 3
patches out and try to build mozjs-38 yourself, still doesn't
build like it should.
https://pagure.io/guix-dev/c/07c579fd3e7e0621ef0f323b6130c74fe5a09f62
> Do other distributions do something special wrt these constants?
>
--
♥Ⓐ ng0 -- https://www.inventati.org/patternsinthechaos/
next prev parent reply other threads:[~2017-01-06 20:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-30 18:04 Mozilla help needed - 0ad, or: how to pass the version to mozjs-38? ng0
2016-12-30 18:04 ` [PATCH 1/3] gnu: Add mozjs-38 ng0
2016-12-30 18:04 ` [PATCH 2/3] gnu: Add 0ad-data ng0
2016-12-30 18:04 ` [PATCH 3/3] gnu: Add 0ad ng0
2017-01-06 14:45 ` Mozilla help needed - 0ad, or: how to pass the version to mozjs-38? ng0
2017-01-06 17:49 ` Maxim Cournoyer
2017-01-06 20:44 ` ng0 [this message]
2017-01-22 10:17 ` Ricardo Wurmus
2017-01-22 10:50 ` ng0
2017-01-22 11:04 ` ng0
2017-01-22 11:36 ` Ricardo Wurmus
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=874m1bkjen.fsf@wasp.i-did-not-set--mail-host-address--so-tickle-me \
--to=ng0@libertad.pw \
--cc=guix-devel@gnu.org \
--cc=maxim.cournoyer@gmail.com \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.