New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Do not merge] firefox: Update to 52.1.2esr #43
Conversation
* Update Firefox to 51.1.2esr * Update respective l10n recipes for 51.1.2esr * Fix obsolete configure options in mozilla.bbclass * Remove TARGET_CC_ARCH because it causes a configure error: > mozbuild.configure.options.InvalidOptionError: CC takes 1 value In addition this work around seems not necessary anymore because it was introduced for built-in nss which isn't used in the current recipe.
I've found some issues in this PR. |
How can I update it with my 45 version on my computer ? thanks |
@ashie I'd check Arch Linux and Debian to see if they did not port it to a newer autoconf. @bianchi77 what do you mean? |
We should not be running autoreconf and avoid needing it. |
Oh I see. |
BTW I'm now investigating another issue. |
I have meta-browser in my computer, how can I update my files to the
newest ? "git merge" or something ?
I'll test it after I can update my old version.
…On 03/07/17 22:33, Otavio Salvador wrote:
@ashie <https://github.com/ashie> I'd check Arch Linux and Debian to
see if they did not port it to a newer autoconf.
@bianchi77 <https://github.com/bianchi77> what do you mean?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#43 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AMkg5JVR0xP8TJGYpXQeceug4C4qPvAOks5sKPvDgaJpZM4Nl_47>.
--
*
/*******/
Sent by Ubuntu LTS 16.04,
Kind regards,
Riko Ho
/*******/
*
|
Please try following procedure:
|
All right, thanks for the clue.
…On 04/07/17 11:44, Takuro Ashie wrote:
Please try following procedure:
|$ cd meta-browser, $ git remote add ashie
https://github.com/ashie/meta-browser.git $ git fetch --all $ git
checkout firefox-52.1.2esr-2 |
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#43 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AMkg5E-tIyD4s-MrK5bs5pEv1dn_VUydks5sKbUVgaJpZM4Nl_47>.
--
*
/*******/
Sent by Ubuntu LTS 16.04,
Kind regards,
Riko Ho
/*******/
*
|
My Autoconf version :
bianchi77@bianchi77-HP-Pavilion-dv6-Notebook-PC:~/poky/build$ autoconf
--version
autoconf (GNU Autoconf) 2.69
Copyright (C) 2012 Free Software Foundation, Inc.
License GPLv3+/Autoconf: GNU GPL version 3 or later
<http://gnu.org/licenses/gpl.html>,
<http://gnu.org/licenses/exceptions.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Written by David J. MacKenzie and Akim Demaille.
bianchi77@bianchi77-HP-Pavilion-dv6-Notebook-PC:~/poky/build$
…On 04/07/17 11:44, Takuro Ashie wrote:
Please try following procedure:
|$ cd meta-browser $ git remote add ashie
https://github.com/ashie/meta-browser.git $ git fetch --all $ git
checkout firefox-52.1.2esr-2 |
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#43 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AMkg5E-tIyD4s-MrK5bs5pEv1dn_VUydks5sKbUVgaJpZM4Nl_47>.
--
*
/*******/
Sent by Ubuntu LTS 16.04,
Kind regards,
Riko Ho
/*******/
*
|
Summary
Update Firefox to 52.1.2esr using debian's patchset
Update respective l10n recipes for 51.1.2esr
Update obsolete configure options in mozilla.bbclass
Remove TARGET_CC_ARCH because it causes a configure error:
In addition this work around seems not necessary anymore because it was
introduced for built-in nss which isn't used in the current recipe.
Required poky version
Issues
There is an issue in this pull request, so I added [Do no merge] label to the title.
Although autoconf2.13 is required to build firefox but it never be found without this patch:
because recent bitbake doesn't include host's PATH.
But I think the above patch isn't proper solution, we shouldn't use host's autoconf2.13 directly to respect the poky's change. How should we solve it? Candidates are:
HOSTTOOLS += "autoconf2.13"
to your local.conf