Date: Sat, 29 Apr 2017 19:00:11 +0200 (CEST) From: Gerald Pfeifer <gerald@pfeifer.com> To: Jung-uk Kim <jkim@FreeBSD.org> Cc: papowell@astart.com, freebsd-stable@freebsd.org Subject: Re: GCC + FreeBSD 11.0 Stable - stat.h does not have vm_ooffset_t definition Message-ID: <alpine.LSU.2.21.1704291846170.2928@anthias.pfeifer.com> In-Reply-To: <22bfc9eb-f037-cb1e-931f-a995e98093e2@FreeBSD.org> 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> <22bfc9eb-f037-cb1e-931f-a995e98093e2@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 27 Apr 2017, Jung-uk Kim wrote: >>>>>> 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 create a >>>>>> modified set of include files from the system (default?) include files >>>>>> (/usr/include). However, when the modified /usr/include/sys/types.h >>>>>> file is created, the typedef for vm_ooffset_t is modified, and there 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. >>>>> >>>>> https://lists.freebsd.org/pipermail/freebsd-current/2017-February/064937.html >>>> Does this mean that the GCC port/package needs to be updated? If so, >>>> should I file a PR report on this issue? >>>> I (temporarily) fixed this problem by hand editting the modified types.h >>>> file and things seem to work. >>> I already wrote a patch (attached). :-) > If the maintainer (gerald) approves. CC'd. Thanks for bringing this to my attention. Can you please help me understand why this is necessary? If the port/package is builts from scratch, does this trigger the problem? Or is this only a question of an old package running on that new version of FreeBSD after these changes? (I am wondering whether just forcing a rebuild of that package is not going to have the same effect?) Gerald
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.LSU.2.21.1704291846170.2928>