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
Hi!
I've just uploaded a diff you need:
https://github.com/OrangeGrayCyan/warsow/blob/master/warsow.diff
Also to avoid tarball name confict between warsow and warsow-data,
please use 2.1.2-source tag instead of 2.1.2 (we noticed it too late).
On Sat, May 18, 2019 at 02:11:06PM +0300, Leonid
On 2019-May-18, at 21:11, Mark Millard wrote:
> This was in a poudriere bulk build on a head -r347549 based powerpc64
> system with system clang 8 for cc and c++ and base/binutils
> for ld. I was attempting a build with the -O1 changes disabled. (Note:
> the system is self hosting for buildworld
This was in a poudriere bulk build on a head -r347549 based powerpc64
system with system clang 8 for cc and c++ and base/binutils
for ld. I was attempting a build with the -O1 changes disabled. (Note:
the system is self hosting for buildworld buildkernel via the clang 8
and base/binutils
On 5/8/19 1:44 PM, Jan Beich wrote:
Hello.
While I am by no means at the end of this, I'll post some updates.
> "stack overflow detected" messages are part of -fstack-protector*.
> Recently, ports/ default changed to -strong in order to follow base/.
>
>
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
On Sat, May 18, 2019 at 10:31:04AM +, Alexey Dokuchaev wrote:
> On Tue, May 14, 2019 at 01:39:43PM +0300, Leonid Bobrov wrote:
> > I've finished porting Warsow on my side, I hope you'll use my patches
> > to resurrect appropriate ports and Warsow will just work at FreeBSD.
> >
> >
