Hi! This week I’ve continued my work on getting Python to run. It has
\nmostly involved defining a lot of missing functions and types for
\nPython.<\/p>\n
These are mostly taken from musl libc, but some things are also just
\nimplemented using a no op.<\/p>\n
In LLVM libc there are currenly some headers without all the needed
\ndeclarations available. That will make “HAVE_*_H” configuration tests
\npass, but then fail later. For some of these cases I simply did
\n‘#undef’ and hoped the functionality wasn’t needed.<\/p>\n
My current plan is to just get Python to build, and then go back to
\nfix things properly, within reason.<\/p>\n
I also found a bug in LLVM libc where the TableGen<\/a> specifications for At the end of the week I went back to fix an error I got while setting Next week I aim to be finished with Python, and in that case I’ll Hi! This week I’ve continued my work on getting Python to run. It has mostly involved defining a lot of missing functions and types for Python. These are mostly taken from musl libc, but some things are also just implemented … Continue reading
\ntruncate and ftruncate had mixed up argument types. Because the
\nlibc headers are generated from these specifications, the unistd.h
\nheader had incorrect declarations for these functions. As this did not
\nadd any new things, and was easy to implement, I got it committed into
\nupstream LLVM instead of keeping it locally like the other fixes. Sam
\nsuggested that if I get stuck on something and want to do something
\nelse for I while I could go through the spec files and look for errors
\nsimilar to this (truncate commit on phabricator<\/a>).<\/p>\n
\nup LLVM libc, that being an error related to PRId64 format string. Sam
\nsuggested that I could use this to learn how to use cvise, which I
\nwill do next week.<\/p>\n
\ncontinue with getting Crossdev to work with LLVM by making it able to
\ncompile compiler-rt for non-host triples.<\/p>\n","protected":false},"excerpt":{"rendered":"