Re: what is the proper procedure for submitting changes to existing ports?

> > Are these diffs in the links below in proper format? Thanks for the help
> > as I've
> > never done this before.
>
> No - please send "cvs diff -u" or "git diff" depending on where you got your ports tree from.
>
>
> > The AltiVec patches are crucial to playing 360p
> > x264 MP4 files on my 1.42GHz G4, as well as speeding up file conversion.
> > The IOQuake3 patches are the first to support any PowerPC BSD, and were
> > pretty straight forward to figure out.
> >
> > https://marc.info/?l=openbsd-ports&m=159072101614301&w=2
> >
> > https://marc.info/?l=openbsd-ports&m=159071707413348&w=2
>
> The altivec patch forces CC=gcc which is the old base-system gcc
> which generally shouldn't be used any more. Since there is a problem
> with clang then you can try setting COMPILER=ports-gcc to use a more
> modern version of gcc from ports.
>
>

Thank you very much for setting me on the right path. I will see if
ports-gcc has the same bugs. I will also change all the patches to the
correct format.