devel/binutils could use a bit of love wrt https://www.freebsd.org/doc/en/books/porters-handbook/porting-order.html to make it more readable.

Heh, I had thought about just doing this for the ones used by xtoolchain, but this looks more complete.

One thing that might really be nice would be to have an easy way to have multiple PLIST files so that one could have something like:

PLIST_FILES= ${.CURDIR}/pkg-plist ${.CURDIR}/pkg-plist.${TARGETARCH}

And put "common" files in pkg-plist and ARCH-specific files in the sub-plists rather than duplicating lots of plist content. For freebsd6-gcc I used a unified plist with PLIST_SUB's for ARCH-specific files, but having a nice way to have pkg-plist.${FOO} in addition to pkg-plist would be nicer IMO.

One thing to consider is that this doesn't fix all the places that have dependencies like all the devel/<arch>-gcc ports, etc.

In D22258#486560, @jhb wrote:

Heh, I had thought about just doing this for the ones used by xtoolchain, but this looks more complete.

One thing that might really be nice would be to have an easy way to have multiple PLIST files so that one could have something like:

PLIST_FILES= ${.CURDIR}/pkg-plist ${.CURDIR}/pkg-plist.${TARGETARCH}

And put "common" files in pkg-plist and ARCH-specific files in the sub-plists rather than duplicating lots of plist content. For freebsd6-gcc I used a unified plist with PLIST_SUB's for ARCH-specific files, but having a nice way to have pkg-plist.${FOO} in addition to pkg-plist would be nicer IMO.

Agreed on that, but that requires some work on the framework which I will probably do later, if the use case becomes common ;)

One thing to consider is that this doesn't fix all the places that have dependencies like all the devel/<arch>-gcc ports, etc.

hum did I miss a place? as far as grep tells me, I should have addressed everything. Anyway I requested an exp-run, we will know quickly.

In D22258#486564, @bapt wrote:

In D22258#486560, @jhb wrote:

Heh, I had thought about just doing this for the ones used by xtoolchain, but this looks more complete.

One thing that might really be nice would be to have an easy way to have multiple PLIST files so that one could have something like:

PLIST_FILES= ${.CURDIR}/pkg-plist ${.CURDIR}/pkg-plist.${TARGETARCH}

And put "common" files in pkg-plist and ARCH-specific files in the sub-plists rather than duplicating lots of plist content. For freebsd6-gcc I used a unified plist with PLIST_SUB's for ARCH-specific files, but having a nice way to have pkg-plist.${FOO} in addition to pkg-plist would be nicer IMO.

Agreed on that, but that requires some work on the framework which I will probably do later, if the use case becomes common ;)

I would use it in freebsd-gcc*, base/binutils, and base/gcc* at least. :)

One thing to consider is that this doesn't fix all the places that have dependencies like all the devel/<arch>-gcc ports, etc.

hum did I miss a place? as far as grep tells me, I should have addressed everything. Anyway I requested an exp-run, we will know quickly.

Oh, I guess it was just powerpc64-gcc/Makefile that had to be updated.

I'm fine with this one landing first and then updating my freebsd6-gcc one. Should be a tiny update to that.