On Wed, Jan 29, 2025 at 10:02:30AM -0800, Steve Kargl wrote:
> On Tue, Jan 28, 2025 at 12:02:09PM -0800, Steve Kargl wrote:
> > JFYI,
> >
> > The ports of lang/gcc are likely effected by
> >
> > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118685
> >
> > If one uses -static and ctor/dtor's are involved,
> > the resulting executable will segfault at exit.
> >
>
> This issue is now
>
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=284441
>
To move this along, as there is a boat-load of inertia in portland
diff --git a/files/patch-libgcc-config.host b/files/patch-libgcc-config.host
new file mode 100644
index 000000000000..266694676d17
--- /dev/null
+++ b/files/patch-libgcc-config.host
@@ -0,0 +1,11 @@
+--- libgcc/config.host.orig 2025-01-30 12:31:26.479569000 -0800
++++ libgcc/config.host 2025-01-30 12:32:03.732682000 -0800
+@@ -286,7 +286,7 @@
+ # machine-specific sections may refine and add to this
+ # configuration.
+ tmake_file="$tmake_file t-freebsd t-crtstuff-pic t-libgcc-pic t-eh-dw2-dip
t-slibgcc t-slibgcc-gld t-slibgcc-elf-ver"
+- extra_parts="crtbegin.o crtend.o crtbeginS.o crtendS.o"
++ extra_parts="crtbegin.o crtend.o crtbeginS.o crtbeginT.o crtendS.o"
+ case ${target_thread_file} in
+ posix)
+ tmake_file="${tmake_file} t-freebsd-thread"
--
Steve
