Closed GoogleCodeExporter closed 9 years ago
This looks like it might be mixed architecture objects being linked in? I
think potentially from a leftover set of objects. I suspect the solution might
be to put the .o files in ARCH specific directories. I will attempt this and
issue a CL.
Original comment by matthewt...@gmail.com
on 1 May 2014 at 5:33
Don't we already do each build in its own folder?
Why is it trying to link objects from build/host_python-2.7.5/build/? Clearly
they will not be arm objects right?
Original comment by sbc@google.com
on 1 May 2014 at 5:39
So python-static collects objects from each of the python modules built as
separate portfiles, and then creates a unified .pexe from them all. I did not
do sufficient separation of the module object files between different
architectures; I am happy to move them to a different location, but right now
the .o files and .list files (which define the object files to use) get put
into the host_python build directory. Where should they go?
Original comment by matthewt...@gmail.com
on 1 May 2014 at 6:12
Seems to be working now.
Original comment by sbc@google.com
on 19 Jun 2014 at 6:13
Original issue reported on code.google.com by
sbc@google.com
on 1 May 2014 at 5:30