Have you consider that compiler searches its own header path and header files have environment switches.
Make it clear where “mexPrintf” is defined and why it is not effective. _____ From: [email protected] [mailto:[email protected]] On Behalf Of Markus Bergholz Sent: Friday, June 27, 2014 1:16 AM To: [email protected] Subject: Re: [Tinycc-devel] Crosscompiling On Tue, Jun 24, 2014 at 11:25 PM, grischka <[email protected]> wrote: Markus Bergholz wrote: I'd tried to compile tcc itself with build_cross="yes" and tried ./x86_64-win32-tcc -nostdinc -I /usr/x86_64-w64-mingw32/include/ ../helloworld.c -o helloworld-gcc.exe [...] /usr/x86_64-w64-mingw32/include//vadefs.h:33: error: #error VARARGS not implemented for this compiler If you love problems I know a lot of options that you can try. ;) Otherwise ./configure --enabie-cross && make && make install cd win32/examples x86_64-win32-tcc -v hello_win.c did work with 0.9.26. And still should if it hasn't been broken. --gr Indeed, this works fine for hello_win.c But the tcc crosscompiler said that mexprintf is undefined $ tcc -v -I /usr/include/octave-3.8.1/octave/ -shared mexample.c -o mexample.mex tcc version 0.9.26 (x86-64 Linux) -> mexample.c <- mexample.mex $ x86_64-win32-tcc -v -I /usr/include/octave-3.8.1/octave/ -shared mexample.c -o mexample.mex tcc version 0.9.26 (x86-64 Win64) -> mexample.c tcc: error: undefined symbol 'mexPrintf' $ x86_64-win32-tcc -v -I ~/R2013a/extern/include/ -shared mexample.c -o mexample.mex tcc version 0.9.26 (x86-64 Win64) -> mexample.c tcc: error: undefined symbol 'mexPrintf' And ideas why this just work with native tcc but not with tcc crosscompiler? _______________________________________________ Tinycc-devel mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/tinycc-devel -- icq: 167498924 XMPP|Jabber: [email protected]
_______________________________________________ Tinycc-devel mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/tinycc-devel
