Glibc is one big gnu ew, no wonder there are issues. Still, what exactly is wrong? Do you need to use glibc in particular?
2018-01-11 16:30 GMT+01:00 lukáš Hozda <luk.ho...@gmail.com>: > Glibc is one big gnu ew, no wonder there are issues. Still, what exactly is > wrong? Do you need to use glibc in particular? > > Dne 11. 1. 2018 16:04 napsal uživatel "k.suz...@aist.go.jp" > <k.suz...@aist.go.jp>: > >> Dear, >> >> Can I build stali with another libc? The old stali seems to be built by >> uClibc. >> https://chemnitzer.linux-tage.de/2010/vortraege/shortpaper/308_stali.pdf >> https://dl.suckless.org/stali/clt2010/stali.html >> Should I use old stali source code? >> https://git.sta.li/src.old/ >> >> P.S. >> I just tried to build the current stali with the normal glibc on ARM-QEMU >> with the following "config.mk". >> I could not build because include files have type conflicts. >> >> --- config.mk ---------------------------------------------------- >> # stali version >> VERSION = 0.0 >> >> # define target and target rootfs >> HOST_ARCH = x86_64-linux-glibc >> >> TARGET_ARCH = arm-linux-glibc >> OBJTYPE = arm >> TARGET_LONG = 4 >> SYS = sys.pi >> DESTDIR = $(HOME)/rootfs-pi >> >> PREFIX = / >> MANPREFIX = $(PREFIX)/share/man >> >> >> M4 = m4 >> HOSTCC = /usr/bin/gcc >> CC = /usr/bin/gcc >> CXX = /usr/bin/g++ >> AS = /usr/bin/as >> LD = $(CC) >> >> YACC = $(ROOT)/bin/hbase/yacc/yacc >> HOSTAR = /usr/bin/ar >> AR = /usr/bin/ar >> HOSTRANLIB = /usr/bin/ranlib >> RANLIB = /usr/bin/ranlib >> >> HOSTCPPFLAGS = -D_POSIX_SOURCE -D__stali__ -DTARGET_LONG=$(TARGET_LONG) >> CPPFLAGS = $(HOSTCPPFLAGS) >> HOSTCFLAGS = -I/usr/include >> CFLAGS = -I/usr/include >> CXXFLAGS = -I/usr/include >> HOSTLDFLAGS = -static >> LDFLAGS = $(HOSTLDFLAGS) >> --- config.mk ---------------------------------------------------- >> >> ------ >> suzaki >> >> >> >
