Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 30 Dec 2020 07:50:33 +0000
From:      bugzilla-noreply@freebsd.org
To:        ports-bugs@FreeBSD.org
Subject:   [Bug 252281] devel/aarch64-none-elf-binutils: duplicates devel/binutils' origin
Message-ID:  <bug-252281-7788@https.bugs.freebsd.org/bugzilla/>

next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D252281

            Bug ID: 252281
           Summary: devel/aarch64-none-elf-binutils: duplicates
                    devel/binutils' origin
           Product: Ports & Packages
           Version: Latest
          Hardware: amd64
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: Individual Port(s)
          Assignee: ports-bugs@FreeBSD.org
          Reporter: pcc@gmx.net

G'day, folks,

As-is, and since a good while back (months? ever?),
devel/aarch64-none-elf-binutils duplicates the origin of devel/binutils so =
that
e. g. portupgrade complains just that. I. e., with portupgrade, build and
install work exactly once but never thereafter until I remove
devel/aarch64-none-elf-binutils to start anew.
I gather, though, that multiple *binutils ports should be present if one wa=
nted
to cross-build for another architecture (as I did for my RPI48GB. Btw., tha=
nks
for that!).

Without too much recent knowledge of ports, I naively tried to move the bui=
ld
directory to have a distinct orgin ...

8c8
< MMASTERDIR=3D   ${.CURDIR}/../binutils
---
> MASTERDIR=3D    ${.CURDIR}/../binutils
10c10
< .include "${MMASTERDIR}/Makefile"
---
> .include "${MASTERDIR}/Makefile"

... and symlinked some of the ports files to see what happens ...

( cd /usr/ports/devel/aarch64-none-elf-binutils/ && ln -s ../binutils/pkg-d=
escr
. )
( cd /usr/ports/devel/aarch64-none-elf-binutils/ && ln -s ../binutils/disti=
nfo
. )

... (hoping for the pkg-plist present in devel/aarch64-none-elf-binutils to=
 be
the correct one) but this eventually fails creating a package.

Comparing with other ports (www/nginx*, to be more specific), I currently g=
uess
that the MASTERDIR mechanism was inherited with _alternative_ ports in mind=
 (or
changed such at some stage) which would be different here -- but the Ports
Makefile magic beats me today.

So, until I learn more, here's my request to The Knowing for a glance, some
help, and maybe a fix.

Thanks a lot, and

All the best,

Peter.

---

[1] Possibly related (???):
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D250035

--=20
You are receiving this mail because:
You are the assignee for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-252281-7788>