From: Sergey 'Jin' Bostandzhyan <jin@mediatomb.cc>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: js 185 -> js186_1.0.0
Date: Tue, 10 Apr 2012 17:22:44 +0200 [thread overview]
Message-ID: <20120410152244.GA2852@deadlock.dhs.org> (raw)
In-Reply-To: <CAK18fxFb3xkxbiyCDBncgpyvqOVCgOvzViveLa=aw3CyQPKiQA@mail.gmail.com>
Hi,
On Tue, Apr 10, 2012 at 06:14:58PM +0300, Andrei Gherzan wrote:
> Have a problem while updating js to version 185. This version renames the
> library in libmozjs185. What to do in order to avoid breaking packages which
> need libjs? Another interesting thing is that js is now called js185_1.0.0
> which seems to be actually another package / implementation? I will try to test
> this using symlinks while compiling web package.
JS 1.8.5 is not backwards compatible! This is the reason why they renamed the
libs, you can not link older software against JS 1.8.5 without adaptions, the
new version has a new API.
Kind regards,
Jin
next prev parent reply other threads:[~2012-04-10 15:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-10 15:14 js 185 -> js186_1.0.0 Andrei Gherzan
2012-04-10 15:22 ` Sergey 'Jin' Bostandzhyan [this message]
2012-04-10 16:02 ` Andrei Gherzan
2012-04-10 16:04 ` Saul Wold
2012-04-10 19:16 ` Joshua Lock
2012-04-10 20:31 ` Andrei Gherzan
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=20120410152244.GA2852@deadlock.dhs.org \
--to=jin@mediatomb.cc \
--cc=openembedded-core@lists.openembedded.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