Bug 248737 - devel/libunwind: Fix build with -fno-common (clang 11 and gcc 10)
Summary: devel/libunwind: Fix build with -fno-common (clang 11 and gcc 10)
Status: Closed Overcome By Events
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Some People
Assignee: Po-Chuan Hsieh
URL:
Keywords:
Depends on:
Blocks: 248756
  Show dependency tree / graph
 
Reported: 2020-08-18 21:11 UTC by Dimitry Andric
Modified: 2020-08-19 17:42 UTC (History)
1 user (show)

See Also:
bugzilla: maintainer-feedback? (sunpoet)

Attachments
Fix build with -fno-common (clang 11 and gcc 10) (941 bytes, patch)
2020-08-18 21:11 UTC, Dimitry Andric 		no flags Details | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Dimitry Andric freebsd_committer freebsd_triage 2020-08-18 21:11:35 UTC 
Created attachment 217322 [details]
Fix build with -fno-common (clang 11 and gcc 10)

In base r364284, I imported clang 11 into head. Like gcc 10, it now defaults to -fno-common, meaning that duplicated global symbols will most likely lead to link errors. Here is a patch to fix this port's duplicated global symbols.
Comment 1 Niclas Zeising freebsd_committer freebsd_triage 2020-08-18 23:30:35 UTC 
This is already fixed in ports r545235