Date: Wed, 01 Mar 2023 00:18:09 +0000 From: Lorenzo Salvadore <developer@lorenzosalvadore.it> To: Gerald Pfeifer <gerald@pfeifer.com> Cc: Mark Millard <marklmi@yahoo.com>, Piotr Kubaj <pkubaj@anongoth.pl>, dev-commits-ports-main@freebsd.org Subject: Re: git: ca48c22e1c7a - main - lang/gcc12: add gcc 12 Message-ID: <QkUBIj-1CD22J9PEYwiCkMtiparUujCIb7WsDKBo4pnzqZ2m-vO89kvc2-s-rZmIP1H5sv5-lX5eoiThtTFlTswmZJl9fJDxW_ckDSR5x64=@lorenzosalvadore.it> In-Reply-To: <41ba5bb0-853c-6712-f035-9f14794737e2@pfeifer.com> References: <BC65C422-C4E6-444B-8B52-F7989D97200F@yahoo.com> <94B6CB06-97A9-4413-BBA8-4DAF0794617D@yahoo.com> <Ynr5cfXW0RvetkQZ@KGPE-D16> <7453FF09-7361-4F16-8F18-5FA0242B002F@yahoo.com> <41ba5bb0-853c-6712-f035-9f14794737e2@pfeifer.com>
next in thread | previous in thread | raw e-mail | index | archive | help
------- Original Message ------- On Wednesday, March 1st, 2023 at 12:50 AM, Gerald Pfeifer <gerald@pfeifer.c= om> wrote: >=20 >=20 > [ Adding Lorenzo and providing a full quote ] >=20 > On Tue, 10 May 2022, Mark Millard wrote: >=20 > > [Looks like you did not CC Gerald for him to decide > > if he wanted to comment or to just send a decline to > > comment.] > >=20 > > On 2022-May-10, at 16:46, Piotr Kubaj pkubaj@anongoth.pl wrote: > >=20 > > > I fixed the first issue. > > >=20 > > > As for the second one, I'm not sure what would be the correct fix (we > > > could move libgccjit++.h to a non-standard directory, but I'm not sur= e > > > about the consequences). Maybe Gerald could offer some insight about > > > this issue. > >=20 > > If the normal notation is via #include <libgccjit++.h> there > > might be other places that would just work [absent file name > > conflicts] and be gcc vintage specific. > >=20 > > But if the normal notation is via #include "libgccjit++.h" > > then it might not be that easy. > >=20 > > I will also note that, while pkg only reported the one file, > > there is also a libgccjit.h with the issue as well: > >=20 > > # grep -v % /usr/ports/lang/gcc12/pkg-plist > > include/libgccjit++.h > > include/libgccjit.h > > @postexec if type ccache-update-links >/dev/null 2>&1; then ccache-upda= te-links -v; fi > > @postunexec if type ccache-update-links >/dev/null 2>&1; then ccache-up= date-links -v; fi > > @comment Insert PLIST.lib here > >=20 > > # grep -v % /usr/ports/lang/gcc11/pkg-plist > > include/libgccjit++.h > > include/libgccjit.h > > @postexec if type ccache-update-links >/dev/null 2>&1; then ccache-upda= te-links -v; fi > > @postunexec if type ccache-update-links >/dev/null 2>&1; then ccache-up= date-links -v; fi > > @comment Insert PLIST.lib here > >=20 > > I do not know how much use is made of libgccjit* > > under FreeBSD. > >=20 > > Looking around it seems that linux contexts seem to > > deal with such by bundling up libgccjit* material > > for separate installation so there ends up being > > either zero or one instance around, despite possibly > > having multiple gcc* vintages installed. >=20 >=20 > Lorenzo has created a fix for this which, sadly, is stuck upstream still: > https://gcc.gnu.org/pipermail/gcc-patches/2022-November/606450.html Yes, and unfortunately the same holds for another similar patch that has be= en submitted in the following upstream bug report: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D101491 . I will keep trying to get some attention to the patches. Cheers, Lorenzo Salvadore
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?QkUBIj-1CD22J9PEYwiCkMtiparUujCIb7WsDKBo4pnzqZ2m-vO89kvc2-s-rZmIP1H5sv5-lX5eoiThtTFlTswmZJl9fJDxW_ckDSR5x64=>