On 5/21/19 6:56 AM, James Shuriff wrote:
> What do you think of updating the bare metals to 9.1.0? I don’t know anything
> outside of U-Boot and the PSCI Monitor (rpi-firmware) that actually depends
> on those ports and I've tested them with my custom ports. The powerpc64-gcc
> patches aren't
huriff ; Mark Millard
> Cc: ports-list freebsd ; b...@freebsd.org
> Subject: Re: maintenance of gcc cross ports
>
> I do think it probably makes sense to divorce the baremetal GCC ports from
> powerpc64-gcc and let powerpc64-gcc just be the basis for FreeBSD-specific
>
unday, May 19, 2019 11:46 AM
> To: James Shuriff
> Cc: ports-list freebsd ; b...@freebsd.org;
> j...@freebsd.org
> Subject: Re: maintenance of gcc cross ports
>
>
>
> On 2019-May-19, at 07:40, James Shuriff wrote:
>
>> I didn't/don't plan on touching binutils. Bi
y 19, 2019 11:46 AM
> To: James Shuriff
> Cc: ports-list freebsd ; b...@freebsd.org;
> j...@freebsd.org
> Subject: Re: maintenance of gcc cross ports
>
>
>
> On 2019-May-19, at 07:40, James Shuriff wrote:
>
>> I didn't/don't plan on touching binutils. Binut
; b...@freebsd.org;
j...@freebsd.org
Subject: Re: maintenance of gcc cross ports
On 2019-May-19, at 07:40, James Shuriff wrote:
> I didn't/don't plan on touching binutils. Binutils is okay. I made new
> patches as well. What I'm really concerned with bringing up to date is
> aarch64
ARGETARCH. The
> original regex for all of those is ${PKGNAMEPREFIX:C/-//g} and I'm sure you
> can see how that's a problem when there's multiple hyphens.
Thanks for the notes.
> - James Shuriff
>
> -Original Message-
> From: Mark Millard
> Sent: Sunday, May 19, 2019 1
I submitted a bug report.
- James Shuriff
-Original Message-
From: Kurt Jaeger
Sent: Sunday, May 19, 2019 3:02 AM
To: James Shuriff
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 mas
To: James Shuriff ; ports-list freebsd
Subject: Re: maintenance of gcc cross ports
James Shuriff james at opentech.cc wrote on Sat May 18 12:29:22 UTC 2019 :
> The powerpc64-gcc port and all the ports that use it as a master
> (aarch64-gcc, aarch64-none-elf-gcc, amd64-gcc, arm-none-ea
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
James Shuriff james at opentech.cc wrote on
Sat May 18 12:29:22 UTC 2019 :
> 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
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. Powerpc64-gcc uses an
11 matches
Mail list logo
