I ran sudo make tcc > build.log...hopefully that's what was meant. Results are attached to this email
On Sun, Aug 25, 2013 at 2:03 PM, Cayce Pollard <[email protected]>wrote: > Sure. What directory do the compilation logs output to? > > > > > On Sun, Aug 25, 2013 at 1:40 PM, Thomas Preud'homme <[email protected]>wrote: > >> Le dimanche 25 août 2013 13:32:55 Cayce Pollard a écrit : >> > > I have not encountered trouble on my Mac or Linux box with the >> configure >> > > script. >> > > >> > > Are *no* object files being produced at all? Does uname -m report >> i386, or >> > > one of x86_64 or amd64? I'm mostly thinking aloud, but I wonder if the >> > > build setup might get confused and assume you're building a >> > > cross-compiler. >> > > >> > > David >> > >> > To answer your two questions, *no* object files being produced at all, >> and >> > uname -m reports x86_64. >> > >> > Also, and I don't know if this is relevant but I'm grasping at straws >> > already, I'm building tcc with a toolchain built using the >> > make-standalone-toolchain.sh script from the Android NDK as I'm building >> > tcc for the Android platform (specifically my device). The toolchain >> > worked on CentOS 6.2, but because I also wanted to build gcc for Android >> > *and* because the glibc version in 6.2 is incompatible with the >> toolchain, >> > I moved to 5.9. I could quit trying to build tcc, but I'm thinking that >> > whatever is preventing tcc from building may cause the same or similar >> > problems when I start on gcc. >> >> Could you please publish the compilation logs? It might help spot some >> problem. >> >> Best regards, >> >> Thomas > > >
build.log
Description: Binary data
_______________________________________________ Tinycc-devel mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/tinycc-devel
