From owner-freebsd-ports@freebsd.org Tue Aug 4 00:22:48 2015 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5407F9B2C67 for ; Tue, 4 Aug 2015 00:22:48 +0000 (UTC) (envelope-from jkim@FreeBSD.org) Received: from mx2.freebsd.org (mx2.freebsd.org [8.8.178.116]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mx2.freebsd.org", Issuer "Gandi Standard SSL CA 2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 433931057 for ; Tue, 4 Aug 2015 00:22:48 +0000 (UTC) (envelope-from jkim@FreeBSD.org) Received: from hammer.pct.niksun.com (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx2.freebsd.org (Postfix) with ESMTP id E131921B5; Tue, 4 Aug 2015 00:22:47 +0000 (UTC) (envelope-from jkim@FreeBSD.org) Subject: Re: lang/tcc unusable To: Carlos Jacobo Puga Medina , "freebsd-ports@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> <1438644237.7343.13.camel@fbsd.es> From: Jung-uk Kim X-Enigmail-Draft-Status: N1110 Message-ID: <55C005D7.3050103@FreeBSD.org> Date: Mon, 3 Aug 2015 20:22:47 -0400 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.1.0 MIME-Version: 1.0 In-Reply-To: <1438644237.7343.13.camel@fbsd.es> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Aug 2015 00:22:48 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 08/03/2015 19:23, Carlos Jacobo Puga Medina wrote: > El lun, 03-08-2015 a las 18:26 -0400, Jung-uk Kim escribió: >> 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ó: >>>> 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ó: >>>>> >>>>> Hi Jung-uk, >>>>>> On 08/03/2015 16:26, Carlos Jacobo Puga Medina wrote: >>>>>>> Hi people, >>>>>>> >>>>>>> Recently I added amd64 support to TinyCC, but I >>>>>>> encounter the following problem trying to compile a >>>>>>> simple code. >>>>>>> >>>>>>> #include >>>>>>> >>>>>>> int main(){ printf("hello, world!\n); return 0; } >>>>>>> >>>>>>> % tcc -o hello hello.c In file included from >>>>>>> hello.c:1: /usr/include/stdio.h:63: error: ';' expected >>>>>>> (got "va_list") >>>>>>> >>>>>>> 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. >>>>>>> >>>>>>> Also I reported this problem in the tinycc-devel >>>>>>> mailing list [1] >>>>>>> >>>>>>> Any thoughts? >>>>>> >>>>>> I haven't tried tcc but '"' is missing for the printf(). >>>>> >>>>> Yes, it was a typo here :) >>>> >>>> It seems it's a known tcc bug: >>>> >>>> http://savannah.nongnu.org/bugs/?30966 >>>> >>> >>> Is there something that we can do about it? >>> >>> Thanks for pointing me, jkim@ >> >> It seems there is no easy way to fix this problem without >> touching src tree, e.g., >> >> --- 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; /* internally known to gcc */ -#elif defined(lint) >> +#elif defined(__TINYC__) || defined(lint) typedef char * >> __va_list; /* pretend */ #endif #if >> defined(__GNUC_VA_LIST_COMPATIBILITY) && >> !defined(__GNUC_VA_LIST) \ >> > > If you need doing some changes into the src tree. https://svnweb.freebsd.org/changeset/base/286265 > So, what do you recommend in such case? Would it be much trouble > add the necessary changes to run TCC again? Furthermore, TinyCC > developer has ignored this issue completely. The only hack I see is defining __va_list as a macro from libtcc.c but it is ugly. Jung-uk Kim -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJVwAXXAAoJEHyflib82/FGLOwH/3HxMqLqt/G6thF5DqTQsqA+ PoHwp3Qdvkwx9Z/LjjLQlyrtZMSXSBfKv0IisZlblaFqkV0p8rnC/X+hpHhtTm4I 6inQyI36zwCRr3aD31hvRWpeYpjjZSJotsTbvmb4+cvjw4nSyJ43lBcomAyGx9dW 0lDrxVDzUvyVpBqYMGOgp6IvaDpyo2YF8yanpKD1vksdzDi2KvyvkRQx9/3VLu8A OJla4pluo2Q83wQmRZqJZIu5eqgYQCdI/2ETiV4bVWLarQRkdwWHgjwt2LqQEciE ZNIGKhFUBDXhXjuw0ND+UofQrt9IZtmNRRYX6LoaDuTdhazlDQKsq/opCHGYVsI= =bbog -----END PGP SIGNATURE-----