lang/gcc5 vs. devel/powerpc64-gcc: conflict for /usr/local/bin/powerpc64-portbld-freebsd11.0-gcc-5.2.0

[Mark Millard]

On a powerpc64 PowerMac I attempted to install lang/gcc5 and then use it to update devel/powerpc64-xtoolchain-gcc from the old 4.9.1 vintage that I had around. After the usual workaround for around 6 files that stage funny when a powerpc64 hosts powerpc64-gcc being built, I got the following notice on continuing the powerpc64-xtoolchain-gcc build (portmaster's -C used):

> Installing powerpc64-gcc-5.2.0...
> pkg-static: powerpc64-gcc-5.2.0 conflicts with gcc5-5.2.0_2 (installs files into the same place).  Problematic file: /usr/local/bin/powerpc64-portbld-freebsd11.0-gcc-5.2.0



Context details for those that care:

> # freebsd-version -ku; uname -aKU
> 11.0-CURRENT
> 11.0-CURRENT
> FreeBSD FBSDG5C0 11.0-CURRENT FreeBSD 11.0-CURRENT #12 r281630M: Sat Apr 18 01:15:13 PDT 2015     root at FBSDG5C0:/usr/obj/usr/src/sys/GENERIC64vtsc-NODEBUG  powerpc 1100070 1100070

The activity was to be a preliminary stage to updating to a more modern 11.0-CURRENT based on the updated powerpc64-xtoolchain-gcc .

> # svnlite info /usr/ports
> Path: /usr/ports
> Working Copy Root Path: /usr/ports
> URL: https://svn0.us-west.freebsd.org/ports/head
> Relative URL: ^/head
> Repository Root: https://svn0.us-west.freebsd.org/ports
> Repository UUID: 35697150-7ecd-e111-bb59-0022644237b5
> Revision: 402562
> Node Kind: directory
> Schedule: normal
> Last Changed Author: rene
> Last Changed Rev: 402562
> Last Changed Date: 2015-11-28 15:08:03 -0800 (Sat, 28 Nov 2015)

> # more /etc/make.conf
> WRKDIRPREFIX=/usr/obj/portswork
> MALLOC_PRODUCTION=
> CC=/usr/local/bin/gcc5
> CXX=/usr/local/bin/g++5
> CPP=/usr/local/bin/cpp5
> AS=/usr/local/powerpc64-portbld-freebsd11.0/bin/as
> AR=/usr/local/powerpc64-portbld-freebsd11.0/bin/ar
> LD=/usr/local/powerpc64-portbld-freebsd11.0/bin/ld
> NM=/usr/local/powerpc64-portbld-freebsd11.0/bin/nm
> OBJCOPY=/usr/local/powerpc64-portbld-freebsd11.0/bin/objcopy
> OBJDUMP=/usr/local/powerpc64-portbld-freebsd11.0/bin/objdump
> RANLIB=/usr/local/powerpc64-portbld-freebsd11.0/bin/ranlib
> SIZE=/usr/local/powerpc64-portbld-freebsd11.0/bin/size
> STRINGS=/usr/local/powerpc64-portbld-freebsd11.0/bin/strings



Side note on the powerpc64-gcc staging problems:

My workaround for the powerpc64-gcc staging problems when built on a powerpc64 PowerMac for a 11.0-CURRENT context was:

> cp -ax /usr/obj/portswork/usr/ports/devel/powerpc64-gcc/work/build-gcc/gcc/gcov /usr/obj/portswork/usr/ports/devel/powerpc64-gcc/work/stage/usr/local/bin/powerpc64-portbld-freebsd11.0-gcov
> 
> cp -ax /usr/obj/portswork/usr/ports/devel/powerpc64-gcc/work/build-gcc/gcc/gcov-tool /usr/obj/portswork/usr/ports/devel/powerpc64-gcc/work/stage/usr/local/bin/powerpc64-portbld-freebsd11.0-gcov-tool
> 
> cp -ax /usr/obj/portswork/usr/ports/devel/powerpc64-gcc/work/stage/usr/local/man/man1/cpp.1.gz /usr/obj/portswork/usr/ports/devel/powerpc64-gcc/work/stage/usr/local/man/man1/powerpc64-portbld-freebsd11.0-cpp.1.gz
> 
> cp -ax /usr/obj/portswork/usr/ports/devel/powerpc64-gcc/work/stage/usr/local/man/man1/g++.1.gz /usr/obj/portswork/usr/ports/devel/powerpc64-gcc/work/stage/usr/local/man/man1/powerpc64-portbld-freebsd11.0-g++.1.gz
> 
> cp -ax /usr/obj/portswork/usr/ports/devel/powerpc64-gcc/work/stage/usr/local/man/man1/gcc.1.gz /usr/obj/portswork/usr/ports/devel/powerpc64-gcc/work/stage/usr/local/man/man1/powerpc64-portbld-freebsd11.0-gcc.1.gz
> 
> cp -ax /usr/obj/portswork/usr/ports/devel/powerpc64-gcc/work/stage/usr/local/man/man1/gcov.1.gz /usr/obj/portswork/usr/ports/devel/powerpc64-gcc/work/stage/usr/local/man/man1/powerpc64-portbld-freebsd11.0-gcov.1.gz
> 
> portmaster --no-confirm -CtDK lang/powerpc64-xtoolchain-gcc

That last simply added the "C" before the "tDK" of the original portmaster command that I started the powerpc64-xtoolchain-gcc build with.


===
Mark Millard
markmi at dsl-only.net