Date: Fri, 14 Apr 2017 20:07:37 -0700 From: "Ngie Cooper (yaneurabeya)" <yaneurabeya@gmail.com> To: Mark Millard <markmi@dsl-only.net> Cc: Gerald Pfeifer <gerald@pfeifer.com>, Pedro Giffuni <pfg@FreeBSD.org>, FreeBSD Ports <freebsd-ports@freebsd.org>, FreeBSD Toolchain <freebsd-toolchain@freebsd.org>, freebsd-arm <freebsd-arm@freebsd.org>, ericturgeon.bsd@gmail.com, FreeBSD Current <freebsd-current@freebsd.org> Subject: Re: lang/gcc6-aux for head beyond __nonnull related issues: vm_ooffset_t and vm_pindex_t related changes (and more) Message-ID: <7606F976-20B7-4FB8-BE80-C27773F5529A@gmail.com> In-Reply-To: <FA9D3BB0-E5DA-4DAE-BA61-01BFCFBCC24C@dsl-only.net> References: <E54E495A-E4C8-40B3-B1E8-133A9872B6B2@dsl-only.net> <9758023E-1526-41F9-9416-6AC8AD3201B5@dsl-only.net> <E86AC2D1-EE2D-4E33-85FD-8069B050421F@FreeBSD.org> <alpine.LNX.2.21.1704150928320.4604@anthias.pfeifer.com> <FA9D3BB0-E5DA-4DAE-BA61-01BFCFBCC24C@dsl-only.net>
next in thread | previous in thread | raw e-mail | index | archive | help
--Apple-Mail=_534C68CC-3A27-411C-AB28-2AACB66F40B1 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 > On Apr 14, 2017, at 19:53, Mark Millard <markmi@dsl-only.net> wrote: >=20 > On 2017-Apr-14, at 4:30 PM, Gerald Pfeifer <gerald@pfeifer.com> wrote: >=20 >> On Thu, 13 Apr 2017, Pedro Giffuni wrote: >>> I didn=E2=80=99t want to get into this but the problem is that as = part of it's >>> build/bootstrapping process, GCC historically takes system headers >>> and attempts to =E2=80=9Cfix=E2=80=9D them. I am unsure the fixes do = anything at all >>> nowadays but the effect is that the compiler tends to take snapshots >>> of the system headers when it is built. cdefs.h is used by all the >>> system headers so changes in cdefs.h have good chances affecting >>> such builds but any change are likely to cause similar trouble. >>>=20 >>> In the case of gcc-aux, it appears the compilation is based on a >>> bootstrap compiler which already carries outdated headers. >>> A workaround, suggested by gerald@ the last time a similar issue >>> happened was to run for install-tools/fixinc.sh. I think that may >>> regenerate the headers and let the build use updated headers. >>> Ultimately gcc-aux needs maintainer intervention and using >>> outdated headers will break sooner or later: especially on -current. >>=20 >> Indeed, thanks for the analysis/background, Pedro! >>=20 >> I had a look at gcc6-aux is based on the 20170202 snapshot of GCC 6, >> and perhaps John (as the maintainer of that port) has plans to update >> it? Let me copy him. >=20 > [As I have a prior E-mail exchange with John M. indicating that > he was not intending to be the lang/gcc6-aux maintainer, I > avoid spamming him with this material: I've removed him from > the CC list in this reply. I can send the material to him if I > see evidence of his wanting it.] >=20 > Just FYI: >=20 > [Previously: temporarily adding __nonnull and __nonnull_all > back into into my local head FreeBSD variant got problems > with: __vm_ooffset_t and __vm_pindex_t no longer existing and > also the same pid_t issue indicated below.] >=20 >=20 > I tried using [on a Pine64+ 2GB aarch64 system]: >=20 > # = /usr/obj/portswork/usr/ports/lang/gcc6-aux/work/bootstrap/libexec/gcc/aarc= h64-aux-freebsd12.0/6.3.1/install-tools/mkheaders = /usr/obj/portswork/usr/ports/lang/gcc6-aux/work/bootstrap >=20 > to deal with __nonnull, __nonnull_all, __vm_ooffset_t, and = __vm_pindex_t. >=20 > I then built via portmaster -CDK usage. Various header issues > did go away but the build of lang/gcc6-aux still stopped with: >=20 > In file included from = /usr/obj/portswork/usr/ports/lang/gcc6-aux/work/gcc-6-20170202/libiberty/s= imple-object.c:20:0: > ./config.h:556:15: error: two or more data types in declaration = specifiers > #define pid_t int > ^ >=20 > I'm guessing that the define for pid_t in config.h resulted > in something like: >=20 > typedef ??? pid_t; >=20 > that turned into something like a: >=20 > typedef ??? int; >=20 > for the error listed above. >=20 > There were also implicit-declaration warnings: >=20 > = /usr/obj/portswork/usr/ports/lang/gcc6-aux/work/gcc-6-20170202/libiberty/s= imple-object.c: In function 'simple_object_internal_read': > = /usr/obj/portswork/usr/ports/lang/gcc6-aux/work/gcc-6-20170202/libiberty/s= imple-object.c:75:21: warning: implicit declaration of function 'read' = [-Wimplicit-function-declaration] > ssize_t got =3D read (descriptor, buffer, size); > ^~~~ > = /usr/obj/portswork/usr/ports/lang/gcc6-aux/work/gcc-6-20170202/libiberty/s= imple-object.c: In function 'simple_object_internal_write': > = /usr/obj/portswork/usr/ports/lang/gcc6-aux/work/gcc-6-20170202/libiberty/s= imple-object.c:119:23: warning: implicit declaration of function 'write' = [-Wimplicit-function-declaration] > ssize_t wrote =3D write (descriptor, buffer, size); > ^~~~~ >=20 > The implicit-declaration warnings for read and write may well > also not be expected/desirable. >=20 > It may be that more than a script run is needed to make > things be appropriate. Is there a reason why you need ada support (that seems to be the = only real reason for installing gcc6 vs gcc6-aux)? gcc6-aux uses a = snapshot of gcc6 with custom options. Thanks! -Ngie --Apple-Mail=_534C68CC-3A27-411C-AB28-2AACB66F40B1 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQIcBAEBCgAGBQJY8Y56AAoJEPWDqSZpMIYVCqUQAJ3/RIVZHjUlbjtlq+eCNLiZ fk4l21s7AFvgMtRsqSulnEjPQywT+kcq/BIZUr7r+J9KRqIWu8uBIeZQ3znciXbS zH8LEfJFl/2Xy1ixCE3nJ1e4v/kP4CgeKLtiNVz4PgxA0rcqgucQLqWApC4QaRPl xe7/lLOTn1j9As4YaNErasU55JSzmlvGEQQb4HAKIR+/CX9qofekwj8cqtsdy7Bt dQ93H3HPVsJRHSbPDYt4zWfbGC//PZM28nEWVNguVKI21XIz68oToB9mWPdF7QVM qWCB7OfDoVHclKk4dmdNJe3Qz/qhDdYJQQd2T8i6q9qHE4xxuuTLlKx5J8KAxohd oM7ZEbqBMtddJA35g1nGwhBnIqcOITho+aDMaANYo7ykEUNpY2LFOtuxuBeSJpZ5 LgVXuRz4kopf4UHZ+XoNCI4EFWIFl/VpJd/rjpMkBgbn/Olu+6tNIyy6tZUB5BPn Cchu+5lmRaqTVtjjFbc0QS/SdXlRnoz2MA+xd+CvI2TDFXdoDS+amUU2keOPvkS+ nOb0h5exvPecvlnhhVQPgmLRnl6SJ4+N6MBt5l7Zfp5nc9lUMMK+1xo48guPd4E8 mLgozotLhXZIcRECl++g5dCm7x+7pYN/4+VHM9jd4YiRvZnnABj4+XaNlovukQAR yVjX49cZnKiT2FVMK3d5 =jZS8 -----END PGP SIGNATURE----- --Apple-Mail=_534C68CC-3A27-411C-AB28-2AACB66F40B1--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?7606F976-20B7-4FB8-BE80-C27773F5529A>