Page MenuHomeFreeBSD

devel/gdb: Handle recent 14.0 systems with libc++ in /lib.
ClosedPublic

Authored by jhb on Mar 22 2022, 4:48 PM.
Tags
None
Referenced Files
Unknown Object (File)
Tue, Nov 5, 2:12 PM
Unknown Object (File)
Sun, Nov 3, 4:50 PM
Unknown Object (File)
Fri, Nov 1, 1:31 PM
Unknown Object (File)
Wed, Oct 30, 2:29 AM
Unknown Object (File)
Wed, Oct 23, 8:44 PM
Unknown Object (File)
Thu, Oct 17, 1:22 PM
Unknown Object (File)
Wed, Oct 16, 3:55 AM
Unknown Object (File)
Oct 13 2024, 12:21 PM
Subscribers

Details

Summary

The auto-load python wrapper for libc++ pretty printers has to be
installed at the same path as libc++ to work correctly. Update the
port to install the top-level wrapper in lib/ under the auto-load data
directory instead of usr/lib on recent 14.0 systems.

Diff Detail

Repository
R11 FreeBSD ports repository
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

jhb requested review of this revision.Mar 22 2022, 4:48 PM
devel/gdb/Makefile
173

does gdb bulid/work with no libc++ at all?

devel/gdb/Makefile
173

no, gdb is a C++ application, so it cannot be built without libc++
I guess the libc++ pretty printer conditions could be reworked/simplified assuming that libc++ is always available.
Is there any possibility that libc++.so.1 is not available?

devel/gdb/Makefile
173

Mmm, I guess it is still possible to build without libc++ right now but see D33108 which avoids libc++ and C++ applications in the base system.

I think it would be fine to remove the .if condition and just require that one of the two paths will exist but it's also fine to just leave tihs.

devel/gdb/Makefile
173

Yeah, when I first added this to the port we still had platforms using GCC instead of clang that didn't support libc++. I could assume it is always present at this point if that is preferred.

I think I'd rather just fix this bit for now and switch to assuming libc++ and always installing these bits as a separate followup.

This revision was not accepted when it landed; it landed in state Needs Review.Apr 14 2022, 5:06 PM
This revision was automatically updated to reflect the committed changes.