Hello All,

I am attempting to build the release version (release_0_9_27) of tinycc
on a FreeBSD 15-CURRENT machine and am getting the following error:

gmake[1]: Entering directory '/home/${USER}/tinycc/lib'
../tcc -c bcheck.c -o bcheck.o -B..
In file included from bcheck.c:20:
In file included from /usr/include/stdlib.h:37:
/usr/include/sys/_types.h:58: error: #error unsupported long size
gmake[1]: *** [Makefile:64: bcheck.o] Error 1
gmake[1]: Leaving directory '/home/${USER}/tinycc/lib'
gmake: *** [Makefile:230: libtcc1.a] Error 2

I have been able to build the most recent commit without issue, but have
not been able to figure out what the difference is that is causing this
error on one, but not the other. Has anyone built this release on a
recent version of FreeBSD? If so, were any code changes required to get
it to build? I am also including my config.mak and config.h files in the
event that something in one of those files is insightful into the
problem, and thank you (all) in advance for any help or guidance on this
issue.
# Automatically generated by configure - do not modify
prefix=/usr/local
bindir=$(DESTDIR)/usr/local/bin
tccdir=$(DESTDIR)/usr/local/lib/tcc
libdir=$(DESTDIR)/usr/local/lib
includedir=$(DESTDIR)/usr/local/include
mandir=$(DESTDIR)/usr/local/share/man
infodir=$(DESTDIR)/usr/local/share/info
docdir=$(DESTDIR)/usr/local/share/doc
CC=clang
GCC_MAJOR=4
GCC_MINOR=2
AR=ar
STRIP=strip -s -R .comment -R .note
CFLAGS=-Wall -g -O2 -Wdeclaration-after-statement -fno-strict-aliasing 
-fheinous-gnu-extensions -Wno-pointer-sign -Wno-sign-compare -Wno-unused-result 
-Wno-string-plus-int
LDFLAGS=
LIBSUF=.a
EXESUF=
DLLSUF=.so
ARCH=x86_64
TARGETOS=FreeBSD
CONFIG_ldl=no
VERSION = 0.9.27
TOPSRC=$(TOP)
/* Automatically generated by configure - do not modify */
#ifndef CONFIG_TCCDIR
# define CONFIG_TCCDIR "/usr/local/lib/tcc"
#endif
#define TCC_VERSION "0.9.27"
_______________________________________________
Tinycc-devel mailing list
Tinycc-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/tinycc-devel

Reply via email to