Hello,
On Wed, 15 Apr 2020, James Mills wrote:
Sorry for the bad subject line; but this is the best I could come up
with!
I am trying to understand this "invalid type" I keep getting when trying to
compile software that wants to pull in syslog.h -- e.g: libressl and most
recently I also tried util-linux.
You can see the full issue/details
here: https://github.com/prologic/ulinux/issues/24
Well, what declaration or type is on syslog.h:68 ? (Possibly look at
preprocessed output (-E) in case some macro substitution is going on).
Some background:
- ulinux is a custom Linux-based OS/Distro thing I'm trying to create :)
- It uses a busybox userland
- It ships with a tcc+musl toolchain
That sounds quite fascinating :) (Note that with musl you'll probably run
into problems with stdarg.h usages; musl want's to rely on compiler
provided builtins for those, which TCC doesn't provide, even though our
implementation is binary compatible with the psABI, ... one of those days
...)
I would appreciate some help understanding this syslog.h "invalid type"
problem. I don't quite get it :) FWIW that line references va_list which
... ah, oh, see? :) Hmm, so is TCC's stdarg.h really being included, or
is it picking up some other stdarg.h?
Ciao,
Michael.
I've been able to get other software built that wants to use valist
successfully be ensuring -I/usr/lib/tcc/include comes first by adding this
to an export CFLAGS=... in /etc/pkg.conf (pkg is what builds ports from
Pkgfile(s))
Kind regards
James
James Mills / prologic
E: prolo...@shortcircuit.net.auw: prologic.shortcircuit.net.au
_______________________________________________
Tinycc-devel mailing list
Tinycc-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/tinycc-devel
