Date: Thu, 27 Apr 2017 19:14:13 -0400 From: Jung-uk Kim <jkim@FreeBSD.org> To: papowell@astart.com, freebsd-stable@freebsd.org Cc: gerald@freebsd.org Subject: Re: GCC + FreeBSD 11.0 Stable - stat.h does not have vm_ooffset_t definition Message-ID: <22bfc9eb-f037-cb1e-931f-a995e98093e2@FreeBSD.org> In-Reply-To: <fb7749f8-193a-2cdc-db8f-9ca046a0b94e@astart.com> References: <8316fd8e-056d-32a1-1e59-414269476190@astart.com> <95c6f08e-0cf7-f0f3-8b19-29e03b3f4f96@FreeBSD.org> <39149f1c-d939-5c60-a0c3-ab76fa0f750b@astart.com> <f264ebcc-4cd4-4541-f19d-227cde74b3ba@FreeBSD.org> <fb7749f8-193a-2cdc-db8f-9ca046a0b94e@astart.com>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --igvH66wDinfCqTTIS4iAaubQgrdXMpe7f Content-Type: multipart/mixed; boundary="WqsKBVEBa5CGRNq6dhbRPIU4AVTHBikcJ"; protected-headers="v1" From: Jung-uk Kim <jkim@FreeBSD.org> To: papowell@astart.com, freebsd-stable@freebsd.org Cc: gerald@freebsd.org Message-ID: <22bfc9eb-f037-cb1e-931f-a995e98093e2@FreeBSD.org> Subject: Re: GCC + FreeBSD 11.0 Stable - stat.h does not have vm_ooffset_t definition References: <8316fd8e-056d-32a1-1e59-414269476190@astart.com> <95c6f08e-0cf7-f0f3-8b19-29e03b3f4f96@FreeBSD.org> <39149f1c-d939-5c60-a0c3-ab76fa0f750b@astart.com> <f264ebcc-4cd4-4541-f19d-227cde74b3ba@FreeBSD.org> <fb7749f8-193a-2cdc-db8f-9ca046a0b94e@astart.com> In-Reply-To: <fb7749f8-193a-2cdc-db8f-9ca046a0b94e@astart.com> --WqsKBVEBa5CGRNq6dhbRPIU4AVTHBikcJ Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable On 04/27/2017 19:07, Patrick Powell wrote: > On 04/27/17 13:59, Jung-uk Kim wrote: >> On 04/27/2017 12:45, Patrick Powell wrote: >>> On 04/26/17 09:34, Jung-uk Kim wrote: >>>> On 04/26/2017 10:14, Patrick Powell wrote: >>>>> First: a big thank-you to the support/fixit people for all of their= work! >>>>> >>>>> I was doing some testing using FreeBSD 11.0-STABLE and some of my >>>>> configure scripts died. However, they were working fine on FreeBSD= 11.0 >>>>> RELEASE. >>>>> >>>>> I found the problem, but I do not know how to resolve this. When = you >>>>> install the GCC compiler from the PKG repository it appears to crea= te a >>>>> modified set of include files from the system (default?) include fi= les >>>>> (/usr/include). However, when the modified /usr/include/sys/types.= h >>>>> file is created, the typedef for vm_ooffset_t is modified, and the= re is >>>>> no reference to __vm_ooffset_t that the compiler can resolve. >>>>> >>>>> < typedef __int64_t vm_ooffset_t; >>>>> --- >>>>>> typedef __vm_ooffset_t vm_ooffset_t; >>>> ... >>>> You have to rebuild lang/gcc from the ports tree to fix this problem= =2E >>>> >>>> https://lists.freebsd.org/pipermail/freebsd-current/2017-February/06= 4937.html >>>> >>>> Jung-uk Kim >>>> >>> Does this mean that the GCC port/package needs to be updated? If so,= =20 >>> should I file a PR report on this issue? >>> I (temporarily) fixed this problem by hand editting the modified type= s.h >>> file and things seem to work. >> I already wrote a patch (attached). :-) >> >> Jung-uk Kim > Will the GCC port be updated with this patch? If the maintainer (gerald) approves. CC'd. > Any action needed by me on this? No, thanks. :-) Jung-uk Kim --WqsKBVEBa5CGRNq6dhbRPIU4AVTHBikcJ-- --igvH66wDinfCqTTIS4iAaubQgrdXMpe7f Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEEl1bqgKaRyqfWXu/CfJ+WJvzb8UYFAlkCe0UACgkQfJ+WJvzb 8Ubv2gf+MvRBxL58pmee/2GTCb/6w5//Tb7GLl32DkiC07oHxOwMlzyppxYRrRGF xAGAMeOIxXceNDyXd9Ag3RCUALhIxwmLzEUUI0hBpxGIk239kuGccc/LlCMFYHrR fZG0URO2HQIV63jcoGjSGwTWQKSqixLJqMBPls8KiBv2RsuyX3uPgMikHyjiWhzG Bb1i9eEVacYP9t1AXxBKs5LiBsbWzzE2GJai3heBhXCMcOBrifZMCxjK3tn7daLa GzYiGhc8DzrdPBm2NXWgPJneYPGY886HquTtD6peE+Vg1aLlmzM9YLtur1fu/pxr Wu6eJ7h5SkB1Uqqnf0ZYVbgs7L415w== =NTN3 -----END PGP SIGNATURE----- --igvH66wDinfCqTTIS4iAaubQgrdXMpe7f--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?22bfc9eb-f037-cb1e-931f-a995e98093e2>