-
Notifications
You must be signed in to change notification settings - Fork 14
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
Node 6.5.0 #68
Node 6.5.0 #68
Conversation
Relevant issues: Patch coming from (patch merged after 6.5.0) : |
@huseyinkozan can you update this to 6.9.0—thanks!! |
@rwaldron Tried to update but no luck at first build. No time to retry. |
I've updated @huseyinkozan's branch to Node
I haven't had time to look into this much but does anyone have an instinct as to what might be the issue? Incorrect C++ compiler? |
I think this commented out line might be the issue. Trying to compile again... |
Nope, the issue still occurs 😭 |
@thealphanerd, @rwaldron mentioned that you might have some insight here. Do you have any ideas why we'd be getting C++ compilation errors when trying to compile Node (on MIPS)? |
was 6.9.1 working? is this using the default tarball? the failing bits seem related to inspector, which there were some updates to in the release. /cc @nodejs/v8 |
No, we're only just now getting a chance to work on the upgrade to Node 6.x. The patch we received for 6.5.0 compiles correctly, but @johnnyman727 was hoping to build 6.9.2. |
I think y'all need a newer version of gcc. snprintf is a c++ 11 feature.
which version of gcc are you using?
…On Wed, Dec 7, 2016, 2:32 PM Rick Waldron ***@***.***> wrote:
was 6.9.1 working?
No, we're only just now getting a chance to work on the upgrade to Node
6.x. The patch we received for 6.5.0 compiles correctly, but @johnnyman727
<https://github.com/johnnyman727> was hoping to build 6.9.2.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#68 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAecV3x3wME1hiRVx1bxX0yrxchVohiEks5rFzQSgaJpZM4J8Jbe>
.
|
We're running with gcc 4.8.4 on our build box currently. Do you think we need v6+? |
it should be working with gcc 4.8.x
can you try adding `-std=c++11` as a compile flag?
/cc @bnoordhuis
…On Wed, Dec 7, 2016, 2:38 PM Jon ***@***.***> wrote:
We're running with gcc 4.8.4 on our build box currently. Do you think we
need v6+?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#68 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAecV9xQsZ5LCAVE37SWGo93-tL4W0gFks5rFzVmgaJpZM4J8Jbe>
.
|
It's probably a compatibility issue with the C++ standard library headers that you are compiling against because the compiler itself must be C++11-compatible if you can get to the point where InspectorProtocol.cpp is generated and compiled. If you can live without V8 inspector (DevTools) support, do |
Hi all, I tried to compile but no luck. Here the results :
Then I found this : http://src.mouf.net/ports/view/head/www/node/Makefile?rev=422711
And passed the But we have another issue because of old uclibc (I thing). Like :
We can try this mentioned patch : https://git.busybox.net/uClibc/commit/?id=6c4538905e65ceb203f59aaa9a61728e81c6bc0a Or, update a newer version. It will be so good if we update/upgrade all OpenWRT. Thats all for today, see you |
I wonder if this would result in an observable size reduction? |
@rwaldron Trying ... |
Still same
|
Untested, but you might be able to get away with |
@huseyinkozan you're a champ for that follow up ❤️ |
@bnoordhuis interesting, definitely worth a try |
https://github.com/artynet/openwrt-git/tree/openwrt-1505-setup-03/package/linino Can we combine/use that OpenWRT tree ? |
After much consideration, I think we should upgrade to Node 6.5.0 per @huseyinkozan original patch. We can work on newer 6.x.x upgrades after that. |
@rwaldron Agreed. 👍 |
I'm going to work on resolving the existing conflict and get this landed today. |
Lmk if I can help at all
…On Apr 25, 2017 10:47 AM, "Rick Waldron" ***@***.***> wrote:
I'm going to work on resolving the existing conflict and get this landed
today.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#68 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAecV8NiDmmCcqf23PBnpxZ1gZPvRE6pks5rzgeGgaJpZM4J8Jbe>
.
|
@huseyinkozan I've landed this in master |
Temporarily reverted |
Hi, I will get my Tessel few days later. I may look at again, If I have time. |
I'm open to floating a patch on node for this header.
…On May 3, 2017 12:49 PM, "Hüseyin Kozan" ***@***.***> wrote:
Hi,
I will get my Tessel few days later. I may look at again, If I have time.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#68 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAecV59c64iskcqyK_FGy8Ak0OK3vJZ4ks5r2Fu6gaJpZM4J8Jbe>
.
|
@huseyinkozan thanks, I'm in the process of getting chaos calmer upgraded as well. @MylesBorins I appreciate the offer, but I still haven't made a successful build with any patches or headers :| (Fact: that is likely because I don't know what the hell I'm doing) |
@rwaldron I see. I tried to build with these sub modules:
I got |
@huseyinkozan is this relevant: https://github.com/tessel/openwrt/pull/2/files ? |
@rwaldron I am not sure to use a not maintained lib. Also, there is a comparison: I want to try to build. Nothing to loose, rather than time : - / |
@rwaldron Added the patch you noted, but same error. Cannot find how to switch to musl. |
I'd recommend rebasing on LEDE 17.01 which switched to musl by default. It's possible to switch 15.05 to musl in the build configuration, but not well tested AFAIK. |
@kevinmehall just so I understand correctly, you're suggesting that we try to apply our existing openwrt patches to the
It appears minor, but I don't know how to resolve this:
The other two files have no issues. |
Here's the branch I'm cherry picking from: https://github.com/tessel/openwrt/commits/2017-04-26 |
Correct. The conflict is against an upstream change that appears to be intended to have the same effect as my commit. My commit can likely be dropped, but the |
Hi all, I am very sory to misguide about node versions greater than 6.5. After saw tessel/openwrt#2 I tried to build carefully and made it success with 6.10.3. I am preparing a PR. |
@rwaldron Where are we setting the version info ? I am getting undefined, like:
|
Node 6.5.0 patchs. Only
--without-intl
and some trials to enable intl.Signed the Tessel CLA.