Jung-uk Kim
2017-Apr-26 16:34 UTC
GCC + FreeBSD 11.0 Stable - stat.h does not have vm_ooffset_t definition
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 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 Jung-uk Kim -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 488 bytes Desc: OpenPGP digital signature URL: <http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20170426/24d0593a/attachment.sig>
Patrick Powell
2017-Apr-27 16:45 UTC
GCC + FreeBSD 11.0 Stable - stat.h does not have vm_ooffset_t definition
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 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 > > Jung-uk Kim >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. -- Patrick Powell Astart Technologies papowell at astart.com 1530 Jamacha Rd, Suite X Network and System San Diego, CA 92019 Consulting Cell 858-518-7581 FAX 858-751-2435 Web: papowell at astart dot com