when I pass in the --prefix=... to ./configure, it seems that the 'make
install' part uses that, while the 'make' build of tcc itself uses
/usr/local/
 
thus, the binary cannot find its installed headers, etc.
 
this changed recently, and used to work correctly.
 
Below is older good version log vs. newer bad recent version which did not
work correctly (or at least as expected).
 
Seems that paths in tcc.h are not adjusted from the ./configure ???
 
This is on cygwin.
 
Thanks,
 
John Refling
 
 

######################################  GOOD
##########################################
 
unzip -q tinycc-release_0_9_27.zip 
 
cd tinycc-release_0_9_27
 
./configure --prefix=/usr/tcc --bindir=/bin
 
Binary directory    /bin
TinyCC directory    /usr/tcc
Library directory   /usr/tcc/libtcc
Doc directory       /usr/tcc/doc
Source path         .
C compiler          gcc (10.2)
Target OS           CYGWIN_NT-6.1
CPU                 x86_64
Config              WIN32
Creating config.mak and config.h
 
make
.
.
.
 
./tcc -vv
 
tcc version 0.9.27 (x86_64 Windows)
install: /usr/tcc
include:
  /usr/tcc/include
  /usr/tcc/include/winapi
libraries:
  /usr/tcc/lib
libtcc1:
  /usr/tcc/libtcc1.a
 
######################################  BAD
##########################################
 
unzip -q tinycc-mob.zip 
 
cd tinycc-mob/
 
./configure --prefix=/usr/tcc --bindir=/bin
 
Binary directory    /bin
TinyCC directory    /usr/tcc
Library directory   /usr/tcc/libtcc
Doc directory       /usr/tcc/doc
Source path         .
C compiler          gcc (10.2)
Target OS           WIN32
CPU                 x86_64
Config              WIN32
Creating config.mak and config.h
 
make
.
.
.
 
./tcc -vv
 
tcc version 0.9.27 (x86_64 Windows)
install: /usr/local/lib/tcc
include:
  /usr/local/lib/tcc/include
  /usr/local/lib/tcc/include/winapi
libraries:
  /usr/local/lib/tcc/lib
libtcc1:
  /usr/local/lib/tcc/lib/libtcc1.a
 
 
_______________________________________________
Tinycc-devel mailing list
[email protected]
https://lists.nongnu.org/mailman/listinfo/tinycc-devel

Reply via email to