Date: Sun, 19 May 2019 14:47:43 +0000 From: James Shuriff <james@opentech.cc> To: Kurt Jaeger <pi@freebsd.org> Cc: "freebsd-ports@freebsd.org" <freebsd-ports@freebsd.org> Subject: RE: maintenance of gcc cross ports Message-ID: <BN7PR06MB5187825F9A4C2059056F43D9AA050@BN7PR06MB5187.namprd06.prod.outlook.com> In-Reply-To: <20190519070147.GA72200@home.opsec.eu> References: <BN7PR06MB5187F9588EC1B133C5DC90A7AA040@BN7PR06MB5187.namprd06.prod.outlook.com> <20190519070147.GA72200@home.opsec.eu>
next in thread | previous in thread | raw e-mail | index | archive | help
I submitted a bug report. - James Shuriff -----Original Message----- From: Kurt Jaeger <pi@freebsd.org> Sent: Sunday, May 19, 2019 3:02 AM To: James Shuriff <james@opentech.cc> Cc: freebsd-ports@freebsd.org Subject: Re: maintenance of gcc cross ports Hi! > The powerpc64-gcc port and all the ports that use it as a master > (aarch64-gcc, aarch64-none-elf-gcc, amd64-gcc, arm-none-eabi-gcc, > i386-gcc, mips-gcc, mips64-gcc, and sparc64-gcc) are very old and use > buggy makefiles. > I would like to take over maintenance of these ports. [...] Can you submit patches via bugs.freebsd.org so that your patches can be wor= ked on ? -- pi@opsec.eu +49 171 3101372 One year to go ! ________________________________ DISCLAIMER: This message and any attachments are intended solely for the u= se of the recipient and may contain confidential information. If you have r= eceived this message in error please delete it and promptly notify the send= er, James Shuriff (james@opentech.cc<mailto:james@opentech.cc>).
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?BN7PR06MB5187825F9A4C2059056F43D9AA050>