revert 'no-libtcc1' feature
commitaed5cd0ce9a2763ebe4c326a63c1ec22c54ece96
authorgrischka <grischka>
Thu, 17 Sep 2020 08:32:48 +0000 (17 10:32 +0200)
committergrischka <grischka>
Thu, 17 Sep 2020 18:57:21 +0000 (17 20:57 +0200)
tree97e8ea58c287220903cfefc8c8eea1937b02389d
parent4cd6298f9dceabcb109270c17ddff6c0e2df661d
revert 'no-libtcc1' feature

from 43ae3503904d42a171305b2708f9fd1d37a352ea
and a3578379fbd36b663032869a15a0c28c32be4cf6

Sorry, but this feature appears to be rather a personal
experiment than generically interesting for other people.
Also those "other people" always have some interest in
TCC staying simple.

One can still avoid the startup code from libtcc1.a simply
by providing __start explicitly.

While at it: Tidy tccpe.c:pe_add_runtime(), somewhat.
tccelf.c
tccpe.c