On 21/01/20 17:04, Jan Rovins wrote:
Confirmed, I am seeing the same ninja/python issues, And also solved it with a 
symlink python3->python. I am traveling right now, so can’t post any patches.
Jan


thanks for that Jan, send them when you have time please, i'm just 'playing' at this point to see how it will go.


On Jan 20, 2020, at 11:17 PM, scsijon <[email protected]> wrote:


Next a Ninja build fail, but actually a Python problem:

AGot as far as ninja, but couldn't build ninja, tracking showed me there was no 
python executable in the installed r49128 to start with, or anywhere in the 
TOOLCHAIN/cross.build/ directories, as well as a few other related problems.

It seems with python3.7 and with no python2.x there is nothing for the link 
created to link into. I added a link from /usr/bin/python3.7 to create  the 
/usr/bin/python link.

I added this and ninja built, but there may be other problems later, i'm still 
building 0- packages at this stage.

Also, the python.conf (for python3 )has a python_postmake(), but there is no 
/lib/python to link into ?so not sure what to do here, and python2's 
python2.conf had a python_postmake() had a different export PYTHON line that 
?may be needing to add into the python.conf so both PYTHON and PYTHON3 have 
export lines.

this has yet to be sorted properly, however to test I have just copied the 
python2.conf's export line into python.conf's under the python3's one and will 
see what happens when i rebuild.



As i'm sorting each problem out, i'm doing a ./scripts/Cleanup -all and 
starting the build again, so it takes time. I will report on each problem found 
and my fix (attempt and result) so it may become boring at times, but i'm happy 
for others to jump in with sugestions and fixes if you have them.



----------------------------------------------------------- If you wish to 
unsubscribe from this mailing, send mail to
[email protected] with a subject of: unsubscribe t2





----------------------------------------------------------- If you wish to unsubscribe from this mailing, send mail to
[email protected] with a subject of: unsubscribe t2

Reply via email to