Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 07 Jan 2024 17:51:01 +0000
From:      bugzilla-noreply@freebsd.org
To:        ports-bugs@FreeBSD.org
Subject:   [Bug 273753] [exp-run] Against llvm-17-update branch on GitHub
Message-ID:  <bug-273753-7788-caitU752Ak@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-273753-7788@https.bugs.freebsd.org/bugzilla/>
References:  <bug-273753-7788@https.bugs.freebsd.org/bugzilla/>

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

--- Comment #114 from commit-hook@FreeBSD.org ---
A commit in branch stable/14 references this bug:

URL:
https://cgit.FreeBSD.org/src/commit/?id=3D86188fdaca05f6cac1d67e2a57547dc6f=
423ba1b

commit 86188fdaca05f6cac1d67e2a57547dc6f423ba1b
Author:     Dimitry Andric <dim@FreeBSD.org>
AuthorDate: 2023-12-13 18:53:17 +0000
Commit:     Dimitry Andric <dim@FreeBSD.org>
CommitDate: 2024-01-07 17:46:19 +0000

    Proactively remove libc++ __tuple header file that became a directory

    This was already handled in ObsoleteFiles.inc (see the 20230622 entry),
    but some people never run "make delete-old", or want to upgrade directly
    from a revision that still had libc++ 15 to the most recent revision.

    They would then encounter a failure during installworld, similar to:

      install: target directory `/usr/include/c++/v1/__tuple/' does not exi=
st

    Therefore, clean it up in the distrib-cleanup phase, similar to the
    earlier instance of the libc++ __string header file that became a
    directory.

    PR:             273753
    MFC after:      1 month

    (cherry picked from commit ca217224f17229570f40227893353ca10ae1dda1)

 etc/Makefile | 1 +
 1 file changed, 1 insertion(+)

--=20
You are receiving this mail because:
You are on the CC list for the bug.=



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