Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 09 Aug 2018 19:47:34 +0000
From:      bugzilla-noreply@freebsd.org
To:        toolchain@FreeBSD.org
Subject:   [Bug 230399] devel/libunwind: fails to build with Clang 7
Message-ID:  <bug-230399-29464-uM6cdyFRIo@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-230399-29464@https.bugs.freebsd.org/bugzilla/>
References:  <bug-230399-29464@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=3D230399

Dimitry Andric <dim@FreeBSD.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |emaste@freebsd.org
             Status|New                         |In Progress

--- Comment #5 from Dimitry Andric <dim@FreeBSD.org> ---
(In reply to Jan Beich from comment #2)
> Probably affects a number of LLD_UNSAFE ports:
>=20
> $ echo 'int main() {}' >a.c
> $ cc a.c -lexecinfo
> $ cc a.c -fuse-ld=3Dbfd -lexecinfo
> /usr/lib/libgcc_s.so: undefined reference to `__gxx_personality_v0'
> cc: error: linker command failed with exit code 1 (use -v to see invocati=
on)

It's weird, the __gxx_personality_v0 symbol is referenced from libunwind.pi=
co,
built during the libgcc_s build.

libunwind.pico is built from contrib/llvm/projects/libunwind/src/libunwind.=
cpp,
which indeed is a C++ source file, so somehow this C++ specific symbol gets=
 in,
but it did not in the previous version of clang.

Investigating...

--=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-230399-29464-uM6cdyFRIo>