Skip to content
This repository has been archived by the owner on Apr 22, 2023. It is now read-only.

build error, already fix by hand, there should be some configure/makefile generate problem, need help to allocate/fix #25911

Closed
aratic opened this issue Aug 30, 2015 · 2 comments

Comments

@aratic
Copy link

aratic commented Aug 30, 2015

environment: virtual machine, Gentoo 64 bits, and python3.3/2.7

problem 1, system use python3.3 as default and think ''' block comments invalid, not a issse
problem 2, when python2.7 ./configure done, I met some "TypeError: object of type 'filter' has no len()" during make, and i believe this is still a python2/3 problem, i grep out that among following makefiles, some were automatically geneated as python2.7, but some still left as python, which evokes python3,

./config.mk: ./* use python2.7, fine /
./out/deps/v8/tools/gyp/postmortem-metadata.target.mk /
use python, not ok /
./out/deps/v8/tools/gyp/js2c.target.mk /
use python, not ok /
./out/node_js2c.host.mk /
use python2.7, fine */

i fix these makefiles by hand and pass the build, but it seems they were automatically generated or fetch(svn) from somewhere else, need help

@ChALkeR
Copy link
Member

ChALkeR commented Sep 14, 2015

nodejs/node#418
nodejs/node#2735
Especially, nodejs/node#2735 (comment).

Hope this helps. If it doesn't — report an issue in nodejs/node repository, this is an archive.

@ChALkeR ChALkeR closed this as completed Sep 14, 2015
@aratic
Copy link
Author

aratic commented Sep 14, 2015

as the nodejs/node#418 says this seems been hardcoded somewhere else.. whatever.
Thx for organizing and the reference,~

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants