Date: Tue, 04 Aug 2015 01:23:57 +0200 From: Carlos Jacobo Puga Medina <cpm@fbsd.es> To: Jung-uk Kim <jkim@FreeBSD.org>, "freebsd-ports@freebsd.org" <freebsd-ports@freebsd.org> Subject: Re: lang/tcc unusable Message-ID: <1438644237.7343.13.camel@fbsd.es> In-Reply-To: <55BFEAAA.4070008@FreeBSD.org> References: <1438633579.6572.13.camel@fbsd.es> <55BFD033.8070507@FreeBSD.org> <1438634467.7343.2.camel@fbsd.es> <55BFDCA0.8040006@FreeBSD.org> <1438638022.7343.7.camel@fbsd.es> <55BFEAAA.4070008@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--=-uj44wW4OmCha03GDMYWU
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
El lun, 03-08-2015 a las 18:26 -0400, Jung-uk Kim escribi=C3=B3:
> On 08/03/2015 17:40, Carlos Jacobo Puga Medina wrote:
> > El lun, 03-08-2015 a las 17:26 -0400, Jung-uk Kim escribi=C3=B3:
> > > On 08/03/2015 16:41, Carlos Jacobo Puga Medina wrote:
> > > > El lun, 03-08-2015 a las 16:33 -0400, Jung-uk Kim escribi=C3=B3:
> > > >=20
> > > > Hi Jung-uk,
> > > > > On 08/03/2015 16:26, Carlos Jacobo Puga Medina wrote:
> > > > > > Hi people,
> > > > > >=20
> > > > > > Recently I added amd64 support to TinyCC, but I encounter
> > > > > > the following problem trying to compile a simple code.
> > > > > >=20
> > > > > > #include <stdio.h>
> > > > > >=20
> > > > > > int main(){ printf("hello, world!\n); return 0; }
> > > > > >=20
> > > > > > % tcc -o hello hello.c In file included from hello.c:1:=20
> > > > > > /usr/include/stdio.h:63: error: ';' expected (got
> > > > > > "va_list")
> > > > > >=20
> > > > > > I guess that some change introduced in 'stdio.h' causes
> > > > > > this weird behaviour. Last time that TCC worked fine was on
> > > > > > FreeBSD 9.1 -RELEASE/i386.
> > > > > >=20
> > > > > > Also I reported this problem in the tinycc-devel mailing
> > > > > > list [1]
> > > > > >=20
> > > > > > Any thoughts?
> > > > >=20
> > > > > I haven't tried tcc but '"' is missing for the printf().
> > > >=20
> > > > Yes, it was a typo here :)
> > >=20
> > > It seems it's a known tcc bug:
> > >=20
> > > http://savannah.nongnu.org/bugs/?30966
> > >=20
> >=20
> > Is there something that we can do about it?
> >=20
> > Thanks for pointing me, jkim@
>=20
> It seems there is no easy way to fix this problem without touching=20
> src
> tree, e.g.,
>=20
> --- sys/x86/include/_types.h (revision 286256)
> +++ sys/x86/include/_types.h (working copy)
> @@ -152,7 +152,7 @@
> */
> #ifdef __GNUCLIKE_BUILTIN_VARARGS
> typedef __builtin_va_list __va_list; /*=20
> internally known to gcc */
> -#elif defined(lint)
> +#elif defined(__TINYC__) || defined(lint)
> typedef char * __va_list; /*=20
> pretend */
> #endif
> #if defined(__GNUC_VA_LIST_COMPATIBILITY) &&=20
> !defined(__GNUC_VA_LIST) \
>=20
If you need doing some changes into the src tree. So, what do you
recommend in such case?=20
Would it be much trouble add the necessary changes to run TCC again?
Furthermore, TinyCC developer has ignored this issue completely.
Cheers,
--
Carlos Jacobo Puga Medina <cpm@fbsd.es>
PGP fingerprint =3D C60E 9497 5302 793B CC2D BB89 A1F3 5D66 E6D0 5453
--=-uj44wW4OmCha03GDMYWU
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part
Content-Transfer-Encoding: 7bit
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQEcBAABCAAGBQJVv/gOAAoJEKHzXWbm0FRTzNQH/1yuKLlyuPg/WqO91+XOh+Qg
uwDVHDiDljlp7jcs53wwJnDnzUpR3xKAWrTDvzss8q/dKFLhWzy4YwUbU1DnDlxH
R4tQqpHyd3TcfSoE3L2ioWdzSPpgFo03xxjllkYJ3/BlCtF3q1+AuSbtQnQRm2ut
ARDh9AzRvSCEGW6Ydk6ULXt0SCDwgVhOtkJ3ia+h1N4JkU/EbvAKkprbfw24KRp4
EM5aXkVmTBoVSTwr0CWcUdVebir7wYivYZC6Wi6w7g+kfy6EXydgDedGAhLwCJSW
fqtlcPxn9RlzC5BS0QT8/E4f38ONDY9wzfwG/3BqROAiOYpkKasFhMTTG7/mnk8=
=OC4d
-----END PGP SIGNATURE-----
--=-uj44wW4OmCha03GDMYWU--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1438644237.7343.13.camel>