|
|
Tcc won't link libraries.
I installed tcc (tiny C compiler) on my work computer, and it's fine.
I installed the same version on a notebook, and it will compile Ansi C
programs, but it won't link the Windows libraries. It doesn't give an
error message. The executable just fails to appear. The dlls are
there, and I can't find any difference between the notebook and the
big machine that would account for the problem.
Anyone any ideas?
|
|
0
|
|
|
|
Reply
|
malcolm.mclean5 (725)
|
6/18/2011 12:46:33 PM |
|
On Jun 18, 8:46=A0pm, Malcolm McLean <malcolm.mcle...@btinternet.com>
wrote:
> I installed tcc (tiny C compiler) on my work computer, and it's fine.
>
> I installed the same version on a notebook, and it will compile Ansi C
> programs, but it won't link the Windows libraries. It doesn't give an
> error message. The executable just fails to appear. The dlls are
> there, and I can't find any difference between the notebook and the
> big machine that would account for the problem.
I don't have Windows now. But I tried compiling a small piece of C
with pthread calls, and tried scripting the same piece against TCC.
Both work fine.
$ tcc -v
tcc version 0.9.25
$
$ ls
a.c
$ tcc a.c -lpthread
$ ls
a.c a.out
$ ./a.out
In main: creating thread 0
-cut-
Hello World! It's me, thread #0!
$
$ ls
a.c
$
$ tcc -lpthread -run a.c
In main: creating thread 0
-cut-Hello World! It's me, thread #1!
Hello World! It's me, thread #0!
$
|
|
0
|
|
|
|
Reply
|
lovecreatesbeauty (723)
|
6/18/2011 2:48:31 PM
|
|
On Jun 18, 8:46=A0pm, Malcolm McLean <malcolm.mcle...@btinternet.com>
wrote:
> I can't find any difference between the notebook and the
> big machine that would account for the problem.
Maybe the difference is one runs Windows and the other doesn't :)
|
|
0
|
|
|
|
Reply
|
lovecreatesbeauty (723)
|
6/18/2011 2:55:41 PM
|
|
On 6/18/2011 7:46 AM, Malcolm McLean wrote:
> I installed tcc (tiny C compiler) on my work computer, and it's fine.
>
> I installed the same version on a notebook, and it will compile Ansi C
> programs, but it won't link the Windows libraries. It doesn't give an
> error message. The executable just fails to appear. The dlls are
> there, and I can't find any difference between the notebook and the
> big machine that would account for the problem.
>
> Anyone any ideas?
You could check to see if it's possible to file a bug report.
You could observe what the compiler is doing by using Microsoft's
Sysinternals' Process Monitor logging application. Perhaps an error
observed close to the end of the logging can yield some clues.
|
|
0
|
|
|
|
Reply
|
sha0.miller (876)
|
6/19/2011 10:42:29 PM
|
|
Il 18/06/2011 16:55, lovecreatesbeauty ha scritto:
> On Jun 18, 8:46 pm, Malcolm McLean<malcolm.mcle...@btinternet.com>
> wrote:
>> I can't find any difference between the notebook and the
>> big machine that would account for the problem.
>
> Maybe the difference is one runs Windows and the other doesn't :)
If that is the case, try reading the limitations in the win32 version
(browse online at http://repo.or.cz/w/tinycc.git, and look at
win32/tcc_win32.txt)
good luck
|
|
0
|
|
|
|
Reply
|
lory.fulgi (9)
|
6/21/2011 7:36:50 PM
|
|
|
4 Replies
52 Views
(page loaded in 0.114 seconds)
|
|
|
|
|
|
|
|
|