Re: lang/gcc* package builds vs. release/11.0.1/ and the future release/11.1.0 because of vm_ooffset_t and vm_pindex_t changes and how the lang/gcc* work
ows categories for builds for 8.4 9.3 10.1 10.3 11.0 head (Nothing for stable/*/ .) But the 10.3 rows show no package builds. I would guess that they start once 10.1 stops (approximately). So it may be that 11.1 will not get package builds until 11.0 stops (approximately). If so unless lang/gcc* are changed to bootstrap differently they will configure to match release/11.0.1/ and will not be compatible with the vm_ooffset_t and vm_pindex_t changes in stable/11/ and release/11.1.0/ . But as I understand updating how the lang/gcc* builds work to remove such dependencies is under investigation. I do not know any timing relative to release/11.1.0/ if my understanding is right. Until then (if I was right): Unless there are separate packages made for targeting release/11.0.1/ vs. release/11.1.0/ it is not obvious when lang/gcc* packages will be generally compatible with various folks choices about what to install as the system version within the release/11.*/ and stable/11/ family. This would likely be true even if they were built on release/11.1.0/ : then release/11.0.1/ likely would have compatibility problems. The ABI versioning does not cover the specific issues involved based on how vm_ooffset_t and vm_pindex_t were changed and what the lang/gcc* builds do relative to such changes. Yet there is incompatibility for some fairly-significant-usage ports. Aspect #2: stable/10/ and release/10.4.0/ Just covered for completeness: I do not see a MFC of -r313194 to stable/10/ : its sys/sys/types.h dates back to 2015-Oct-10. So it looks like 10.x has a permanent difference in this area: 10.x continues to get separate lang/gcc* package builds from 11.x and later. No problem for this context as far as I know. Note: To simplify I choose to not be explicit about what authors wrote what original text. If that becomes an issue, it is correctable. Blame me for any errors in the above. === Mark Millard markmi at dsl-only.net ___ freebsd-po...@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" -- Patrick Powell Astart Technologies papow...@astart.com1530 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 ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: GCC + FreeBSD 11.0 Stable - stat.h does not have vm_ooffset_t definition
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 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. I already wrote a patch (attached). :-) Jung-uk Kim Will the GCC port be updated with this patch? Any action needed by me on this? -- Patrick Powell Astart Technologies papow...@astart.com1530 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 ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: 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 papow...@astart.com1530 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 ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
GCC + FreeBSD 11.0 Stable - stat.h does not have vm_ooffset_t definition
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; I suspect that this change from __int64_t to __vm_offset_t is the cause of the problem. This editting (?) appears to be done by 'fixincludes' (as noted in the README files in the /usr/local/lib/gcc5/gcc/x86_64-portbld-freebsd11.0/5.4.0/include-fixed directory. Details: Configuration: FreeBSD test11snapshot 11.0-STABLE FreeBSD 11.0-STABLE #0 r317153: Thu Apr 20 05:43:02 UTC 2017 r...@releng2.nyi.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64 p#> pkg which /usr/local/bin/gcc /usr/local/bin/gcc was installed by package gcc-5.4.0_1 Test File: conftest.c /* confdefs.h */ #define PACKAGE_NAME "" #define PACKAGE_TARNAME "" #define PACKAGE_VERSION "" #define PACKAGE_STRING "" #define PACKAGE_BUGREPORT "" #define PACKAGE_URL "" #define PACKAGE "FEPT" #define VERSION "7.0.8" #define STDC_HEADERS 1 /* end confdefs.h. */ #include #ifdef HAVE_SYS_TYPES_H # include #endif #ifdef HAVE_SYS_STAT_H # include #endif #ifdef STDC_HEADERS # include # include #else # ifdef HAVE_STDLIB_H # include # endif #endif #ifdef HAVE_STRING_H # if !defined STDC_HEADERS && defined HAVE_MEMORY_H # include # endif # include #endif #ifdef HAVE_STRINGS_H # include #endif #ifdef HAVE_INTTYPES_H # include #endif #ifdef HAVE_STDINT_H # include #endif #ifdef HAVE_UNISTD_H # include #endif #include Compile: #> gcc -c -g -02 conftest.c In file included from conftest.c:46:0: /usr/local/lib/gcc5/gcc/x86_64-portbld-freebsd11.0/5.4.0/include-fixed/sys/types.h:266:9: error: unknown type name '__vm_ooffset_t' typedef __vm_ooffset_t vm_ooffset_t; ^ /usr/local/lib/gcc5/gcc/x86_64-portbld-freebsd11.0/5.4.0/include-fixed/sys/types.h:268:9: error: unknown type name '__vm_pindex_t' typedef __vm_pindex_t vm_pindex_t; ^ root@test11snapshot:/usr/include # diff sys/types.h /usr/local/lib/gcc5/gcc/x86_64-portbld-freebsd11.0/5.4.0/include-fixed/sys/types.h |more 0a1,9 > /* DO NOT EDIT THIS FILE. > > It has been auto-edited by fixincludes from: > > "/usr/include/sys/types.h" > > This had to be done to correct non-standard usages in the > original, manufacturer supplied header file. */ > 35c44 < * $FreeBSD: stable/11/sys/sys/types.h 313574 2017-02-11 02:00:56Z kib $ --- > * $FreeBSD: releng/11.0/sys/sys/types.h 299571 2016-05-12 21:18:17Z cem $ 199c208,212 < typedef __size_tsize_t; --- > #if !defined(_GCC_SIZE_T) > #define _GCC_SIZE_T > typedef __SIZE_TYPE__ size_t; > #endif > 253c266 < typedef __int64_t vm_ooffset_t; --- > typedef __vm_ooffset_t vm_ooffset_t; 255c268 < typedef __uint64_t vm_pindex_t; --- > typedef __vm_pindex_t vm_pindex_t; root@test11snapshot:/usr/include # -- Patrick Powell Astart Technologies papow...@astart.com1530 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 ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
